This problem suddenly emerged when we upgraded to SharePoint 2013 in our environment. I have this problem on my own computer as well. I see I can work around this problem by disabling "Outlook Social Connector 2013", however I cannot ask all users with this problem to do this.

I wonder why this happens? I've done a bit of monitoring by using ProcMon and it seems like it tries to connect to a nonexistent site, so I wonder to start by asking where in the registry one define the path for the Social connector?

My settings are completely empty, except for user name.

• Edited by HAL07 Monday, May 04, 2015 8:44 AM

Probably this link will help-

http://community.office365.com/en-us/f/158/t/221669.aspx

Thanks,

Danny

Please remember to mark as answer if it helps or vote if it is useful

No I've already checked that. We do not run Office 365. We run our own Exchange 2013. Also, the article recommends manual steps that we cannot ask all our users to use.

• Edited by HAL07 Monday, May 04, 2015 9:29 AM

Hi,

I didn't find the registry to control the path, but as you mentioned you could work around this problem by disabling "Outlook Social Connector 2013", how about just disabling this specific social connector provider(SharePoint), so that other connectors won't be disabled?

We can learn from this kb:

How to manage the Outlook Social Connector by using Group Policy

Use the String: DisabledProvidersList to disable SharePoint: OscAddin.SharePointProvider in the registry key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Outlook\SocialConnector

Regards,

Melon Chen
TechNet Community Su

I added this to loginscript and this works.

reg add HKCU\Software\Microsoft\Office\Outlook\SocialConnector /v RunOSC /t REG_DWORD /d 0 /f