I'm trying to uncover the cause of a problem we're seeing behave inconsistently across several test servers.
I have a VB6 DLL component that was developed in-house (with MTS Enabled) that is instantiated from an ASP page. On some servers it instantiates properly without the component being in a package. On others, an 'object required' error is reported when a method is invoked on the object. All of these servers are running NT4.0, with either SP5 or SP6a installed; there has been no correlation between the SP and the observed behavior.
This component is only one of a dozen or more that are all developed to run under MTS, and all of the rest have been working without a hitch. I've tried comparing the MTS-related code between the buggy class and others, but have not found any discrepancies.
Any ideas? [sig][/sig]
I have a VB6 DLL component that was developed in-house (with MTS Enabled) that is instantiated from an ASP page. On some servers it instantiates properly without the component being in a package. On others, an 'object required' error is reported when a method is invoked on the object. All of these servers are running NT4.0, with either SP5 or SP6a installed; there has been no correlation between the SP and the observed behavior.
This component is only one of a dozen or more that are all developed to run under MTS, and all of the rest have been working without a hitch. I've tried comparing the MTS-related code between the buggy class and others, but have not found any discrepancies.
Any ideas? [sig][/sig]