HI Mark,
Did you move the SharePoint_Config database? This is a bad idea and is not recommended to do at al as it contains very detailed machine/server details (server names, SID's, etc). Only Content databases should be moved between servers and the configuration databases should be rebuilt from the SharePoint Wizard from scratch. Cheers, DB From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Leonard Sent: Wednesday, 27 August 2008 2:40 PM To: listserver@ozmoss.com Subject: [OzMOSS] Moving the Sharepoint_Config Database to a new Server I've just completed the exercise of moving the MOSS 2007 system databases from one SQL Server to another. I've struck the problem of event id 3760 in the server application log, on the MOSS server, where it's trying to locate the Sharepoint_Config database on the old (original) server. Web searches on this problem seem to suggest the only fix for this is to hack the Objects table in the Sharepoint_Config database and replace the details for the old database server entry with those of the new database server. Has anyone else had this problem and had to go down this path or is there another way? _____________________________________ Mark Leonard ______________________________________________________________________ This email has been scanned for Wollongong City Council by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
