Hi,
Our app uses a 3rd party dll with ActiveX controls that is installed and
registered by the setup.
We have a customer who has installed on Win2k and is getting this exception
when the app tries to use the dll (stack trace below). Other features
of our app work correctly. We have not been able to repro the issue on our
own
Win2k test box. Below the stack trace are some notes about things we tried and
the results. Any help will be appreciated!!
Stack trace
------------
01/04/05 13:06:11.081 [Error] Caught an unhandled exception.
(System.InvalidCastException: QueryInterface for interface
ESELLERATECONTROL350Lib.IeSeller failed.
Server stack trace:
at ESELLERATECONTROL350Lib.eSellerClass.ValidateSeria lNumber(String
inSerialNumber, String inNameBasedKey, String inExtraDataKey, String
inPublisherKey)
at bw.ValidateLicense(String serialNumber)
...
at
System.Runtime.Remoting.Messaging.StackBuilderSink .PrivateProcessMessage(MethodBase
mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,
Object[]& outArgs)
at
System.Runtime.Remoting.Messaging.StackBuilderSink .AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvok eHelper(Message
reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invo ke(Object NotUsed,
MessageData& msgData)
at a.EndInvoke(IAsyncResult result)
at bf.a(IAsyncResult ))
a at offset 155 in file:line:column <filename unknown>:0:0
a at offset 136 in file:line:column <filename unknown>:0:0
a at offset 133 in file:line:column <filename unknown>:0:0
InternalInvoke at offset 0 in file:line:column <filename unknown>:0:0
InternalInvoke at offset 318 in file:line:column <filename unknown>:0:0
DynamicInvokeImpl at offset 52 in file:line:column <filename unknown>:0:0
DynamicInvokeImpl at offset 62 in file:line:column <filename unknown>:0:0
InvokeMarshaledCallbacks at offset 511 in file:line:column <filename
unknown>:0:0
...
What we tried (no repro on our test box):
- had user disable firewall (dll method requires internet) and virus
scanning. No effect.
- installing with virus scanners running has not been a problem, that we
have observed. Are there settings that prevent ActiveX controls from being
registered?
- delete (rename) the interop dll. Our app fails to run at all. Different
error.
- delete (rename) either or both of the 3rd party dlls. Installer
automagically reinstalls them.
- unregister the dlls. App fails to run, different error message.
