I have two computers (desktop and laptop) that are running Sage 50 2017 Accountant's version with Windows 7 OS.  I have the same problem with Sage 50 crashing on the desktop almost every time I try to reconcile. I thought it might be a memory issue. The desktop has 4 GB memory and the laptop has 8 GB but the specs for Sage 50 2017 Pro and Premium recommends 1 GB of available memory so I can't see it being that.  I make sure that nothing else is running at the same time but it still happens. When I am busy this can be very frustrating.  I see that there are enough postings about this issue, but nothing definitive has been written about the cause.  It would be great if there was a fix for this.   

Hi dkumka,

I'm getting to a point where I'm wondering if it's some sort of conflict with Adobe... I have the full creative suite for Illustrator, Photoshop, Acrobat, etc. and I am beginning to suspect the driver for .pdf is causing other software (i.e. primarily, but not limited to, Microsoft Excel) to behave oddly. Lately it seems that when I go to print from Excel, my computer keeps telling me I have no printers installed. I keep having to restart the print spooler... from what I've read on Microsoft's user forums there's a registry fix for this--I REALLY don't want to be poking around with that 

At any rate, I mention this because both these issues seem to have been happening for about the same length of time now... aaaand, that could be just purely coincidence, too. 

So I'd like to ask if you have any Adobe software installed, too, perchance?

Best,

Kristine

Hi dkumka,

I'm getting to a point where I'm wondering if it's some sort of conflict with Adobe... I have the full creative suite for Illustrator, Photoshop, Acrobat, etc. and I am beginning to suspect the driver for .pdf is causing other software (i.e. primarily, but not limited to, Microsoft Excel) to behave oddly. Lately it seems that when I go to print from Excel, my computer keeps telling me I have no printers installed. I keep having to restart the print spooler... from what I've read on Microsoft's user forums there's a registry fix for this--I REALLY don't want to be poking around with that 

At any rate, I mention this because both these issues seem to have been happening for about the same length of time now... aaaand, that could be just purely coincidence, too. 

So I'd like to ask if you have any Adobe software installed, too, perchance?

Best,

Kristine

I have adobe software on both machines and don't think it is a compatibility issue for me.  I contacted tech support but couldn't replicate the crash.  We viewed the error log it seems to stem from the SAGE_SA_CAT03CNT.dll file.  As suggested by the support person, I have uninstalled and reinstalled the Sage 50 2017 software and worked all day without a crash.  :).  I know it takes some time to uninstall/reinstall/update to current version but if I can work with out crashing it is worth it.

Hi dkumka - interesting... so this file "SAGE_SA_CAT03CNT.dll," does it get corrupted or something so that an un-install/re-install/update overwrites it with a clean file, sort of thing?

That is correct Kristine2012.  It may not be the same file for you but may be the same issue.  Have you tried to uninstall and re-install Sage to see if that fixes your problem?

Hi dkumka - I have not yet tried the un-install/re-install Sage50 option, but sounds like I this is the solution. Still, I'd like to know if there is something I'm doing, or if other software is causing, that .dll to corrupt... cuz long-term, I'd like to avoid doing whatever is causing the corruption 

It's unlikely that other software would corrupt a non-shared DLL (in another program's installation folder).  Disk corruption can damage any file anywhere, and a re-install in that situation may work because it will write to a different place on the disk.

An error referring to a DLL also doesn't mean that the problem was cause by the DLL, only that the crash occurred while it was loaded and executing code.  If the code passed to the DLL was wrong, the cause could be elsewhere.  (it's not uncommon to see an error referring to a Microsoft system DLL when the problem was caused by other software)

In any case, if the problem follows the company file to another workstation, it's likely not caused by the installation.  One of the posts mentions the issue ocurring on two different workstations.