Issue: Cannot spot My Site & My links on home page of Sharepoint website
Before we proceed lets check if the SSP is created and its working good
Then check if there is a different application created for My site and My links and check the site collection created in the Central admin page, if there are collections present with /username.
Now start investigating the SSP, here in SSP you have some features to check the status of these two links
Look into Personalization service permissions > edited permissions for NTAuthority\AllAuthenticatedUsers > it should have permissions to create my site & personalize settings
Look into My site settings
Look into My site host permissions, you should be able see the authenticated users there
Check the personalization site permissions, but you will have to work with audience in this way
Also check is use personal permissions is enabled there
When you complete doing all this you have to start thinking on isolation of this issue, Isolation of the issue is very very important as when you troubleshoot as it gives you the right direction
Create a new web application ‘Test’ and check if you can spot the links there, if not there then you might have to check with a new SSP
If you can, either the web application is corrupt or there is a redirection setup on the Application Pool
The point is that if you have a redirection setup on the app pool level it prevents the My sites and My links from appearing on the application
Suppose your site url is http://hotmail and you set the redirection to http://hotmail.dsc.net so that whenever your user opens browser and types http://hotmail and gets redirect to http://hotmail.dsc.net , this keeps away the my sites & my links.
To workaround remove the redirection from Application Pool, and use it through the Alternate Access mappings on the Central Administration page
Wednesday, March 11, 2009
Thursday, March 5, 2009
February Cumulative Update for Sharepoint Server
February Cumulative Update
There are lots of known issue that are fixed [such as orphaned entries for site collection/subsites, SSP Index backup/restore issues]
Please take a look at the following articles and get to know the issues that we have encountered and the ones which are fixed in the update.
Knowledge base articles:WSS 961750 GlobalDescription of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): February 24, 2009http://support.microsoft.com/kb/961750
967703 Language specificDescription of the Windows SharePoint Services 3.0 hotfix package (Wssmui-en-us.msp): February 24, 2009http://support.microsoft.com/kb/967703
MOSS & Search Server 2008 961749 Global Description of the Office SharePoint Server 2007 hotfix package (Coreserver.msp): February 24, 2009http://support.microsoft.com/kb/961749
961754 Language specific Description of the Microsoft Office SharePoint Server 2007 hotfix package (Coreservermui.msp): February 24, 2009http://support.microsoft.com/kb/961754
Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): January 27, 2009http://support.microsoft.com/kb/963023/
Download locations:WSS 961750 Global http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961750&kbln=en-us
967703 Language specific http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=967703&kbln=en-us
MOSS & Search Server 2008 961749 Global http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961749&kbln=en-us
961754 Language specific http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961754&kbln=en-us
A little update on this …..
You cannot install the February Cumulative update on you server unless you have the December CU installed the dilemma is that the Feb CU unlike Dec CU does not contain all the previous updates, or a better option is to wait for the “Uber” package which will contain all the previous updates, this package should be out in few weeks from now but no ETA defined .
There are lots of known issue that are fixed [such as orphaned entries for site collection/subsites, SSP Index backup/restore issues]
Please take a look at the following articles and get to know the issues that we have encountered and the ones which are fixed in the update.
Knowledge base articles:WSS 961750 GlobalDescription of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): February 24, 2009http://support.microsoft.com/kb/961750
967703 Language specificDescription of the Windows SharePoint Services 3.0 hotfix package (Wssmui-en-us.msp): February 24, 2009http://support.microsoft.com/kb/967703
MOSS & Search Server 2008 961749 Global Description of the Office SharePoint Server 2007 hotfix package (Coreserver.msp): February 24, 2009http://support.microsoft.com/kb/961749
961754 Language specific Description of the Microsoft Office SharePoint Server 2007 hotfix package (Coreservermui.msp): February 24, 2009http://support.microsoft.com/kb/961754
Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): January 27, 2009http://support.microsoft.com/kb/963023/
Download locations:WSS 961750 Global http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961750&kbln=en-us
967703 Language specific http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=967703&kbln=en-us
MOSS & Search Server 2008 961749 Global http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961749&kbln=en-us
961754 Language specific http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961754&kbln=en-us
A little update on this …..
You cannot install the February Cumulative update on you server unless you have the December CU installed the dilemma is that the Feb CU unlike Dec CU does not contain all the previous updates, or a better option is to wait for the “Uber” package which will contain all the previous updates, this package should be out in few weeks from now but no ETA defined .
Subscribe to:
Posts (Atom)