Last Updated: Tuesday 21 August 2007, 8:40am AEST
You can obtain a Hotfix from Microsoft without contacting support by visiting this site (https://support.microsoft.com/contactus2/emailcontact.aspx?scid=sw;en;1410&WS=hotfix).
The following is a list of issues that various people I know have found in MOSS.
- If you create a new default page in a publishing site, change the welcome page to point to this site, delete the original default.aspx and then rename your page to default.aspx, when you try to deploy it will fail, stating that a file with the same name already exists. This is due to the underlying GUID of the page being changed.
- If you have created and configured a staging site to use your own master pages, when you first deploy to a blank site collection, The Master page settings and alternate CSS URL settings are not applied. The BlueTabs Master becomes the default.
- SharePoint Designer often gets confused, thinking that you have items checked out when you haven’t. Often you have to delete the file and recreate it to get around the problem.
- When in daylight savings mode, you need to set the time 1 hour earlier in both the staging environment and the destination server in order for deployment to work properly. Stefan has posted an update on this issue, a hotfix is on its way to resolve this, in the meantime, there is a work around. Hotfix for DST problem has been released yesterday. Søren Nielsen has commented below: Hotfix for content deployment problem has also been released (also targetting the PRIMARY KEY problem). Both are private hotfixes, contact MS to obtain them.
- If News articles are displayed on the home page with an RSS subscription link, clicking on it effectively subscribes you to everything on the portal site. As the default setting for lists in MOSS is RSS enable, people get items they never even asked for.
- If you edit the page settings of an existing page the Page Contact information is provided incorrectly and does not let you save your changes until you resupply a correct contact.
- This is not really a bug, more of a gotcha: We have had to explicitly give developers access to all the sharepoint databases including those for the shared service providers. This is necessary to perform actions on the server such as deploying solutions, running the best practise analyser and stsadm. They run in the context of the logged in user and pass those credentials through to the db. The other alternative is you could just log in as the sharepoint admin account. The errors you get through the user interface if you don’t have permission are not descriptive, but if you look in the event log there will be an error indicating which database it is trying to access.
- Incremental content deployment fails with the following error message “Content deployment job ‘Incremental Deploy’ failed.The exception thrown was ‘System.Data.SqlClient.SqlException’ : ‘Violation of PRIMARY KEY constraint ‘PK__#ExportObjects____192930E1′. Cannot insert duplicate key in object ‘dbo.#ExportObjects’. The statement has been terminated.’”. I have found that this occurs if the same page is approved more than once between incremental updates. Microsoft are aware of this issue and are currently working on a hotfix that should be released 11th May 2007 (Hotfix KB 936867).
- Content deployment converts characters into non-english character Â. Microsoft are aware of this issue and are working on a fix. I have been told that the fix will be part of MOSS SP1, likely to be due out sometime around July.
- Some items that are set as ‘Hide’ from the navigation are reverted to ‘Show’ after content deployment. The work around for this is to manually re-hide the navigation items on the presentation server.