OpenSync

Home Forums OpenSync OpenSync not working after migrating system to a new hard drive

This topic contains 8 replies, has 2 voices, and was last updated by  Howard Katz 1 year ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #63337

    Howard Katz
    Premium Member

    Running OpenSync 3.0.18 with QuickBooks Enterprise V17R9. Platform was Server 2008R2, upgraded to Server 2012 R2, then migrated the system to a new M.2 SSD. OpenSync initially didn’t show as registered, but was fine when I uninstalled / reinstalled the OpenSync – with the same Registration number. Unfortunately, it no longer seems to be recognized by QBE. When I run jobs (which always used to run successfully), I now get the errors, please see attached screen grabs of the OpenSync and QuickBooks logs.

    How do I resolve this?

    Thanks,
    Howard Katz

    Attachments:
    You must be logged in to view attached files.
    #63343

    Yudel Rosales
    Keymaster

    You have to open each company file on QB and try to add it in order to re-authorize OpenSync to connect to it. If that doesn’t work, you have to delete company file and re-add it.

    #63353

    Howard Katz
    Premium Member

    Removed all Tasks associated with one of our QuickBooks files.
    Removed that File from OpenSync.
    Tried to add it back.
    – QuickBooks crashes!
    Removed OpenSync as an authorized application, try again
    – Application added successfully, then
    – QuickBooks crashes!

    Event Viewer (Application) shows the following error every time this happens:

    Event ID: 1000
    Source: Application Error
    Task Category: (100)

    Faulting application name: qbw32.exe, version: 27.0.4009.2702, time stamp: 0x5a80c1c9
    Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x49b01fc3
    Exception code: 0xc0000005
    Fault offset: 0x000e49ad
    Faulting process id: 0x1a68
    Faulting application start time: 0x01d3d311747e7dd3
    Faulting application path: C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 17.0\qbw32.exe
    Faulting module path: C:\Windows\SYSTEM32\MSVBVM60.DLL
    Report Id: f57f51d7-3f04-11e8-80c9-3417ebc4b07d
    Faulting package full name:
    Faulting package-relative application ID:

    Details:
    qbw32.exe
    27.0.4009.2702
    5a80c1c9
    MSVBVM60.DLL
    6.0.98.15
    49b01fc3
    c0000005
    000e49ad
    25c0
    01d3d31120c3e0d3
    C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 17.0\qbw32.exe
    C:\Windows\SYSTEM32\MSVBVM60.DLL
    93613af1-3f04-11e8-80c9-3417ebc4b07d

    I removed and reinstalled OpenSync (3.0.18), same issue.
    I had removed and reinstalled QuickBooks a couple of days previous, so all software is shiny and new.

    Help?

    #63354

    Howard Katz
    Premium Member

    Problem persists after re-registering msvbvm60.dll

    Attachments:
    You must be logged in to view attached files.
    #63356

    Howard Katz
    Premium Member

    Please ignore the attachment in the last post, I originally had issues with regsvr32.dll (the image) which were resolved simply by running from an elevated command prompt.

    #63358

    Yudel Rosales
    Keymaster

    Did you get it together then?

    #63361

    Howard Katz
    Premium Member

    No! The only “reversal” was on the inability to register MSVBVM60.DLL.

    This is a critical problem affecting a production system, so any help would be greatly appreciated.

    #63362

    Yudel Rosales
    Keymaster

    But on your logs the application that is having the issue is QB:
    Faulting application name: qbw32.exe, version: 27.0.4009.2702, time stamp: 0x5a80c1c9

    #63401

    Howard Katz
    Premium Member

    The new hard drive was not the issue; I believe that upgrading to Server 2012 R2 was.
    See http://synergration.com/forums/topic/error-could-not-start-quickbooks-2147220472/
    I was getting this error as well.
    Long story short: We restored the previous operating environment (Server 2008R2 Standard Edition) from Disaster Recovery Backup, and everything is working perfectly again.

    Is

      anyone

    out there running OpenSync 3.0 on Server 2012R2 successfully?

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.