asked on

Error 430: Class does not support Automation or does not have the expected interface

I've built my vb6 app on win2k and installed on NT 4. The installation has no problems, but when I try to start the app I get '430 "Class does not support automation" ' error.

I have not renamed any dlls or exe's nor have I manually moved files. I used the deployment setup from vb6.

Richie_Simonetti

What dll is your app using?
Also, check for dll compatibility, not sure that ALL dll from W2k should works on NT.

defy_boy

i noticed i get that when i was using the windows scripting host from my win2k to my winXP, i downloaded wsh again and installed and all was fine

aeklund

Automation errors are usually caused by dlls or ocx files not installed.

Richie_Simonetti

i would like to agree with aeklund, but error 430 appears as a different dll/ocx version rather than "can't create object" which is always the case when a dll/ocx is missing or not registered.

pcumberbatch

Getting the same error with programs packaged by the deployment wizard. Apparently MDAC_TYP has been updated. Investigating further.
Error also occurs when running project on some machines.

CleanupPing

Hi acidxwarp,
This old question (QID 20562982) needs to be finalized -- accept an answer, split points, or get a refund. Please see http://www.cityofangels.com/Experts/Closing.htm for information and options.

GPrentice00

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:

-->PAQ - no points refunded

Please leave any comments here within the next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER

GPrentice00
Cleanup Volunteer

GPrentice00

claim them

ASKER CERTIFIED SOLUTION

YensidMod

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial