App crashes while instantiating AxInterop.VSPrinter8Lib.dll in ASP.Net 64 bit

Posted by: saurabh.asthana on 22 June 2020, 2:09 am EST

  • Posted 22 June 2020, 2:09 am EST

    Hi Team,

    We are using following components for generating reports:
    VSPDF8Lib.dll
    VSPrinter8Lib.dll
    AxInterop.VSPDF8Lib.dll
    AxInterop.VSPrinter8Lib.dll

    We have 2 consumer application:
    1. VB6 windows application
    2. Asp.Net web application

    Components work fine with VB6 application but when we run it with Asp.Net it crashes. Both the applications presently are running on Windows 2019 64 bit server. it works for VB6 but fails for Asp.Net

    here is the error log from Windows Application Event Viewer:
    Faulting application name: w3wp.exe, version: 10.0.17763.1, time stamp: 0xa7ccada2
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x18050098
    Faulting process id: 0xe40
    Faulting application start time: 0x01d6489ccbee9c5b
    Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
    Faulting module path: unknown
    Report Id: a2a97804-33f5-4798-a0da-200bd2a87926
    Faulting package full name:
    Faulting package-relative application ID:
    --------------------------------------------------------------------------------------------
    Faulting application name: w3wp.exe, version: 10.0.17763.1, time stamp: 0xa7ccada2
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc000041d
    Fault offset: 0x18050098
    Faulting process id: 0xe40
    Faulting application start time: 0x01d6489ccbee9c5b
    Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
    Faulting module path: unknown
    Report Id: 1c3f473b-58cf-4c3c-83d5-11b2168b03c8
    Faulting package full name:
    Faulting package-relative application ID:


    Previously we had all the applications (including Asp.net application) running on 32 bit. And everything used to work fine...

    I'm wondering if the issue is due to 64 bit OS, then why VB6 application still working....

    Please suggest what is happening here and recommended solution.

    Thanks
    Saurabh
  • Replied 22 June 2020, 9:25 pm EST

    Hi Saurabh,

    I assume you had already registered the controls as suggested in the article below: https://www.grapecity.com/blogs/registration-of-64-bit-activex-controls

    and, still facing the problem.

    Can you please share the web application demonstrating the issue? Is it something specific to a single project or occurs even for a new web application containing just these two controls? Please confirm.

    Note: ActiveX controls are in maintenance mode and there is no active development going for them.

    Thanks,
    Pragati
  • Replied 23 June 2020, 12:23 am EST

    Hi Pragati,

    Thanks for your reply. we are registering same way in syswow folder as mentioned in the link. but still the issue. And, this is not a new web application. it has been there since years. I mentioned in my previous post that everything used to work until we were on 32 bit OS. Since we are on 64 bit OS, this issue started coming up. For some reasons, it works when called from VB6 application running on same 64 bit machine.

    Code snippet is attached


    Thanks
    Saurabh
  • Marked as Answer

    Replied 25 June 2020, 10:24 pm EST

    Hi Saurabh,

    I would like you to know that we do not support ActiveX controls in Asp.Net environment. It might work in some cases but, has never been tested.

    Since you are targeting Asp.Net application, I would rather suggest you to go for the .Net version of controls. When using an ActiveX control, it is not possible to debug both the .NET and native code at the same time, only one or the other. This is why mixing ActiveX and .NET is difficult to debug.

    Thanks,
    Pragati
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels