/build/static/layout/Breadcrumb_cap_w.png

VZAccess 7.7.21 APPCRASH Issue

Hi, I am trying to package VZAccess Manager 7.7.21 and "VZAM_7.7.1.10_2754a_RIM.exe" is the installer from vendor. While running this it extracts two MSIs - one for Blackberry USB and Modem Driver and another for VZAccess Manager. Both the MSIs install separately and runs fine. 

For VZAccess Manager, during first time run, it tries to detect the hardware, and fails (since I am using desktop test terminal w/o any wireless adapters/cards) and crashes with below Error Msg:

Problem signature:

  Problem Event Name:APPCRASH

  Application Name:VZAccess Manager.exe

  Application Version:7.7.1.10

  Application Timestamp:4ee12cd7

  Fault Module Name:SMWiFiEngine.dll

  Fault Module Version:2.19.3.180

  Fault Module Timestamp:4e4a7c33

  Exception Code:c0000005

  Exception Offset:00003659

  OS Version:6.1.7600.2.0.0.256.48

  Locale ID:1033

  Additional Information 1:0a9e

  Additional Information 2:0a9e372d3b4ad19135b953a78882e789

  Additional Information 3:0a9e

  Additional Information 4:0a9e372d3b4ad19135b953a78882e789

 

If I simply install it through the given exe, this issue doesn't occur (with same desktop test terminal). Tt tries to detect the hardware, and fails same as above condition. But doesn't not Crash, and Manager Interfaces can be used normally.

Does anyone faced this issue? Please share if you have experienced it and have solutions.

Thank you


0 Comments   [ + ] Show comments

Answers (1)

Posted by: pjgeutjens 12 years ago
Red Belt
1

you could try to do a gap captupe, first installing the MSIs, then capturing a run of the setup ontop of that, and checking if anything (relevant) is added by the setup that is not contained in the MSIs


Comments:
  • hmmm ... yes doing the same right now ... thank you pj ... will let you know if any progress on it ... - dshilpakar 12 years ago
  • nice suggestion, that is a perfect way to check what is going inside the EXE. - adilrathore 12 years ago
  • Well, I tried installing the Driver MSI and then VZAccess Manager. And then ran Repackager to run the EXE. Installation runs till Driver but for Manager it says the enterprise version is already installed and stops. Only thing I captured here is few files for Driver which are already there and one reg key.
    So tried having those files and reg key again with MSi installation, still the issue continues.... - dshilpakar 12 years ago
  • try to delete the footprint the msi left in the registry at HKCR\Installer\Products and HKLM\Software\Microsoft\Windows\currentVersion\Uninstall after you install your MSIs

    This should prevent the detection of the existing installation - pjgeutjens 12 years ago
    • I tried several of times to figure out the differences as per how you suggested but all in vain. Even tried repackaging the driver installation phase (install with source .exe, continue installing drivers and stop till UI appears to install for VZAccess Manager. Normally If I stop at this point and install ZVAM msi, the application does not crash. But with the repackaged driver msi then VZAM msi, it still crashes ...

      I just wonder if no one has faced this issue yet? - dshilpakar 12 years ago
  • You can also request the MSI for VZAccess by request from your Verizon service rep. You'll need a login for the Enterprise VZAccess Portal. Once there you can download all the driver MSI's for Verizon devices along with the VZAccess MSI that contains many of them. - Trinity 12 years ago
  • Seemingly, we do not have login access to the Enterprise Portal ... - dshilpakar 12 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Link

Related Links

Post

Related Posts

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ