Re: Classic ASP connectionstring to SQL Server 2005

Both libraries should no be needed.
So this connection string is in the VB6 dll? No, it makes no difference.
I'm still in the dark as to the failure mode when using SQLOLEDB. What
is the error message?
Do you have physical access to the machine running the web server? If
so, can you ping the sql server?

Guy wrote:
Thanks for the information. I tried using 'SQLNCLI' but when I did I
received an error message:

ADODB.Connection error '800a0e7a'

Provider cannot be found. It may not be properly installed.

I also checked to see if TCP/IP is enabled and it is. I noticed that
there is an option to enable both TCP/IP and name pipes. Is that an
option I should enable instead? Did I mention that I am accessing the
database from an ASP to VB6 DLL to SQL Server 2K5? I'm not sure if
that matters but I thought I should mention it. Any other suggestions
would be greatly appreciated.

Thanks
Guy
"Bob Barrows [MVP]" wrote:

Guy wrote:
Hi

I am supporting a classic ASP application that uses SQL Server 2000
on the backend. I now need to contect to a SQL Server 2K5 database.
I currently use conntectionstring: Provider= sqloledb.1;Persist
Security Info=False;User ID='XXX';Password= 'XXXX';Initial Catalog=
'XXXXX';Data Source='XXXX';Connect Timeout='25' which does not work.
Is there another connectionstring I should use?


That's pretty much what I use. You can also use the SQLNCLI provider
instead of the SQLOLEDB one, but if SQLOLEDB isn't working, then
neither should SQLNCLI. (btw - always endeavor to describe your
symptoms without using the words "not work" or "not working" or
similar non-descriptive verbiage - error messages are always
helpful).

Is TCP/IP enabled on your sql server? I think you have to use the SQL
Server Surface Area Configuration tool (Start>SQL Server
2005>Configuration Tools) to enable it ... yes, it's accessed by
clicking the Services and Connections link. Look for the Remote
Connections option in the Database Engine node.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get
a quicker response by posting to the newsgroup.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.


.

Relevant Pages

  • Re: Error when installing SQL server 200 on SBS 2003
    ... it seems this newsgroup is helpful to all the SBS ... Microsoft CSS Online Newsgroup Support ... Error when installing SQL server 200 on SBS 2003 ... | In fact I got the same error message when upgrading to SQL SP4 ...
    (microsoft.public.windows.server.sbs)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... connections need to be returned to the pool to be ... Enterprise version of SQL Server 2000. ... server user login to be sure that it is not mixed with other running clients). ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... communication between ODBC (OLEDB and Native Client, ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)