I've got a client with a single-server MOSS 2007 installation and the Central Admin web site is no longer working (404). The rest of the content databases work fine and the sites are operational. I think they did an improper move of the content databases to another server without properly re-mapping the configuration. I've spent about 3.5 hours already running various STSADM and PSCONFIG commands found on blogs, etc. and I still can't get the Central Admin web to work again. I've since discovered that the admin database is out of synch and while I've been able to create a fresh one from the utilities and then provision the Central Admin web, I still get 404s. How does one get the Central Admin web running again without disturbing the existing content? Does the config DB need to be recreated as well? I'm hoping not because I think this means a full DR of all sites and there are currently 7 of them. How do I safely fix this? Thanks for your help.

Hi Paul, As you have mentioned you were able to create a fresh admin DB , right ? which DB you have created , new config DB or content DB ? What if you create a new config DB using PSConfig wizard ? Did you use the farm admin account to create a config DB? Did you recently change any farm admin password ? And do you have DB Creator and Security admin permissions on farm admin account ? Please check event viewer for details error message when CA gives 404 error.Warm Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/

Hi Paul, Although the configuration database and Central Administration content database can be backed up, restoring backups of the configuration database and Central Administration content database taken from a running farm by using the tools built in to SharePoint Products and Technologies or SQL Server is not supported. This is because data in these databases may not be synchronized with data in other Office SharePoint Server 2007 or Windows SharePoint Services 3.0 databases. Therefore, the tools built in to SharePoint Products and Technologies do not recover these databases during a farm-level restore operation. For your issue, you need to re-create the configuration database and Central Administration content database by using the SharePoint Products and Technologies Configuration Wizard or Psconfig command-line tool, then restore content databases from backups. For more information about restoring databases, see the following article: http://technet.microsoft.com/en-us/library/cc671617(office.12).aspx For more information about recovering the configuration database and Central Administration content database, please refer to the following article: http://technet.microsoft.com/en-us/library/cc287880(office.12).aspx#recovery Thanks, Rock Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.comRegards, Rock Wang Microsoft Online Community Support

Hi Paul, I just want to say hi to know if our suggestion is helpful. If you have any questions, please feel free to reply to the forum. Thanks, Rock Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Regards, Rock Wang Microsoft Online Community Support