After we migrated to a new server we received that error. It turned out that the default web user didn't have permission to read from the registry so it couldn't pull the DB login information out to send to Rodopi. We fixed it by giving the default IIS user more rights.

We noticed this after using RegMon and FileMon from sysinternals.

http://sysinternals.com/ntw2k/utilities.shtml



Erik Tijburg wrote:

I haven't seen that exact error, but you can run the "Rodopi Config Utility'
to reset those setting in the registry.


Erik L. M. Tijburg
ISP Support Services
(214) 681-4976
[EMAIL PROTECTED] -----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephen Goff
Sent: Tuesday, November 04, 2003 1:38 PM
To: [EMAIL PROTECTED]
Subject: [Rodopi] OLE DB Error


Rodopi 5.3 SP2 SQL2000 SP3:

I've been seeing the following error in the Application log:

Error 80004005 occurred in module Microsoft OLE DB Provider for SQL Server:
Invalid connection string attribute

There are registry entries at HKLM\Software\Intranet
Software\Rodopi\Connections and
HKLM\Software\Rodopi Software\Instance Settings\SERVERNAME.AbacBill

APP=RODOPI;DATABASE=AbacBill;DRIVER={SQL Server};Network
Address=SERVERNAME;Network
Library=dbmssocn;PWD=*******;Provider=SQLOLEDB;SERVER=SERVERNAME;UID=AbacLog
in;

Has anyone else seen this and know the solution?

Thanks,
Steve




---------------------
To Leave the Rodopi mail list send a message to [EMAIL PROTECTED] with the word LEAVE as the message body.


Please also visit the Rodopi FAQ at http://www.rodopi-faq.com
---------------------




---------------------
To Leave the Rodopi mail list send a message to [EMAIL PROTECTED] with the word LEAVE as the message body.


Please also visit the Rodopi FAQ at http://www.rodopi-faq.com
---------------------







---------------------
To Leave the Rodopi mail list send a message to [EMAIL PROTECTED] with the word LEAVE as the message body.


Please also visit the Rodopi FAQ at http://www.rodopi-faq.com
---------------------

Reply via email to