Error Code 00000 51870

Adam Dardick
Adam Dardick Member Posts: 5
edited December 2019 in Reckon Accounts (Desktop)
Dear community, one of the team has been receiving this error code (00000 51870)  for the past month, shutting down and restarting Reckon. (Reckon Accounts Enterprise (40user). This can happen several times a day. I have tried an un-install and re-install to no success. I can't find any other community threads with this error code. Please help.
Thanks
Adam

Comments

  • DebonAir
    DebonAir Member Posts: 392
    edited December 2019
    If this is only on one computer, you could try to reinstall it in different location on the same computer.

  • Rav
    Rav Administrator, Reckon Staff Posts: 15,305 Community Manager Community Manager
    edited December 2019
    Hi Adam,
    Welcome to the Community!

    My first suggestion would be to test the file integrity of your QBW file by running the verify and rebuild process. Follow up on any errors that are presented here and then check if the issue persists after that.

    How to Verify Data and Rebuild Data for a company data file in Accounts Business (Desktop)
    How to create a backup in Reckon Accounts (Desktop)

    Let me know how you get on


    ℹ️ Stay up to date with important news & announcements for your Reckon software! Click HERE for more info.

  • Adam Dardick
    Adam Dardick Member Posts: 5
    edited March 2017
    Hi DebonAir,
    Thanks for the response, unfortunately at install reckon Enterprise does not allow you to install the file in a different file path.
  • Adam Dardick
    Adam Dardick Member Posts: 5
    edited March 2017
    Hi Rav,

    Thank you for the response, to give some idea of the setup:
    18 concurrent users across multiple operating systems
    TS connection for 7 staff
    datafile saved and operated from SBS 2011 server
    current data file size: 2GB +
    Re-build is done fortnightly as a precautionary measure.
    re-build takes 4-5 hours on the SBS server.
    Table sorts done monthly.
    Backups done daily.

    This user is a heavy user, taking orders, creating sales orders, converting to invoices, creating purchase orders and entering bills.
    the error seems to happen the most when saving a sales order, but its not limited to only this.

    the users details:
    Windows 7
    SSD 250gb - 18bg free
    4gb ram

    This is not limited to this user, it just happens the most to him.



  • Adam Dardick
    Adam Dardick Member Posts: 5
    edited March 2017
    Further, this is the final lines of the QBwinlog:
    dbspecificerrorhandler.cpp (70) :  MESSAGE: Thu Mar 16 10:42:21 LVL_ERROR--DB error -298 ErrorMessage:'Attempted two active database requests' from file:'.\.\src\DMTXNSQLTransactionLink.cpp' at line 2384 from function:'IDBTransactionLinkList::DBSQLLoadTransactionLinkList'dbspecificerrorhandler.cpp (70) :  MESSAGE: Thu Mar 16 10:42:21 LVL_ERROR--DB error -298 ErrorMessage:'Attempted two active database requests' from file:'.\.\src\DMTXNSQLTransactionLink.cpp' at line 2409 from function:'IDBTransactionLinkList::DBSQLLoadTransactionLinkList'
    dbspecificerrorhandler.cpp (70) :  MESSAGE: Thu Mar 16 10:42:21 LVL_ERROR--DB error -298 ErrorMessage:'Attempted two active database requests' from file:'.\.\src\DMTXNSQLTransactionLink.cpp' at line 2437 from function:'IDBTransactionLinkList::DBSQLLoadTransactionLinkList'
    DMDQEDynamicQuery.cpp (1340) :  MESSAGE: Thu Mar 16 10:43:11 LVL_SEVERE_ERROR--ExecuteQuery failed (DETAIL AVAILABLE), error id: -6019, sub id: 0, 'Succeeded', ''
    DQEWrapper.cpp (422) :  MESSAGE: Thu Mar 16 10:43:11 LVL_SEVERE_ERROR--DQEWrapper::DoQuery: ExecuteQuery failed, error id: -6019, sub id: 0, 'Succeeded'
    ItemHistUpdateEngine.cpp (728) :  MESSAGE: Thu Mar 16 10:43:11 LVL_ERROR--Item History database error (6).  Error Message: Succeeded

    SBRPaymentSummary.c (133) :  CHECKPOINT: Thu Mar 16 10:43:12 GetAppSetting (GOVCON_PS) = (ON)
    windows.c (2422) :  VERIFY: Thu Mar 16 10:43:33 (! InModalState ()) is false
    TransactionManager.cpp (1546) :  MESSAGE: Thu Mar 16 10:43:33 LVL_FATAL_ERROR--*** FATAL ERROR *** (M=2188, L=1546, C=315, V=0 (0x0))