Paul Liebrand's Weblog

Welcome to my blog mainly about SharePoint

Skip to: Content | Sidebar | Footer

Google Search

“Set as default My Site”, “SharePoint Sites”, or “My SharePoint Sites” missing in Office 2010 on SharePoint 2007?

27 September, 2011 (10:15) | Office, SharePoint | By: Liebrand

If your organization is rolling out Windows 7 with Office 2010 in your environment but you are still using SharePoint 2007 you might notice that the “Set as default My Site” option is no longer working. Clicking this link is crucial to enabling the Office / SharePoint integration points.

If you do not already know this, each time you click on the Open or Save menus within an Office product it looks for a special registry key under the user profile. This registry key tells Office what SharePoint farm your user is connected to and will retrieve their SharePoint site membership information. Once this information has been retrieved, it will hydrate the “SharePoint Sites” (or “My SharePoint Sites” on Office 2007) folder.

NOTE: If it successfully finds this location in the registry it will not check it again for up to 24 hours.

9-27-2011 9-56-29 AM

I have other posts that explains how this membership works in SharePoint and how to effectively use it with Office.

On to the issue – you will notice that if you visit your My Site with Office 2010 installed you may see the “Set as default My Site” display momentarily and the disappear.

If we look closely at the HTML source of the My Site page, you can see that Microsoft is attempting create a new ActiveX object:

objPersonalSite = new ActiveXObject("PortalConnect12.PersonalSite.1");

If you use the developer toolbar and attempt to evaluate objPersonalSite it will return null.

Searching through the registry, I found no mention of PortalConnect12.PersonalSite.1 – I did however find a mention of PortalConnect14.PersonalSite.1. No wonder the ActiveX control is not working – there is no reference to it on the system.

I took the PortalConnect14 keys and duplicated them and changed the values from 14 to 12 using a registry file:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite]
@="PersonalSite Class"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CLSID]
@="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CurVer]
@="PortalConnect12.PersonalSite.1"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1]
@="PersonalSite Class"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1\CLSID]
@="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

I went back to my My Site and the automatic dialog box popped up asking if I want to set this site as my default My Site:

9-27-2011 10-09-17 AM

I clicked Yes and went to the registry location I was aware of (HKCU\Software\Microsoft\Office\14.0\Common) but did not see the Portal key I was expecting.  Come to find out, on Windows 7, this is written to another location:

HKCU\Software\AppDataLow\Microsoft\Office\14.0\Common\Portal

At this point, if you fire up any of the core Office applications and click on Open or Save As and wait a few minutes, you should see a “SharePoint Sites” option appear and start hydrating it with all your SharePoint membership sites.


Post to Twitter Post to Delicious Post to Digg Post to Facebook Post to Reddit

  • Pingback: Sharepoint Update Sep-27-2011 | SDavara's Knowledge Center()

  • Chad

    I’m having a similar issue where the “SharePoint Sites” or “My SharePoint Sites” links aren’t showing up under the save as dialog. We’re currently in the process of ugprading our network from Windows XP to Windows 7, but my machine is still on XP (with office 2007). I have, however, tested on both XP and Win7 machines I do not see the links on either.

    We’re also experiencing strange timeout behaviour with the save as dialogs (the dialog freezes), so I’m thinking it’s trying to communicate with sharepoint but is unable. We’ve recently upgraded our SharePoint server from 2007 to 2010 and the server name and IP changed so it may be trying to communicate with the old server still.

    I’ve searched the registry for references to the old server and deleted or replaced those references, but still no luck. Any ideas?

  • Download and install Fiddler. When running fiddler, open the save as dialog and see if it is trying to communicate with an old server.

  • Bryan

    What if you’re running sharepoint 2010 and it doesn’t prompt you to set as my default mysite?  We have sharepoint 2007 and sharepoint 2010.  I want my sharepoitn 2010 mysite to be default.

  • SharePoint 2010 does not have that prompt that SharePoint 2007 does — it is handled differently and requires you to have Office 2010.

  • Mleckman

    Paul,
    I am having this exact issue. Any chance we can converse about this.

  • Mleckman

    Paul, ran your fix and just wanted to update 1 piece. Under the first PortalConnect header, there is a sub menu called “curVer” that also needs to be changed to 12. Appreciate your hard work and continued help. thanks

  • Thanks for the clarification. I am glad you got it working.

  • Pingback: Excel 2010, Connection files on the Network, SharePoint Data Connection Libraries, and the Enterprise « Martin's BI Blog()

  • PepperX

    Hi Paul, thanks for a great blog post! Do you know if there’s a way to manually trigger the call to update a client machines registry without having to resort to regedit? It’s kind of inefficient waiting for the 24h update when you’re experimenting. This is SP 2010 and Office 2010 on Win7. Thanks!

  • Unfortunately, I do not know of a way of triggering besides through the registry. I completely agree with you that this the wrong way to do it but it is what it is.

    Paul

  • GL

    You have helped us! After a long search, I came across your post and of course immediately tested. Works great with the import of the reg file.
    Our environment:
    Win7 + Office 2010 + SharePoint 2007

    Thanks very much!

  • Glad I could help!

  • Aaron

    Hi Paul, great post. Your solution has helped for many years now, unfortunately Office 2013 is not behaving in the same way. Any ideas on why Office 2013 doesn’t create the defined “Published links to Office client applications” from a SharePoint 2010 environment.

  • Paul Oswald

    Hi Aaron, I’m having the same issue in my environment. Have you had any luck finding a solution?

  • Aaron,
    I haven’t had a chance to look into this personally. I am assuming you have attempting to change the 12 to 14 in the registry keys?
    If I get a chance I’ll try get something setup to test myself and see if I can figure out how it works or has changed in Office 2013.
    Thanks,
    Paul

  • Paul Ryan

    Hi Paul, excellent help thanks!
    Same thing happens with Office 2013 with SharePoint 2013. Would be awesome to see an update here. You’re a legend.

  • Paul Ryan

    Hi Paul, i’m having the same issue with Office 2013 + SharePoint 2013. have you found anything?

  • Paul Ryan

    -post deleted-

  • Paul,

    What exactly is happening? I finally got around to testing it this morning and everything appeared to be functioning the way it should. My machine I am testing on is not a fresh install so it could be that some of the old components (i.e. Office 2010) are “helping” it work.

    Explain exactly what is happening to you and I might be able to offer some insight.

    Thanks,

    Paul

  • You may want to refer to this article. Obviously everything is now 15 instead of 12. http://paulliebrand.com/2009/08/25/publishing-links-to-office-2007-without-enabling-my-sites-in-sharepoint/

    I just tested this in my environment and it totally worked. If you do not have the 15.0/Common/Portal registry key setup with a PersonalSiteURL defined then Office 2013 will not get any of the published links.

  • Paul, See my response above to Aaron.

  • Paul Ryan

    Hi Paul, after further investigation, things are ALMOST working correctly. Office is sucking down the links and whacking them in the registry, however Office seems a bit confused as to where to look for them.

    There are two paths: “c:usersusernamesharepoint” and “c:usersusernamesharepoint sites”

    it is the SharePoint folder which is shown in MS Office under favourites. SharePoint Sites does not appear, certainly not by default.

    Also, i was hoping that the initial File-Open-SharePoint area would display the published links.

    Anyway, so its difficult for an end user to find the SharePoint Sites folder. they have to manually navigate. do you know why Office has created two folders and chosen the wrong one to present to the user?

    PS. You’re a massive legend.