Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SharePoint 2003 problem

  Asked By: Jameson    Date: Jan 26    Category: Sharepoint    Views: 705

Yet another problem that happened while I was away. The old SharePoint
site (2003) now responds with the error:

Unable to connect to database. Check database connection information and
make sure the database server is running. For tips on troubleshooting
this error, search for article 823287 in the Microsoft Knowledge Base at
http://support.microsoft.com

Now the first thing I did was read the KB article and follow the
suggestions. As it happens the first one solve my problem indirectly.
The problem seems to be that the SQL instance has been renamed. I have
no idea how SQL people do this and they are denying all knowledge of it.
However, the SharePoint configuration thinks the instance is
VSSQL01\PilotSPS01 and that's what it has been for a couple of years.
When I check on the SQL server however, I find that it is now called
VSSQL01\PilotSP01. There is a missing S now. Anyway, I thought it would
just be a bit of configuration and all would be well. In Central Admin
I've used "Set Default Content Database server" and "Set Configuration
Database server" to change the name of the SQL instance being used. This
has had some effect because now Central Admin starts up pretty quickly
and the links all work whereas before it was very slow and some of the
links didn't work. However, users still get the same error above and
when I check in event viewer it is reporting errors using the old name
of the SQL instance (with the additional S). I guess there must be
somewhere else that the content database server instance is stored but I
can't find it. Does anyone know where this is?

Share: 

 

No Answers Found. Be the First, To Post Answer.

 
Didn't find what you were looking for? Find more on SharePoint 2003 problem Or get search suggestion and latest updates.




Tagged: