I have a VB script that runs from an .asp web page. It's been running fine
for months reading data from a SQL Server database on a Windows 2000 server.
The database needs to be moved to a different server. I moved the database
to the new Windows 2003 server and now the VB script gets this error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.

Both SQL Servers are SQL 2000.

I have a VB6 app that will read the new database just fine. The problem
seems to be with the VB script. Any ideas on what could be the problem?

Thanks,
Mark

Re: VB Script getting error connecting to SQL Database by Bob

Bob
Fri Apr 30 19:38:10 CDT 2004

Mark Brown wrote:
> I have a VB script that runs from an .asp web page. It's been
> running fine for months reading data from a SQL Server database on a
> Windows 2000 server. The database needs to be moved to a different
> server. I moved the database to the new Windows 2003 server and now
> the VB script gets this error:
>
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
>
> Both SQL Servers are SQL 2000.
>
> I have a VB6 app that will read the new database just fine. The
> problem seems to be with the VB script. Any ideas on what could be
> the problem?
>
> Thanks,
> Mark

Try using the SQLOLEDB provider instead of the ODBC provider. You may need
to add the setting to make the connection by TCP/IP instead of named pipes.
See www.able-consulting.com/ado_conn.htm for connection string details

http://www.aspfaq.com/show.asp?id=2009 - 80004005 errors

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"



Re: VB Script getting error connecting to SQL Database by Mark

Mark
Mon May 03 08:21:39 CDT 2004


"Bob Barrows" <reb01501@NOyahoo.SPAMcom> wrote in message
news:Ott2RSxLEHA.3872@TK2MSFTNGP12.phx.gbl...
>
> Try using the SQLOLEDB provider instead of the ODBC provider. You may need
> to add the setting to make the connection by TCP/IP instead of named
pipes.
> See www.able-consulting.com/ado_conn.htm for connection string details
>
> http://www.aspfaq.com/show.asp?id=2009 - 80004005 errors
>

Thanks, using TCP/IP connection did the trick!

Mark