The error message "Cannot connect to the Configuration database" is displayed in the browser, while "Cannot generate SSPI context" is found in the Event Viewer.
Most of the online blogs and the solutions found on the Microsoft website are helpful, but none of them may be of any help to you.
One way to solve this problem is to:
- Log into the SQL Server box, open up SQL Management Studio and once connected right click on the Server Name and select "Activity Monitor". This should tell you if there are any incoming connections to the SQL Server.
- If you notice there is no activity from the Web Server, then it is pretty obvious the Web Server cannot make contact with the SQL Server.
Thanks to my mate Des for this helpful suggestion.
To test this theory, on the Web Server Desktop create a temporary "Test.UDL" connection file and try to connect to the SQL Server, first using the IP Address of the SQL Server and then using the Name of the SQL Server. Also, use either Windows Authentication of a dedicated SQL Account to connect.
You may be able to connect with the IP Address but not the name of the server or vice versa. This is a DNS issue which is preventing the Web Server from making contact. Immediately get in touch with your Network Administrator to resolve the DNS issue.
The problem may have occurred after installing updates on the Server.
A .UDL file must be able to connect to the SQL Server with the IP Address or the Name of the SQL Server. The .UDL file is created to test connection between the servers only and not for any other purpose.
Any questions please just ask.
Regards
Derek
Helpful links:
Other solutions:
- Check the Application Pool accounts for the Central Administration website and the MOSS 2007 website in IIS and ensure that the domain account used has proper rights on the SQL Server box, and has access to all the MOSS 2007 databases with the DBCreator and Security Admin permissions included.
- Believe you are the best and work just like that!
No comments:
Post a Comment