msjro.dll failing to register

[David RH]

Hello

I have an app that uses ADO to manipulate an access DB and JRO to compact and repair afterwards.

Lately I've been having users get an error message during install that msjro.dll failed to register during the install with failure code 0x3.

These are vista machines. Haven't seen this on an XP machine yet.

Using the following refs:
Microsoft jet and replication objects 2.6 library
Microsoft activex data objects 2.6 library

Thanks

David

[si_the_geek]

Thread moved to Application Deployment forum

There is a newer version of ADO which is pre-installed on Vista, so you should not be installing that.

I've checked what Jet downloads are available (via the MDAC link in my signature), and it seems nothing new has been released for a few years, and there is nothing for Vista (but there is for XP etc). This makes me think that Vista has it pre-installed too, and I presume this is also the case for JRO - so you should check if that is the case (preferably on a new Vista installation).

[dilettante]

msjro.dll

The file msjro.dll is a component from Microsoft Data Access Component(MDAC), and the MDAC is included in Operation System which is later the windows 2000 with Server Pack 4. I suggest you exclude this file by set the Exclude property to true.

Actually Windows DAC instead of MDAC, but the point is you don't try to deploy things like ADO, JET, and JRO anymore.

[David RH]

msjro.dll

Actually Windows DAC instead of MDAC, but the point is you don't try to deploy things like ADO, JET, and JRO anymore.

Does this apply to vista only or to pre vista OS also?

I have users with both vista and xp and maybe 2k, 98, and me.

[si_the_geek]

I've had to update MDAC on Windows 2000 before (not sure which SP), so I'm fairly sure that it is only Vista and XP (which both have MDAC/Windows DAC 2.8 or later), and based on the quote Windows 2000 with SP4 or higher.

[dilettante]

That's true, for anything "unsupported" (before Win2K SP4) MDAC deployment is still an issue. I assume people use some sort of installer logic to detect before deploying MDAC and Jet now (since Jet was unbundled back around MDAC 2.5). Really old machines (Win95) also need DCOM deployed before MDAC can be updated.

If you use a Windows Installer package (.MSI) Microsoft offers this: FILE: Install DCOM and MDAC Through a Windows Installer Package. To check for an MDAC after 2.1 though you'll have to modify and comple the C source.

It is probably also possible to modify the Setup1.exe use by PDW to do the necessary checks and install the necessary set of components, but this means including the DCOM95/98, MDAC 2.x, and if needed Jet 4.0 packages when you distribute your application. This gets more complicated, since Jet comes in different flavors for different OSs and each takes a separate installer package: MDAC Downloads.