Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
automicgina
Starting Member
25 Posts |
 Posted - 2003-10-07 : 17:50:08
|
| Hi, my client's computer is XP standalone. When trying to run osql we get this error:[ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access deniedWhen trying to configure the system DSN we get error 1231, 2, or 10061. Depending on what server name we put it. We tried the computer's name, (local), or just . and none of them worked. The MDAC version is 2.7. We use SQL login, netlib is tcp/ip and dynamic port. Any suggestion? Thanks! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-07 : 18:00:32
|
| Is the SQL Server listening on a port different than 1433? If so, you'll need a registry entry added to the client.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectToString valueName would be server name or even an alias of the serverData would be DBMSSOCN, ServerName, 1439In the above, ServerName could be the name of the server or IP address of the server. 1439 is the port that SQL Server is listening on.If you still can not connect, can other computers on that same subnet connect to the SQL Server just fine. If not, it could be a network problem.Tara |
 |
|
|
automicgina
Starting Member
25 Posts |
Posted - 2003-10-08 : 08:56:20
|
| Thanks for the reply. The problem is that this computer is not part of a network. We are using MSDE 1.0. I have no clue what is wrong here. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-08 : 12:08:08
|
| So MSDE 1.0 is on the local machine? If so, then you might need to put in a loopback cable. I had to do this once when I was installing SQL Server 2000 and the server was not yet connected to the network. I had found a bug article on it at the time but I can't find it now. The solution was to use a loopback cable.Tara |
|
|
|
automicgina
Starting Member
25 Posts |
Posted - 2003-10-08 : 15:41:54
|
| Thanks. Just tried your suggestion with my client. Still can't get it to connect. Any suggestions?I think this may be the article you were refering to:http://support.microsoft.com/default.aspx?scid=kb;en-us;171225&Product=sql |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-08 : 16:07:24
|
| Yes that article is the one. Instead of a loopback adapter, you can also use a loopback cable. It is a cable that is about 2 inches long and is inserted where the LAN connection goes. Go to start, run. Type in cmd and hit enter. Type in:osql -S(local) -Usa -PIf the sa account has a password, then put it after the P.If SQL authenticatino is not allowed:osql -S(local) -EHit enter after. Do you get the same error?Tara |
|
|
|
automicgina
Starting Member
25 Posts |
Posted - 2003-10-09 : 11:35:04
|
| I tried the osql command and it gave me the error SQL Server not exist. I ping 127.0.0.1 and got replies. That's just weird. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-09 : 12:24:15
|
| Is the MSSQLSERVER service started on the machine?Tara |
|
|
|
|
|
|
|
|
connection failed