COM COmponent Error
I have developed a VB COM component on Windows 2000 Pro running IIS 5.0 that runs fine.
When I register this component on another Web Server (the live Production Web Server) running IIS 4.0 on Windows NT I receive this error
"DealerUpload error '800a01ae'
Class does not support Automation or does not support expected interface
/MST/DealerURL/TransferData/TransferData.asp, line 6"
Dealer Upload is the name of the dll. At line 6 the instance of the object is attempting to invoke a method right after the component has been created (using Server.CreateObject("ClassID"). So it appears that the object is being created it just can't invoke the method.
Can someone help me with this??
Thanks
[773 byte] By [
bgibbons2] at [2007-11-17 16:57:40]
# 1 Re: COM COmponent Error
Sounds to me like you are missing a dependancy - that's why its falling over when you're invoking a method. Run 'Depends' on the development machine and check that all the dll's & ocx's are registered on the target machine. Other than that, I have no suggestions.
# 2 Re: COM COmponent Error
The error you are getting is a typical COM+/MTS error. The component expect a specific interface, and don't allow direct creation (they do, but you won't get any good of it). You must do this through their interface. If for some reason, you made a change to the interface (like changing the datatype of a parameter, or the number of methods, or the number of parameters, or ...), you will break the interface, and each component that uses the interface is to be recompiled before it can be used again.
Cakkie at 2007-11-10 0:24:13 >
