Ouaes Jamali

Recently we had to move the content databases for MOSS. once we had sucessfylly moved the databases over, we started to see the errors(See blow) in the Applicaton log Event ID: 7888 Task Category: Office Server General Source: Office SharePoint Server A runtime exception was detected. Details follow. Message: A duplicate site ID 53e40665-62d0-4316-9192-4d65f247a9a4(http://moss) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue. Techinal Details: Microsoft.Office.Server.UserProfiles.ProfileSynchronizationDuplicateSiteIDException: A duplicate site ID 53e40665-62d0-4316-9192-4d65f247a9a4(http://moss) was found. This might be caused by restoring a content database from one server farm into a different serv...

To save everyone else the potential HOURS of searching trying to figure out why I couldn't get the machineKey section from the web.config for a WSS 3.0 site it turns out that the IUSR_* account does not have read access to the web.config. Once read permissions were granted to the web.config all was fine. Typically this is not an issue but I changed the site to use forms authentication with a custom membership and role provider. Doing this required reading the machineKey from the web.config to encrypt the password. Since the IUSR*_ account was now the default identity and it didn't have read access to the web.config the login would fail and no errors were logged or reported anywhere. It is worth noting that when you have issues in your membership and/or role provider it can be difficult to track down the error since it isn't always logged for some reason. Also, just because it works in a stand alone web application doesn't mean it will work in WSS 3.0 since by defau...