• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1116
  • Last Modified:

MSDE Databases will not start in SBS 2003

I have a Windows SBS 2003 server. The three MSDE instances (MSSQL$MSFW, MSSQL$SBSMONITORING, and MSSQL$SHAREPOINT) will no longer start.  This first occurred after a recent restart of the server for a hardware replacement.  When attempting to start any of these services, I receive the message "Error 1053: The service did not respond to the start or control request in a timely fashion." The System log has two events logged when this occurs (7009 and 7000); the 7000 event give the same error as above, but the 7009 says "Timeout waiting for the service to connect."  Also,the application log has event 1000 for the Windows Sharepoint Service:"Unable to connect to the database STS_Config on Servername\Sharepoint"

When I attempt to connect to the databases in Management Studio, I receive

Cannot connect to SERVER\MSFW.

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

I was able to get the server functioning to some degree by changing the logging options in ISA 2004 to flat file and removing the dependency of the Windows Firewall service on the the MSSQL$MSFW instance; however this is not the solution I need.

Thanks.
0
ITGhost
Asked:
ITGhost
  • 4
  • 2
1 Solution
 
venk_rCommented:
Check 2 things initially
1.TCP IP Enabled
2.Check the SQL Service account
If you are not using a domain account as a service account (for example if you are using NETWORK SERVICE), you may want to switch this first before proceeding.

Note: Try to move to the SQL Express version if possible . As MSDE are old versions and they have more limitations.

0
 
ITGhostAuthor Commented:
Okay, TCP IP is enabled.  The SQL instances are using a local administrator account.  I guess I don't know what you mean in the last part "Try to move the SQL Express version if possible."
0
 
venk_rCommented:
Well , that may be bit out of context actually. I was saying it would be good to migrate to the SQL Express edition of SQL Server at some point.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
ITGhostAuthor Commented:
Anyone else have any ideas?
0
 
ITGhostAuthor Commented:
Found that MSVCP71.dll was missing. Copied from working 2003 server.
0
 
ITGhostAuthor Commented:
This was the actual solution.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now