Migration on active directory from 2003 to 2008 and SharePoint error Cannot connect to the configuration database.

Question

Hi all,
In advance i`m thankful for your help,
I come across a problem while migrating the Active Directory from Windows Server 2003 to Windows Server 2008 R2,
SharePoint 2010 is getting this error Cannot connect to the configuration database. The same goes for the Administrative page,
Nothing is change in the MySql database, same log in, same server name, i guess it have something to do with the SharePoint Farm,
My question is will reinstalling the SharePoint do the job? Or is there an easy way to get back on my old track?
I`ve try to sync users... no good
PS C:\Users\administrator.SERVERM> if($configManager.IsSynchronizationRunning()
-eq $false)
>> {
>> $configManager.StartSynchronization($true)
>> Write-Host "Started Synchronizing"
>> }
>> else
>> {
>> Write-Host "Already Synchronizing"
>> }
>>
Can someone explain a little bit more about this:
6.     
Can they talk to each other?
Verify that SharePoint is using the correct IP address for the SQL server. To do this, run the ping command on the Windows SharePoint Services server.
Verify that the SharePoint server is obtaining the correct IP address for the SQL server from DNS. To do this, run the
nslookup command from the SharePoint Server.
Make sure that there are no incorrect entries for the SQL server. To do this, examine the Hosts file on the SharePoint server. This file is in the following location:
%systemroot%\system32\drivers\etc\Hosts
On the SharePoint server, look for SQL client aliases. To do this, follow these steps: Click
Start, click Run, and then type cliconfg in the
open box.
Click the Alias tab. By default, there are no SQL client aliases. If you have any aliases for the SQL server, verify that they are correct, or remove them.
Open the SQL Server Configuration Manager (Start SQL Server 2008  Configuration Tools  SQL Server Configuration Manager
Navigate to the SQL Server Network Configuration  Protocols for MSSQLSERVER node in the tree view
Enable TCP/IP and Named Pipes (you’ll be warned that these changes will not apply until the service is shut down)
Aleksandar Delcevski, Web-administrator School of Journalism and Public Relations Jurij Gagarin 17-1/1, 1000 Skopje, R. Macedonia t: + 389 2 3090 004 mob: [phone] [email protected]; www.vs.edu.mk; www.medium.edu.mk; www.unescochair-vs.edu.mk

Answer 1

Hiya,
I don't think it is necessary to reinstall.
You should just confirm that your basic infrastructure is working.
1: On the SharePoint server, open cmd and write ping <SQL server name>
2: On the SharePoint server, open cmd and write nslookup <SQL server name>
Basically the steps outlined here, is the best way to start:
6.     
Can they talk to each other?
Verify that SharePoint is using the correct IP address for the SQL server. To do this, run the ping command on the Windows SharePoint Services server.
Verify that the SharePoint server is obtaining the correct IP address for the SQL server from DNS. To do this, run the
nslookup command from the SharePoint Server.
Make sure that there are no incorrect entries for the SQL server. To do this, examine the Hosts file on the SharePoint server. This file is in the following location:
%systemroot%\system32\drivers\etc\Hosts
On the SharePoint server, look for SQL client aliases. To do this, follow these steps: Click
Start, click Run, and then type cliconfg in the
open box.
Click the Alias tab. By default, there are no SQL client aliases. If you have any aliases for the SQL server, verify that they are correct, or remove them.
Open the SQL Server Configuration Manager (Start SQL Server 2008  Configuration Tools  SQL Server Configuration Manager
Navigate to the SQL Server Network Configuration  Protocols for MSSQLSERVER node in the tree view
Enable TCP/IP and Named Pipes (you’ll be warned that these changes will not apply until the service is shut down)