INF: SQL Troubleshooters Available on the Web

ID: Q193088

The information in this article applies to:

Microsoft SQL Server version 6.5
Microsoft SQL Server, Enterprise Edition, version 6.5

SUMMARY

Troubleshooter Wizards that help you solve technical problems with Microsoft products are now available on the Microsoft Support Online Web site. The following Troubleshooter Wizards are available for SQL Server:

Troubleshooting SQL Installation and Connection Problems

Troubleshooting SQLMail Problems

Troubleshooting Slow SQL Query Performance

Help with Problems When Starting SQL Server

Troubleshooting SQL Server Error 1105

Troubleshooting Connectivity Error - "10004 Unable to connect: SQL Server is unavailable or does not exist"

These troubleshooters are available at the following Web location: http://support.microsoft.com/support/tshoot/default.asp

MORE INFORMATION

The remainder of this article provides descriptions of what is covered in each of the troubleshooters listed above.

Troubleshooting SQL Installation and Connection Problems

This troubleshooter covers the following problems:

Installation almost completes or causes "non-critical" errors. Setup does not generate any icons.

Error: "SCM3-1057. Installation could not be completed."

Error: "Could not start MSSQLServer Service on \\servername."

Error 1058: "The specified service is disabled and cannot be started."

Error: "Upgrade failed with a service specific error 1060 - service not installed."

Error 1069 when you start SQL Executive: SQL Executive log on failure.

Error: "SQL 2140: Internal Windows NT error occurred."

Error: "SQL Executive could not be started; it returns service specific error 109."

Error: "ODBCINT.DLL is being used by another application. Installation could not be completed."

Error: "Connection failed - SQL State 01000/SQL Server Error 5 - Access denied."

Error: "OS error:252 message number:10004 severity:9 state:0 unable to connect: SQL server is unavailable or does not exist. Specified SQL server not found. Connection open (read property value)."

Error: "OS error:10061 connection refused."

Troubleshooting SQLMail Problems

This troubleshooter covers the following problems:

SQLMail will not start with a Microsoft Mail postoffice.

SQLMail will not start with Microsoft Exchange Server.

SQLMail will not send or receive messages.

SQLMail causes exception error 35909.

sp_processmail fails, but does not display an error.

Troubleshooting Slow SQL Query Performance

This troubleshooter covers the following problems:

A particular query's performance is slow.

A particular query is slow when it is run as a stored procedure, yet fast when run outside the procedure.

INSERT and UPDATE statements take much longer to run than SELECT statements.

Queries work great alone, but when several people are running queries at the same time, the queries really slow down.

A query used to run fast, but now it's really slow.

The server seems slow overall; can something be adjusted to increase the server's speed?

Should tempdb be put in RAM to increase performance?

Help with Problems When Starting SQL Server

This troubleshooter covers the following problems:

Error message "Unable to Locate DLL. The dynamic link library <bad or missing file> could not be found in the specified path."

Error log contains OS errors indicating that a device could not be found or opened.

Error message "crdb_tempdb: Unable to move tempdb into RAM..." in error log.

SQL Server does not start, but there are no errors.

Troubleshooting SQL Server Error 1105

This troubleshooter covers the following problems:

Run-time 1105 error and object name is Syslogs

Run-time 1105 error and object name is NOT Syslogs

1105 error during recovery on a user database

1105 error during recovery on the master database

1105 error during recovery on the model database

Troubleshooting Connectivity Error - "10004 Unable to connect: SQL Server is unavailable or does not exist"

This troubleshooter covers the following error:

Msg. No: 10004 Severity: 9 State: 0
Unable to connect: SQL Server is unavailable or does not exists.

To determine why the SQL Server client is unable to connect, the OS Error is needed. The OS number is displayed after a failed login attempt in the lower left portion of the ISQL/w window. The OS error number, as well as the function call that failed, is necessary. For example: OS Error 10061 ConnectionOpen(connect()).

The following are the OS error messages covered in this troubleshooter:

Msg. No. 10004 Severity 9 State 0
Unable to connect: SQL Server is unavailable or does not exist. General network error. Check your documentation.
OS Error 10061 ConnectionOpen(connect())

Msg. No. 10004 Severity 9 State 0
Unable to connect: SQL Server is unavailable or does not exist.
Specified SQL Server not found.
OS Error 53 ConnectionOpen(CreateFile())

Msg. No. 10004 Severity 9 State 0
Unable to connect: SQL Server is unavailable or does not exist. General network error. Check your documentation.
OS Error 11001 ConnectionOpen(gethostbyname()())

Msg. No. 10004 Severity 9 State 0
Unable to connect: SQL Server is unavailable or does not exist.
Specified SQL Server not found.
OS Error 252 ConnectionOpen(ReadPropertyValue())

Msg. No. 10004 Severity 9 State 0 Unable to connect: SQL Server is unavailable or does not exist. General network error. Check your documentation. OS Error 1753 ConectionOpen(RPCopen())

Additional query words:


Keywords          : SSrvISQL SSrvNet_Lib 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbinfo

Last Reviewed: March 2, 1999