If you have problems connecting, check the troubleshooting to find possible solutions.
1. Make sure the latest SQL Server service pack.
Since many errors in the service pack for SQL Server have been resolved, you have the latest service pack.
To check what SQL Server service pack is running, see the following link: How can I check what SQL service pack am I running?
See also this link: Where can I download packages from the SQL Server service?
2. Verify that the client and server run the same network protocol.
For example, if the client tries to connect to SQL Server using IPX / SPX, and the server only TCP / IP installed, the customer is not able to connect.
3. Verify that the client and server on the network of the library itself.
The client connects to SQL Server 2000 client must be a library network that corresponds to listen to a network server in the library server use. For example, if the client tries to connect to SQL Server using the multi-protocol network library, the server must now be heard on the multi-protocol network library as well. You can use the network library SQL Server client configuration of the client by using the program group Microsoft SQL Server to change. To change the network library server, you can use the network servers in the program group Microsoft SQL Server.
Note. Note that it is registered made the changes to the network server, but will not take effect until you restart SQL Server service.
4. If you can not connect using Windows authentication, verify that SQL Server is not installed on Windows 9x box.
Windows authentication is not compatible with the installation of SQL Server on Windows 9x box.
5. If you get the error message that says Specified SQL server not found make sure you start the real name of SQL Server and SQL Server that is connected.
6. Verify that the database users ‘unique’ is disabled.
If you get the error message indicates that the database is already open and can be only one user at a time when the database user will be disabled.
Contact your database administrator’s your definition of this option database for multiple users to simultaneously connect to the database.
7. Verify that the user exists in the database.
If you display the error message that the user is not a valid user in the database your administrator database to the user the appropriate permissions.
8. Check BSB as the database option is turned off.
If you get the error message indicates that only the owner can access the database, database-only option BOD is enabled. Ask your database administrator to check this option and set database voltage when not only the database owner to access the database can.
9. If you get the error message indicates that the connection failed to ‘user name’ user, you check the spelling of the username and password.
This error message indicates that you tried to communicate with the user name or password. Please contact your system administrator if you forgot your user name or password.
10. If the error message that says Assertion Failed when you try a SQL Server over TCP / IP on a Windows get to step 98 client in connection, install the Client for Microsoft Networks as a computer network components.
The Client for Microsoft Networks need not be the primary network logon. This error was not reflected in Windows 98 Second Edition.
11. You get the error message indicates that the connection is broken when you run the query the linked server using the Microsoft ODBC Driver for SQL Server on the linked server and the name of a unique index to create is part of another unique clustered index.
To avoid this problem, you can change where this index name, or select Microsoft OLE DB Provider for SQL Server to create instead of ‘Microsoft ODBC Driver for SQL Server on the linked server. This error is SQL Server 7.0 Books, Server 2000 does not contain such problems.
12. If users can not access SQL Server 2000 named instance SPX, where a SQL Server listens 2000 server instance by default to IPX / SPX connection, use the SQL Server Network Utility to listen to modify the properties of the instance SPX called on port 33854th
SQL Server 2000 named instance of SQL Server 2000 Standard instance SPX SPX try both on the same port 33 854 SPX listening. So to solve this problem, you have the network library, or select a port of the 33 854 SPX named instance.
13. If you get the error message that says Specified SQL server not found when you try to install SQL Server Query Analyzer to start with the Start SQL Server if stopped option, try again a little later, or SQL Server start up service Manager.
This error occurs when SQL Server needs to create or move a file. Mdf y LDF at the start (eg tempdb.mdf deleted). In this case, the connection attempt is made before SQL Server is started completely wrong.
14. If you error 17824, check network connections or configure the option ‘priority boost’ SQL Server in a default installation.
This error indicates that the SQL Server connection problems when writing to a client. This error can be network problems (such as the client is booted) are caused, or may default detour caused by the priority boost .
15. To isolate connection problems, you can use the shared memory network library using SQL Server 2000 client-server network off.
The shared memory network library is a library of network connections for client / server on the same computer and the network of libraries, the standard used for communication within the computer.