December 15, 2002 at 4:07 pm
I'm running SQL Server 2000 on a separate machine. If I run my asp page on my XP Pro desktop at work, I can connect to the dbase fine. However, if I run the identical code on my XP Pro desktop at home, I get the error message:
Error Type:
Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found.
/ba.subscribers.asp, line 21
I'm really puzzled because this SQL Server obviously does exist. I can connect to it through SQL client tools from home, the userid and password are correct because I can connect to it from another machine (work).
This is my connection string:
'Create our connection (SQL Server OLEDB Connection)
Set con=Server.Createobject("ADODB.Connection")
con.ConnectionString = "Provider=SQLOLEDB; Data Source=x.x.x.x,1520; Initial Catalog=BoardAnalyst; User ID=x; Password=x"
con.Open
This just started occuring after many months of running successfully. Thanks.
December 15, 2002 at 5:07 pm
Tested connectivity, can you ping the server from home? Someone changed open ports recently?
Andy
December 15, 2002 at 6:51 pm
I can ping the server, the open port is 1520 which I've specified in the connection string. Is there any other place I have to specify the open port?
December 15, 2002 at 8:12 pm
Firewall if you have one, on either side. Can you connect using QA? Using trusted connection? Verify that SQL is really listening on the port, sometimes it wont if there is a glitch when the service starts. You're connecting via VPN, or the server is accessible to outside users?
Andy
December 16, 2002 at 4:26 am
You state you can get to it from home using SQLs client tols so I doubt firewall is the issue here. Try setting up in Client Network utility an alias for the server with TCP/IP connection for the name and specify the port. Then try connecting with the alias as the data source value. May not be treating the Data Source as a TCP/IP address for soem reason.
December 23, 2002 at 1:03 pm
Try adding...
Network=DBMSSOCN;
...to your connection string. That'll force ADO to use IP to connect to the SQL Server.
December 31, 2002 at 11:14 am
The easiest way to test if it's connection issues, copy and paste your connection "ConnectionString "Provider=SQLOLEDB; Data Source=x.x.x.x,1520; Initial Catalog=BoardAnalyst; User ID=x; Password=x" into a text file, and then save the file as say, dsn.udl. Finally, right click on the dsn.udl, it'll bring up the property window, select connection and then click on Test Connection. It should say Test succeeded; otherwise, you'll have to double check the connection string.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply