WSS 3.0: showing wrong server as Configuration Database Server

Question

after moving my configuration db to a different DB server I had some difficulties to get the farm up and running again.

now my eventlog is full of errormessages, that the config-db is not reachable on my old db server. Operation / Servers in Farm ... /_admin/FarmServers.aspx is still showing the old db server as config db server

I could create a new wss web application and can see the corresponding records in the objects table in the new config db!?

how can I get rid of this artifact?

TIA Stefan

Answer 1

How did you "move" the config DB? If you restore it from a SQL Server backup it will cause conflicts between GUIDs and other data stored there. You should only restore content and search databases. My advice would be to build up the farm again in the new environment.

Answer 2

Yes, I did detach the Config Database and moved it over to the new server and reconnected it to this server.

Now "Servers in Farm" shows my Old Config Database Server and Instance whereas it as actually picking the infor from the new one and i also checked the registry of the app server and it points to the new one.

I also see using a Sql profiler on my old config server the stored procedure proc_completetimerrunningjobs keeps running, i'm not sure whether its trying to access my content and trying to complete the jobs.

Please Help we are planning getting rid of the Config Database, however we will still have our Contents on the same old Server.