March 25, 2005 at 11:32 am
I am pure DBA, not developers. Today a developer asked me why his web app couldn't see SQL. From IIS server I can query SQL on a separate box so IIS can see SQL. I replaced his connection string with another one then it worked fine. Would you guys tell me why his string didn't work? The string has been working fine for months until this morning. Below is his string (didn't work) and new string (did work):
sConnStr = "Provider=SQLOLEDB; Data Source=xxxxx;Password=xxxxx;User ID=xxxxx;Initial Catalog="&Database&"; Network Library=DBMSSOCN; ID:Q167833"
sConnStr = "Provider=SQLOLEDB.1;Password=xxxxx;User ID=xxxxx;Initial Catalog="&Database&";Data Source=xxxxx"
Thx.
March 25, 2005 at 1:18 pm
Not sure what the "ID:Q167833" is, as that is not listed anywhere as a connection property (might have been WSID: if your workstations are named in that format?).
"Network Library=DBMSSOCN", is the default (TCP) library, so not having that should not have any effect.
So that leaves Provider as the only real difference. I've seen the ".1" sometimes appended, but not sure why. Could be that an updated version of MDAC was installed (appending the .1 after the name), and then the old version was uninstalled recently?
Mark
March 25, 2005 at 1:25 pm
I tried removing and adding .1 but it didn't change. Silly thing is it worked yesterday.
ID:Q167833 is from the original string he got from internet. It's existing also didn't make any change.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply