-
I have a client whose NT4 box will not run an ADO-based VB6 app. Looking thru his uninstall log (St6unst.log), I find nothing that gives a clue. Everything was installed and/or registered.
The kind of errors encountered while running the app are:
430 Class does not support Automation...
3709 Operation is not allowed...
Is this a DCOM-type error? Doesn't NT automatically have DCOM, etc? Is MDAC involved?
We have lots of other clients running similar apps on NT boxes with no problems. Can anyone give me a clue???
Thanks
-
Hi Jeff,
I have the same problem before. It took me a while to figure it out.
Here it is:
I used ADO 2.5. When I use Package and Deployment Wizard. It pick ups ADO 2.1. Therefore when I install on the client machine, ADO 2.1 is installed.
The problem occurs because the program is compile with
ADO2.5. To fix this I installed ADO 2.5 on my client machine and everything work OK.
Please let me know if this can fix your problem. I am very curious to know.
Regards,
TheBao
-
Don't forget to mak sure you have Admin privs on an NT box when installing MDAC or it will all go South when you try to run the application. :(
-
Thanks, guys. According to my client, he does have admin privs.
I looked in the setup.lst file for this project (the list of distributed files) and "msado15.dll" is not in there. Is this a problem? The only "msado" file in there is "msadox.dll".
Additionally, what version of MDAC should they have? They are running NT4. I notice I have Ver 2.50xxx on my machine. Should I have them load that?
Thanks for your help. I am lost!
-
Ok, here's the latest...
Client definitely has the latest MDAC version on his machine. He also has the msado15.dll file. We are both going nuts!
Just a thought...if he installed MDAC as a non-Admin, would that make a difference? Sorry, just grasping for straws.
Anyone???
-
Trust no-one! If possible go yourself and install MDAC with admin privs or have someone you know is reliable do it. Most customers are lucky they find their way home each day :).
