Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers

Webmaster Forum / ASP / Database Access / March 2008



Tip: Looking for answers? Try searching our database.

Classic ASP connectionstring to SQL Server 2005

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Guy - 13 Mar 2008 16:39 GMT
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?

Thanks
Guy
Bob Barrows [MVP] - 13 Mar 2008 17:06 GMT
> Hi
>
[quoted text clipped - 4 lines]
> '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.

Signature

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.

Guy - 14 Mar 2008 15:55 GMT
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

> > Hi
> >
[quoted text clipped - 16 lines]
> clicking the Services and Connections link. Look for the Remote
> Connections option in the Database Engine node.
Bob Barrows [MVP] - 14 Mar 2008 16:05 GMT
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?

> Thanks for the information. I tried using 'SQLNCLI' but when I did I
> received an error message:
[quoted text clipped - 40 lines]
>> header is my spam trap, so I don't check it very often. You will get
>> a quicker response by posting to the newsgroup.

Signature

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.

Guy - 14 Mar 2008 16:50 GMT
So this connection string is in the VB6 dll? Yes

What is the error message? Provider cannot be found. It may not be properly
installed.

Do you have physical access to the machine running the web server? Yes

If so, can you ping the sql server? Yes

> Both libraries should no be needed.
> So this connection string is in the VB6 dll? No, it makes no difference.
[quoted text clipped - 47 lines]
> >> header is my spam trap, so I don't check it very often. You will get
> >> a quicker response by posting to the newsgroup.
Bob Barrows [MVP] - 14 Mar 2008 17:10 GMT
> So this connection string is in the VB6 dll? Yes
>
> What is the error message? Provider cannot be found. It may not be
> properly installed.

I thought that was the error you received when using SQLNCLI? You are
also getting it when using SQLOLEDB? If so, you need to reinstall or
upgrade MDAC on that server.

> Do you have physical access to the machine running the web server? Yes
>
> If so, can you ping the sql server? Yes

So it's probbly not a network issue.

Signature

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.

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.