"Provider not found" error

I have an application that works just fine on several computers.
{Delphi6 with ADO Components }
We have a MSSQL2K DB with MDAC 2.81.1117 on EVERY machine.
However, on one of them, when I try to run the program, I get a
"Provider not found. It may not be properly installed" error,
then an "Error in the DLL" message box.
We can access database through Enterprise manager AND I can create an
ODBC DSN to the database in question on the problem machine just fine.
Let me explain here what we've attempted.
1. Reinstalled SQL Server2K
2. Reinstalled XP SP2
3. Installed Delphi fully
4. Tried MDAC 2.8 install, won't because of XP SP2,
says already installed
5. tried using DSN file .vs connectionstring
6. tried clearing the provider from connectionstring
7. tried creating ODBC DSN and connecting that way.
All of these result in same "Provider not found" error. When I opened
the source on this machine in Delphi and tried to build the
connectionstring there, I got an error stating that the provider was not
installed at all.
I can verify that sqloledb.dll IS installed in the
C:\Program Files\Common Files\System\Ole DB directory and registered
I can verify that mdasql.dll IS installed in the
C:\Program Files\Common Files\System\Ole DB directory
I can verify that mdatl3.dll IS installed in the
C:\Program Files\Common Files\System\Ole DB directory
I can verify that registry entires are correct for SQLOLEDB provider.
I can also verify that the directory
C:\Program Files\Common Files\System\Ole DB is in the search path.
This is a critical time accounting appplication for our employees
that works on dozens of other machines and for it to not work on one
certain machine is very puzzling. We can not understand what is so
"special" about this one.
Any ideas?
The Cleaning Wonder Boy wrote:
> *I have an application that works just fine on several computers.
> {Delphi6 with ADO Components }
> We have a MSSQL2K DB with MDAC 2.81.1117 on EVERY machine.
> However, on one of them, when I try to run the program, I get a
> "Provider not found. It may not be properly installed" error,
> then an "Error in the DLL" message box.
> We can access database through Enterprise manager AND I can create
> an
> ODBC DSN to the database in question on the problem machine just
> fine.
> Let me explain here what we've attempted.
> 1. Reinstalled SQL Server2K
> 2. Reinstalled XP SP2
> 3. Installed Delphi fully
> 4. Tried MDAC 2.8 install, won't because of XP SP2,
> says already installed
> 5. tried using DSN file .vs connectionstring
> 6. tried clearing the provider from connectionstring
> 7. tried creating ODBC DSN and connecting that way.
> All of these result in same "Provider not found" error. When I
> opened
> the source on this machine in Delphi and tried to build the
> connectionstring there, I got an error stating that the provider was
> not
> installed at all.
> I can verify that sqloledb.dll IS installed in the
> C:\Program Files\Common Files\System\Ole DB directory and registered
> I can verify that mdasql.dll IS installed in the
> C:\Program Files\Common Files\System\Ole DB directory
> I can verify that mdatl3.dll IS installed in the
> C:\Program Files\Common Files\System\Ole DB directory
> I can verify that registry entires are correct for SQLOLEDB
> provider.
> I can also verify that the directory
> C:\Program Files\Common Files\System\Ole DB is in the search path.
> This is a critical time accounting appplication for our employees
> that works on dozens of other machines and for it to not work on one
> certain machine is very puzzling. We can not understand what is so
> "special" about this one.
> Any ideas? *
Hi
I too have faced the same problem on one of my clients machine
i have treid all that you have described above but nothing seems to
work.
But the solution is simple
You first need to delete the folder
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Setup\ExceptionComponents
in the Registry and then try re-installing MDAC2.6SP2
Reboot and the problem is gone.
It has worked for me on Win 2000 OS, i hope this works for you
Thanks
Ganta.
Ganta
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message974581.html