"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!
The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

'OraOLEDB.Oracle.1' is not registered on local machine

Hi all of you,

Primary platform is Framework 2.0 running over XP.

I've got an issue with a SSIS package which uses Oracle Provider for OleDB:

Test connection failed because of an error in initializing provider 'OraOLEDB.Oracle.1' is not registered on local machine

Nevertheless, MS Ole DB Provider for Oracle works fine. Let me know where am I failing.

Thanks in advance,

Try reinstalling the Oracle client.|||

Thanks for your answer Phil.

I've got a question.. If I do such thing, my tnsnames.ora will be destroyed? 'suppose so

Anyway, I think that my problem is other one..

|||Copy your tnsnames.ora file to another name and then restore it when done. Which is something you should be doing anyway -- backing it up.

You can try just reinstalling the OLE provider: http://www.oracle.com/technology/software/tech/windows/ole_db/index.html|||

Hi Phil,

Thanks indeed. It works fine. I'm sorry for my scepticism.

|||

Hi Phil.

I am also having this problem, made sure that the ACL are read and execute for ASPNET, IUSR, IWAM users on the server. The app is .NET 2.0 by a vendor that is using the following connection string. names change to protect the innocent.

Provider=OraOLEDB.Oracle;Password=pass;User ID=user; Data Source=ds'/>

Unfortunately the vendor has no answers...

My question is that I have been told by my DBA that reinstalling doesn't always reinstall correctly as the registry entries still exists. Am I being told correctly? Also, If I reinstall, am I creating a new Oracle_Home that I would have set up in the OBDC administrator.

|||

n2magick wrote:

Hi Phil.

I am also having this problem, made sure that the ACL are read and execute for ASPNET, IUSR, IWAM users on the server. The app is .NET 2.0 by a vendor that is using the following connection string. names change to protect the innocent.

Provider=OraOLEDB.Oracle;Password=pass;User ID=user; Data Source=ds'/>

Unfortunately the vendor has no answers...

My question is that I have been told by my DBA that reinstalling doesn't always reinstall correctly as the registry entries still exists. Am I being told correctly? Also, If I reinstall, am I creating a new Oracle_Home that I would have set up in the OBDC administrator.

Right, but are you using SSIS? If not, I'm afraid I cannot help you... It seems that you have several layers that could be causing you issues.|||

Thanks Phil for answering my question. No I am not using SSIS. Just happen on the post doing a search trying to find the answer to my problem.

Thanks again for your prompt answer.

LuAnn