Below are the main ConnectionStrings I use. I've interchanged the keywords from both (e.g. 'uid' for 'user id' and vice-versa)

ConnString = "provider=SQLOLEDB;user id=svcPerfReporting;password=perfreporting$;initia l
catalog=Perf_Reporting;Data Source=SYDSQLD02\SQLDEV_MORGANITE"

ConnString = "Driver={SQL Server};uid=svcPerfReporting;pwd=perfreporting$;da tabase=Perf_Reporting;
server=SYDSQLD02\SQLDEV_MORGANITE"

And then this is the error I usually get:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver][Named Pipes]Specified SQL server not found. /cba/login.asp, line 20

OR

Microsoft OLE DB Provider for SQL Server (0x80004005) [DBNMPNTW]Specified SQL server not found. /cba/login.asp, line 20

I think the problem has something to do with the instance name, not too sure though... I've also tried replacing the server name with its IP address; as well as using the dot notation (e.g. "server.instancename")

Thank you in advance

Wind is your friend
Matt

__________________
Wind is your friend
Matt

connection string looks fine. What ADO version are you using? Anything less than 2.6 doesn't understand named instances.

pgTips

Thank you for your reply. Without direct admin server access we cant find out the ADO version, or can we. This SQL Server instance is within a bank network. Fairly tightly controlled as you can imagine. I will make efforts to find out the ADO version and get back to you, there is a very goo chance this is the issue?

Thanking you

Wind is your friend
Matt

Matt, something else just struck me when re-reading your post - the error indicates you're using Named Pipes to connect. The problem could be that Named Pipes is an authenticated protocol, but you're not passing any windows user credentials to authenticate. You're just passing a SQL uid/pwd which won't help you get the connection request across the network to the SQL box.

Try connecting through TCP/IP instead as that's not an authenticated protocol. Easiest was to do this is by adding Network Library=dbmssocn to your OLEDB conn string. (see http://support.microsoft.com/default.aspx?kbid=238949 for all the other options)

rgds
Phil

Phil

Thanking you, will try this and have a look at the link.


Wind is your friend
Matt

pgTips

Yes, brilliant ADO (MDAC) was the problem. All is good now this has been updated.

Thanking you kindly

Wind is your friend
Matt