Sage 50 Accounting 2013 [0057-rel\2013.2] has encountered a problem and needs to close.

Sage 50 Accounting - Canadian Edition

Sage 50 Accounting - Canadian Edition
Solutions are just a click away as you share, learn, and network with other small business owners, bookkeepers, and accountants. Sage 50 Canada Accounting support specialists and knowledgeable fellow users are ready to help!

Sage 50 Accounting 2013 [0057-rel\2013.2] has encountered a problem and needs to close.

  • Hi,

    I'm seeing a lot of program crashes that relate to running reports.     Reinstalling the .NET framework has a good chance of fixing a problem that's happening on one computer, but this isn't one of those situations.  So, before you tell me that I just need to run Fdisk / MBR, and then reformat my hard drive, and reinstall Windows, or delete all my historical data, or any other voodoo fixes, please read on.

    I've read assertions in this forum that if a crash occurred in the .NET framework, or the first crash occurred in the .NET framework, that the problem wasn't caused by Sage 50 / Simply Accounting, but by a problem (bug, corruption, setup, etc.) in the .NET framework.

    That's just horse puckey.

    If the calling module tells another module to do something that it can't do, it'll crash.

    What I would believe, is that if the crash happens in the .NET framework, the error address won't help anyone find the line of code that caused the crash.

    I've seen a more than a few of these sort of error messages, and some proposed fixes and possible causes.  To refer to all crashes "that .NET error" is like saying "That car crash problem". 

    If you look at the About box in Simply Accounting, and click on the 'Support Info' button, you will see a list of all the podules that Sage50Accounting.exe relies upon.  It's a really, really complicated stack of code, and it's really, really difficult to troubleshoot anything from an NT event in an email.

    The event report that I pasted in below happened a few minutes ago, and strangely, until I click on 'Debug' or 'Close', the program is still running, and communicating with the operating system.  The error displayed instantly, after clicking on 'refresh' on an inventory list report.

    All I can tell from this, is that the crash happened somewhere around the Sage 50 program attempting to display a progress dialog box, and that the programmer didn't handle an exception, and the exception wasn't terribly critical.  That part isn't 'rocket surgery'. 

    Reporting, and hopefully, eventually reproducing the (apparently random) error on demand, will help a programmer find the cause, also isn't rocket surgery. 

    Now...  Loading the symbol tables into Windows and using SysInternals tools to debug the crash...  I'm not a rocket surgeon, so I'm not going that far.  (yet)  

    Event Type: Error
    Event Source: .NET Runtime
    Event Category: None
    Event ID: 1026
    Date:  5-Mar-2013
    Time:  10:02:50 AM
    User:  N/A
    Computer: DELL-690
    Application: Sage50Accounting.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.InvalidOperationException
       at System.Windows.Forms.Control.WaitForWaitHandle(System.Threading.WaitHandle)
       at System.Windows.Forms.Control.MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean)
       at System.Windows.Forms.Control.Invoke(System.Delegate, System.Object[])
       at Simply.UI.Library.ProgressDialog.VistaProgressDialog.AsyncCallback(System.IAsyncResult)
       at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
       at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall()
       at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
       at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

    The operating system is XP Pro, SP3, all available patches installed. 

    DLL Information:

    Name Version Date Stamp Size Path

    Sage50Accounting.exe 20.10.0000.0001 2012/12/11 00:00 7582576 C:\Program Files\Sage 50 Accountant Edition ...

    ntdll.dll 5.01.2600.6055 2010/12/09 08:15 718336 C:\WINDOWS\system32 tdll.dll

    kernel32.dll 5.01.2600.6293 2012/10/02 21:58 990208 C:\WINDOWS\system32\kernel32.dll

    Sage_SA_QIFLib.dll 20.10.0000.0001 2012/12/11 00:00 76800 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_UTILS.dll 20.10.0000.0001 2012/12/11 00:00 74240 C:\Program Files\Sage 50 Accountant Edition ...

    USER32.dll 5.01.2600.5512 2008/04/14 04:42 578560 C:\WINDOWS\system32\USER32.dll

    GDI32.dll 5.01.2600.5698 2008/10/23 05:36 286720 C:\WINDOWS\system32\GDI32.dll

    ADVAPI32.dll 5.01.2600.5755 2009/02/09 05:10 617472 C:\WINDOWS\system32\ADVAPI32.dll

    RPCRT4.dll 5.01.2600.6022 2010/08/16 01:45 590848 C:\WINDOWS\system32\RPCRT4.dll

    Secur32.dll 5.01.2600.5834 2009/06/25 01:25 56832 C:\WINDOWS\system32\Secur32.dll

    SHELL32.dll 6.00.2900.6242 2012/06/08 07:26 8462848 C:\WINDOWS\system32\SHELL32.dll

    msvcrt.dll 7.00.2600.5512 2008/04/14 04:42 343040 C:\WINDOWS\system32\msvcrt.dll

    SHLWAPI.dll 6.00.2900.5912 2009/12/08 02:23 474112 C:\WINDOWS\system32\SHLWAPI.dll

    MSVCP100.dll 10.00.40219.0325 2011/06/11 01:58 421200 C:\WINDOWS\system32\MSVCP100.dll

    MSVCR100.dll 10.00.40219.0325 2011/06/11 01:58 773968 C:\WINDOWS\system32\MSVCR100.dll

    SAGE_SA_BUS.dll 20.10.0000.0001 2012/12/11 00:00 3776000 C:\Program Files\Sage 50 Accountant Edition 2013\SAGE_SA_B...

    SAGE_SA_REG.dll 20.10.0000.0001 2012/12/11 00:00 13824 C:\Program Files\Sage 50 Accountant Edition 2013\SAGE_SA_R...

    SAGE_SA_RESDLG.dll 20.10.0000.0001 2012/12/11 00:00 2782208 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_RESSTR.dll 20.10.0000.0001 2012/12/11 00:00 2844672 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_RESSTRSP.dll 20.10.0000.0001 2012/12/11 00:00 2879488 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_RESSTRFR.dll 20.10.0000.0001 2012/12/11 00:00 3040256 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_RESDLGFR.dll 20.10.0000.0001 2012/12/11 00:00 2821120 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_RESDLGSP.dll 20.10.0000.0001 2012/12/11 00:00 2840576 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_GLBLSUI.dll 20.10.0000.0001 2012/12/11 00:00 24576 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_ERROR.dll 20.10.0000.0001 2012/12/11 00:00 14848 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_TLSMGR.dll 20.10.0000.0001 2012/12/11 00:00 9728 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_LISTUTIL.dll 20.10.0000.0001 2012/12/11 00:00 23040 C:\Program Files\Sage 50 Accountant Edition ...

    mfc100.dll 10.00.40219.0325 2011/06/11 01:58 4397384 C:\WINDOWS\system32\mfc100.dll

    COMCTL32.dll 6.00.2900.6028 2010/08/23 09:12 1054208 C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_65...

    MSIMG32.dll 5.01.2600.5512 2008/04/14 04:42 4608 C:\WINDOWS\system32\MSIMG32.dll

    SAGE_SA_IO.dll 20.10.0000.0001 2012/12/11 00:00 2659328 C:\Program Files\Sage 50 Accountant Edition 2013\SAGE_SA_I...

    SAGE_SA_DBLYR.dll 20.10.0000.0001 2012/12/11 00:00 199168 C:\Program Files\Sage 50 Accountant Edition ...

    SAGE_SA_DBDRV.dll 20.10.0000.0001 2012/12/11 00:00 235520 C:\Program Files\Sage 50 Accountant Edition ...

  •  Hi RandyWester,

    The .NET reference also depends on your operating system - this was noted in the other forum threads. Again, we are tracking and doing our best to find a resolution to this issue.

    Based on the operating system: The .NET errors and repair requirements would generally affect Windows XP, this is a common issue with Windows XP. As for Windows Vista and higher, it was previously recommended to install the new .NET 4.5 that Microsoft has recently released. We've found this to correct the issue in various circumstances. Please see my below post - I have coopied this from the other forums I posted this in:


    We have been working diligently on trying to find a solution to this issue. We've found an option that has had much success so far with both random crashing as well as crashing when opening reports. We are still in the testing stages, so it is not a guaranteed fix as of yet - but please if you try it and it works, let us know so we can share with others.

    Microsoft has come out with .NET Frameworks 4.5. Installing this version of the .NET has been found to fix the crashing issues. Please see the below link to Microsoft downloads. "


    Thanks, hope this helps

  • Thank you Marissa,

    The workstations I'm responsible for are all XP SP3.  I will reinstall the .NET 4.x framework on the ones that are having the most trouble, and post back as to whether it helps.  Because it's been so random, it will be some time before there's enough data to know.

    I was not suggesting that it's unheard of for a workstation to have a broken or gibbled .NET framework, and I'm definitely not suggesting that Microsoft's .NET framework is bug-free. Code that may have worked perfectly in .NET 2.0 might crash in 4.0, and then not crash in 4.5.

    But I could not agree that the statement that implied that every error message that mentions the .NET framework as the site of the crash, or of the first crash, was not due to a Sage 50 program issue.  I also think that lumping all crashes together into one issue, because the Event Log mentions .NET, is misleading.

    On one workstation, I see 42 .NET errors in the event log, and 34 of them contain this line in the stack trace:

    at Simply.UI.Library.ProgressDialog.VistaProgressDialog.AsyncCallback(System.IAsyncResult)

    The module containing that function is inside a DLL that is provided with Sage 50, 2013, and that module is called by other modules that are inside DLLS provided by Sage.  The most common reported problem I'm hearing about, is related to running reports.   Reports take a while to run, so they use the progress dialog, so that makes sense.  That it happens perhaps less than one time in a hundred, is making it really difficult.

    (For the other 8 times, I don't see any real pattern.)

    As to the severity of the problem, the worst I've seen is 34 crashes over 5 months, is about 80 times a year, and maybe 15 minutes worth of work lost each time, is about 20 hours lost productivity per year.  This is on a workstation where the user runs reports probably a hundred times a day.  So It's a definite nuisance, but it's far from a show-stopper.

    Excel, Outlook, and Internet Explorer also crashed on these workstations, during this period, and probably if someone was a heavy, continuous user of any of these programs they would be complaining too.   (but to someone else)

    As I said, the next time it happens to me, I'll dig a bit deeper.  Versioning of, and crashes in, DLLs have been a plague since the 'ctl3dv2.dll' issues in Windows 3.1

    Thank you,


  • (XP Pro SP3) - Reinstalling the .NET framework had no effect.

    I noticed that there were a lot of temporary files left behind - tmp4E3.tmp.SimplyReport, tmp4E1.tmp.SimplyReport, etc. when the machine crashed. 

    I guess that's obvious, given that creating reports will create temporary files.  The timestamps on these files correspond more or less with the crashes, and many of them are in pairs of close time-stamps (i.e. a 15 MB file @ 4:10 pm, a truncated 20 KB file at 4:11PM)  indicating that it crashed while doing a drill-down from a large (inventory) report.

    I'm going to check whether the workstation is set to virus-scan the temp directory under c:\documents and settings\<username>\Local Settings\Temp.

    The working theory that I have, is that there is a short time-out to access the temporary file, and this machine is old - E2180 cpu is a 'dual Pentium', so it's slow, and the disk is old and slow, so it could be failing on access to the temporary file. 

    If the disk is busy / the antivirus is trying to scan temp files, the Sage 50 program could be unable to reliably access the temp files, leading to the crash result.

    We'll replace the computer soon, they're relatively cheap these days, especially compared to the person's time.


  •  Hey Randy,

    Thanks so much for the info, its greatly appreciated... If you'd like, can you check the SAJ folder of the data file you are trying to open and if you see an ExceptionError.log in there, would you mind inboxing me that? I would love to pass that along if there is one there. Again, this would be to help us further investigate.



  •  I've had one crash, and one hang today.

    Both times it was immediately after starting or refreshing a report.  Both times, the system left behind temporary files:

    12-Mar-2013  09:16 AM        18,012,875 tmp69.tmp.SimplyReport   (crash was at 9:41, referred to VistaProgressDialog)
    12-Mar-2013  11:31 AM        18,014,478 tmp41.tmp.SimplyReport   (hang, displaying the progress dialog box.

    I restarted the system after the first crash, and waited until 1:30 PM for the second one.  The file tmp41.tmp.SimplyReport was still open 2 hours later, but nothing was happening (no file reads or writes).

    Disk is 93% full and fragmented,  I checked the physical disk first using Windows and then Seagate SEAtools, no issues.

  •  I get the same error message.

    Begin > Sage 50 Accounting 2013 [0057-rel\2013.2] has encountered a problem and needs to close.  We are sorry for the inconvenience.

    Microsoft .Net Framework
    Unhandled exception has occurrer in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.

    External component has thrown an exception. > End

    After clicking continue, Sage50Pro freezes. This error occurs each time I try to use Setup > Report and Forms... as soon as I click on the Reports and Forms (R&F) button, the error occurs.

    When I first installed Sage50Pro (S5P), everything seemed fine. Did my previous years migration into S5P and started the new fiscal year. Then I went into R&F and did some changes that I cannot remember, but after that, when I tried to go back into R&F, the above error occurred and has now persisted. So anytime I click on the R&F button, S5P error message and freeze.

    So the problem is not any other software. The problem is with S5P and how it organizes changes to its default settings in the R&F. That's where the problem is and that's where Sage needs to look and fix this ASAP with an update otherwise this software is useless.

    About .Net Framework, it cannot be the cause and getting 4.5 will not help and anyways, there is no 4.5 for XT Pro 64. In any case here is the fix in 4.5.

    Note: The .NET Framework 4.5 redistributable was updated on 10/9/2012 to correct an issue related to an improper timestamp on a digital certificate which causes the digital signature on files produced and signed by Microsoft to expire prematurely. We recommend customers that previously installed the .NET 4.5 redistributable package dated 8/16/2012 install this updated .NET 4.5 redistributable package. More information about the issue can be found Microsoft Security Advisory 2749655.

    The R&F problem has been around for ages occuring in many of the updated verions of Simply and now Sage.

    So this software is useless and all the time spent on this is lost. Just great.



  •  OK, I took this a little further.

    Since I am using XP Pro 64 and since .Net Framework 4.5 is apparently not compatible with any XP version, I decided to go to Add and Remove Programs and clicked on my most recent .Net 4.0 then clicked on Change/Remove. The next window enables to click on Repair, so I did. Once that was done I rebooted my computer to activate the .Net repair.

    Then I opened SagePro50 and tried the Report and Forms (R&F) button and it works. So from now on I will document any other changes made to the R&F, only changing one item then exit the R&F, then re-entering the R&F to see which change will cause the problem.

    So for now it seems to have fixed the problem but I do not know how that problem first occured via the R&F changes.

    Hope this helps others cope. hehehe

    Back in business.



  •  That's awesome! thanks so much for letting us know. I am going to forward your info along internally as well!


    Much Appreciated

  • I'm on Windows XP using Sage 50 and I've been seeing a lot of crashes, especially at start up.  It crashes and then starts up fine the next time.  I've also had crashes while in the middle of doing work.  Pretty frustrating.  If you are going to roll out a product for people to use, shouldn't it be a little more stable than this?

  • Not trying to diminish your problems, but you are running the Windows XP operating system that is beyond it main support life by many years and will reach it's end of extended support life by MS on April 8, 2014.


  • Good morning,

    Please see the instructions earlier in this thread on how to check your event viewer to see if you have any .NET errors. These types of issues are common in XP and will affect how Sage 50 functions as the program uses .NET. Once you determine if you are having these .NET errors, you are then going to want to follow the instructions on how to repair them.

    Once the .NET is repaired Sage 50 should function correctly.


  • As an addition to what Marisa just said, please see the below article for issues related to the Microsoft .net 4.0

    260-1005319 - Error “Sage 50 Accounting has encountered an unexpected error and needs to close” is occurring intermittently

    Hope this helps.