Quickbooks Pro 2007 in Build 5582

Discussion in 'Windows Virtual Machine' started by kwwintl, Jan 7, 2008.

  1. kwwintl

    kwwintl Bit poster

    Messages:
    1
    Greetings All,

    I'm having install problems with QB Pro 2007 in Parallels v3.0 build 5582. It seemed to install ok but then I try to start it for the first time it crashes.

    The error message I get has the following info attached:

    Problem Event Name: APPCRASH
    Application Name: qbw32.exe
    Application Version: 17.0.4004.564
    Application Timestamp: 456cccd9
    Fault Module Name: msxml3.dll
    Fault Module Version: 8.90.1101.0
    Fault Module Timestamp: 4666193b
    Exception Code: c0000005
    Exception Offset: 00002030
    OS Version: 6.0.6000.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: 9dcf
    Additional Information 2: 09236575c3205e541ffac75c03a5b7ee
    Additional Information 3: f4f1
    Additional Information 4: 6f0c04ff0f1ed83ad5852205c7ee7848

    I would appreciate any help you more knowledgeable users can provide.

    Cheers,
    -kw
     
  2. mdeeter

    mdeeter Bit poster

    Messages:
    1
    Same Error

    I've installed Quickbooks 2007 on Vista and get the same error. I uninstalled and reinstalled several times. Let me know if you find a solution.

    Error:

    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: qbw32.exe
    Application Version: 17.0.4003.564
    Application Timestamp: 45349d80
    Fault Module Name: msxml3.dll
    Fault Module Version: 8.90.1101.0
    Fault Module Timestamp: 4666193b
    Exception Code: c0000005
    Exception Offset: 00002030
    OS Version: 6.0.6000.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: 9dcf
    Additional Information 2: 09236575c3205e541ffac75c03a5b7ee
    Additional Information 3: f4f1
    Additional Information 4: 6f0c04ff0f1ed83ad5852205c7ee7848

    Read our privacy statement:
    http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
     
  3. Alicia

    Alicia Parallels Team

    Messages:
    683
    Hello,

    have you contacted Microsoft support? This issue seems to be rather widespread among Windows users.
     

Share This Page