-
I've got a program that I've installed successfully on a number of different Operating Systems (95, 98, NT). I've used ADO in the program, so I've got to install MDAC on the older machines. This usually allows the program to run fine.
The problem is, when I install the app after MDAC on an older Win 95 machines, when I run the program and try to show a Data Report, I get the following error:
Run-time error '-2147220992 (80040200)
Class not registered
This is the same error that I get when MDAC is not installed on the other machines that need it, but when I do install it, the error goes away. Why does this only happen on certain machines, and what can I do to fix it?
Matt
-
If I remember correctly, you need install DCOM before installing MDAC on Windows 95 machines. It should not be hard to find that information on the MS website/readme file for MDAC...
Best regards
Franz Hemmer
-
Thanks for the reply, but I've already installed DCOM on those machines.
Interestingly enough, if it's not present on a Win 95 machine, MDAC is supposed to give you a message telling you to install DCOM before installing MDAC. That didn't happen on those machines, so I'm assuming that they already had DCOM on them already. Anyways, just to be sure, I went ahead and installed DCOM on them. No dice.
Anybody else out there with some knowledge? By the way, I ran the component checker available on Microsoft's UDA page on the problem machines, and they both said they had MDAC 2.5 on them.
This can't be a stumper! Looking forward to your replies.
-
i'm developing for win9x, winnt and i have a test pc on which i have win95, win98 and winnt (separate partitions - multiboot).
So, when i install win95 i know for a fact that it doesnt have dcom95 installed.
also - knowing what i do about dcom (not much really), the error you are getting sounds reasonable to be a dcom problem - because one of the com classes is not registered in the registry.
you said you installed dcom - was this dcom95? I am using installshield express to do my installs and it ships with the mdac_typ.exe and the dcom95 exe also. With these files it detects that dcom95 isnt there and installs it.
Can you be sure that the win95 pc has dcom95 on it - you said that it says it has mdac2.5 - but did it say it had dcom95?
I don't mean to sound like a moron, I know what you've said but it just really sounds like a dcom95 prob to me.
my $0.0022 (10% gst)
-
In situations like this, you could always to to register the missing DLL yourself, or even try to install Visual Basic on that/those machine(s).
I've seen times when Package & Deployment wizard was not able to install correctly, but after installing Visual Basic, it worked fine :-) But before that, try upgrading to the latest service pack.
Best regards
Franz Hemmer
-
I'll examine the DLL's that are installed with DCOM95, but I'm pretty sure they're ok. I'm not even sure that the DCOM95 installation was necessary on those machines though, because when I installed MDAC 2.5 first, it didn't give me the message that I needed to install DCOM first. Isn't MDAC supposed to autodetect DCOM and warn you if it's not there:
http://support.microsoft.com/support...-US&SD=gn&FR=0
Thanks for the replys, any other ideas (not DCOM related) sure would be appreciated.
