Connecting to SQL Server Mgmt Console in Win98

[PCSurgeon69]

Please Help... I installed SQL Server 7 on my Win98 Machine. I keep getting error after error when attempting to connect. I recieve the following error:
A connection could not be made to 'servername' - General network error. Check your network documentation.
ConnectionOpen(connect())..
Please verify SQL Server is running and check your SQL Server registration properties (by right clicking on the 'servername' node) and try again.
I've attempted to delete, the re-register a new servername, and even attempted to add an ODBC Driver in the control panel, all to no avail.
Thanks...

 

[foxdev]

You are trying to get a connection to the SQL Server running on the same box using EM, correct?

Try these:

* Using Client Network Utility, make sure you are setup to use Named Pipes
* Ensure your SQL Server is running (the green status should appear in your status bar icon)
* Try connecting via Query Analyzer and see if you get success
Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:

http://www.lowcostprints.com

 

[PCSurgeon69]

Hi Mr. Bradley,
I've gone to the M$ knowledgebase, did the trouble shooting steps, pinged the PC in DOS, got the IP address, went in and made the proper adjustments in the Client Network Utility, saved the changes, attempted to open SQL Server (the program opens, just will not connect to anything), went to connect to the local server (I am not on a networked machine) and get the following error:Unable to connect to server \\servername:

Server: msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.

This is why I cannot connect, no matter what steps I've taken to rectify the situation.

I attempted to install SP3 to see if this would fix the problem, and then it asked me for an sa password, and I don't have one, attempted to go ahead with the procedure (even with a blank sa password) and it won't let me proceed.

Can't get much funner than this.

Thanks.

 

[foxdev]

went to connect to the local server
ODBC SQL Server Driver][TCP/IP Sockets]

Don't use TCP/IP to connect to a local (same PC) SQL Server instance. Use Named Pipes.

Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:

http://www.lowcostprints.com

 

[PCSurgeon69]

Using Named Pipes, made the adjustments, tested, still no go... I attempted to start services in the Service Manager, however, there are No Services to choose from in the list.

Thanks.

 

[foxdev]

Ahh...the plot thickens. Try going to a command prompt and running the EXE directly (MSSQLSRVR.EXE, or something similar - I don't recall the exact spelling). Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:

http://www.lowcostprints.com

 

[ValJean]

I am having the same trouble, but the pinpoint of my problem is that we just had an IP conversion. All of our static IP addresses changed, including our main server. We're all in the same domain, but the problem started occuring after the IP conversion.
I'm in a client-server environment, and my computer is the only one that is having troubles connecting to SQL Server in the whole building (no matter who I log in as). I thought maybe it had to do with DNS resolution, but that's not right, since my coworkers can connect fine. So, I guess something happened on my [Win98] machine possibly with ODBC or drivers or something.
Let me know if you get any more help with this or something else to try.
Thanks,
Valjean_Elander@stlouisco.com