Error 80004005 [DBNMPNTW]Specified SQL server not found.

Peter Anning

unread,

Dec 3, 1999, 3:00:00 AM12/3/99

to

I am using IIS with ASP and ADO to connect to SQL Server 7 using a non
trusted connection, ie. the sa user

When I authenticate a user to the web site using basic authentication this
works fine.

When I use the IIS anonymous user IUSR_<server name> I get the following
error:

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNMPNTW]Specified SQL server not found.

The ADODB connection has been set up as follows:

oConnection.Provider = "sqloledb"
oConnection.Properties("Data Source").Value = "(local)"
oConnection.Properties("Initial Catalog").Value = "eboc"
oConnection.Properties("User ID").Value = "sa"
oConnection.Properties("Password").Value = ""
oConnection.Open

I have tried using a Domain account for the IUSR account but this does not
seem to work at all, i.e. it asks for user name and password via basic auth
dialog box and will not accept this user. This user has been created with
all the necessary rights: log on locally etc.

Any one had any problems of a similar nature. MS support have been NO help
so far!

Interati Signature Peter Anning peter....@interati.co.uk
www.interati.co.uk tel 020 7692 7424 fax 020 7692 7445 mobile 079 7060 7376
// interati 14-18 Emerald Street London WC1N 3QA

Prabhakar

unread,

Dec 3, 1999, 3:00:00 AM12/3/99

to

Open the Client Configuration of the SQL Server and Configure for the server
U are accessing it.
I had a similar problem but different in a way. Create a System DSN which
uses accesses he server.

Peter Anning <peter....@interati.co.uk> wrote in message
news:8287od$hq8$1...@supernews.com...

Peter Anning

unread,

Dec 6, 1999, 3:00:00 AM12/6/99

to

Thanks to all who pointed out that TCP/IP was to way to go. I had tried this
already with the SQL client configuration tool, however it did not work,
maybe because I was using OLEDB rather that ODBC (no system DSN).

Microsoft advise this course of action as well they just don't tell you how
to do it. So after much digging I have found the answer.

Dim oConnection
Set oConnection = Server.CreateObject("ADODB.Connection")
oConnection.Properties("Network Address").Value = "127.0.0.1"
oConnection.Properties("Network library").Value = "DBMSSOCN"
oConnection.Properties("Initial Catalog").Value = "MyDataBase"

oConnection.Properties("User ID").Value = "sa"

oConnection.Properties("Password").Value = "SQLPassword"
oConnection.Open

The relevant bits are:
Network Library = DBMSSOCN
This reefers to the TCP/IP netlibrary DLL DBMSSOCN.dll

Network Address = 127.0.0.1
The local server address of the SQL Server. As the TCP/IP net lib is being
used this will now be recognised.

The Article of most interest on this subject was Info Article ID Q193135
available from the MS
http://support.microsoft.com/support/kb/articles/Q193/1/35.ASP

This applies to MDAC 2.0 & 2.1 SP2.

I would still like to know why named pipes don't work, trouble is there does
not seem to be any tool for monitoring what IIS is doing!!!!

My support call is still open with MS, and I am waiting to see if they
manage to come up with anything useful, I doubt it somehow!