Okay, background first. We have an application that is working fine on 99% of the machines we have tested it on. There is one machine, called Norm, that seems to be really stubborn. (No relation to the cheers character of course.)
The connection string I am using is "Provider=sqloledb;Uid=xx;Pwd=xx;Server=Dataserver\Adjuvant;Database=Adjuvant_Aps;". I have also tried the variant of the connect string with "Network Library=DBMSSOCN;" at the end.
We have an initial deployment application that makes sure the registry settings are correct and point to the files and a proper database. When I run this application on Norm, I get the following error almost immediately (within 1/2 second):
Source=Provider, Description=Unspecified error, Result=80004005, WC=0, HC=1240640(0012ee40)
Now, I have looked in tek-tips, and over the web, and have tried or looked at the following:
- out of date MDAC. Forced updated machine to 2.7.
- permissions. Tried under various names on the machine. Using SQL/Trusted mixed mode authentication on the SQL server, so shouldn't be an issue.
- domain name resolution. Editted lmhosts and inserted ip address for Dataserver.
- Forced sockets over named pipes. See above.
Any other ideas out there?
thanks in advance,
Jack
Jack De Winter
Software Developer
MedTel Software
The connection string I am using is "Provider=sqloledb;Uid=xx;Pwd=xx;Server=Dataserver\Adjuvant;Database=Adjuvant_Aps;". I have also tried the variant of the connect string with "Network Library=DBMSSOCN;" at the end.
We have an initial deployment application that makes sure the registry settings are correct and point to the files and a proper database. When I run this application on Norm, I get the following error almost immediately (within 1/2 second):
Source=Provider, Description=Unspecified error, Result=80004005, WC=0, HC=1240640(0012ee40)
Now, I have looked in tek-tips, and over the web, and have tried or looked at the following:
- out of date MDAC. Forced updated machine to 2.7.
- permissions. Tried under various names on the machine. Using SQL/Trusted mixed mode authentication on the SQL server, so shouldn't be an issue.
- domain name resolution. Editted lmhosts and inserted ip address for Dataserver.
- Forced sockets over named pipes. See above.
Any other ideas out there?
thanks in advance,
Jack
Jack De Winter
Software Developer
MedTel Software