March 2007 - Posts

• A duplicate site ID ... error in Event Log after moving Content Databases.

  After moving the content database to another SQL Server, I started getting the following message in the event log every hour : "A duplicate site ID ... 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." Nice and simple and even a recommended solution in the error message - except that it wouldn't work. After a lot of additional searching I turned up this command, which did work: stsadm -o sync -DeleteOldDatabases 0 I am reposting it here because of how hard it was to find in the first place.  For what its worth, the full syntax of this is: stsadm -o sync            {-ExcludeWebApps <web applications> |             -SyncTiming <schedule(M/H/D:value)> |             -SweepTiming <schedule(M/H/D:value)> |             -ListOldDatabases <days> |             -DeleteOldDatabases <days>} The original answer was posted by Vikram Garlapati. Posted Mar 01 2007, 10:51 PM by DavidWise with 3 comment(s) Filed under: Sharepoint

• How to determine expiration date of your eval copy of sharepoint

  The other day, I was asked by my management to provide the exact day that our Eval copy of SharePoint 2007 would expire.  Well, I knew it was before Christmas and I could get a rough idea by looking at the timestamps in the 12 hive, but still didn't have the exact date and time.  After some digging, it turns out that Microsoft was nice enough to include the exact date and time right in the Central Administration console, albeit tucked away in a less than intuitive place. When you go to Central Administration -> Application Management -> Office SharePoint Server shared Services -> Check Services enabled in this farm, you will see a message like the one below that lists the exact date and time that your SharePoint eval will go belly up … or whatever it is that SharePoint does when you hit the expiration.  I asked MS about the expiration behavior and they said that it was hard to say exactly what it would do, but it would be something between "stop working entirely" and "disable all admin and publishing functions".  Really! Posted Mar 01 2007, 08:53 PM by DavidWise with no comments Filed under: Sharepoint