locked
Automation error in VB6 COM+ with Windows 2008 RRS feed

  • General discussion

  • Hi,

    We have recently migrated our multi tier client application in VB6 as per the details given below.

                                Pre-migration           Post-migration
    OS                       Windows 2003         Windows 2008
    DB                       Oracle 8i                   Oracle 10g
    DSN driver           Oracle 9i client          Oracle 10g client
    Language            VB6                           VB6


    The client exe will be invoked from user's desktop and that will create a server side instance using CreateObject("Class","Server") for the business component deployed as COM+ in MTS. The business component will make a call to data component which is also deployed in the same MTS as another COM+ component. The data component will establish connection with DB using the DSN created on the server and will perform the DB operations.

    This setup is working some time and some times throwing "Automation Error". Once the error came up, it allows us to perform no further operations and we supposed to close the application and reopen it to proceed with further operations. Hence we thought it is a memory leak issue. However the CPU/memory utilization are normal when the error come up and the code seems to be good as all the objects are reset at the end of each method/procedures.

    Unfortunately we could not find a pattern in which the issue is comming up. It allows us to perform the operation and some time and we are getting error some time.

    Using the application log we found that, call to a method in data component failing for some reason from the method in business component. The calling method passes some ado recordsets, string and long data. And in the called method the parameter are also in same order and type. This gave us the impression that this may be due to some data problem. But for the same data it is working some time and getting error after some time.

    Kindly share us your valuable thoughts on this. We know the code has to be migrated to .NET and some architectural changes are also required. Due to time constraint we can't do that now. Hence looking for advice/suggestion.


    Even log details:

    Faulting application dllhost.exe, version 6.0.6000.16386, time stamp 0x4549b14e, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03824, exception code 0xc0000374, fault offset 0x000ab0bf, process id 0x1410, application start time 0x01cc7c1f7716db98.

    The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
    Server Application ID: {B1A8316C-7646-4188-87FD-2714485E8E93}
    Server Application Instance ID:
    {AF9A5E24-2162-404B-9155-D911035B7F08}
    Server Application Name: Data Services
    The serious nature of this error has caused the process to terminate.
    Exception: C0000005
    Address: 0x77682928


    Regards,
    Vimal

    Wednesday, September 28, 2011 8:07 AM

All replies