Thanks for your reply, Roger, and I will make sure to hit "Save" before posting. Next time this happens to me I will do the same as you and use the feedback option.

When I searched the forums regarding this issue, it seems like people were having this same/similar problem for 2013.x 

To be honest, I wouldn't at all be surprised if it's a Windows 10 issue. What I've been hearing lately about Windows 10 is that it decides for users that software on their machine is a threat or incompatible, and then up an' uninstalls their software... I'm talking 'significant' applications such as AutoCADD. Unbelievable. Anyway, here's hoping someone from Sage addresses this on the forums so we can see what the fix'll be. It's year end for many so this is not good timing.

I'm still getting this error message... anyone else having this problem or know how to fix this? Every time I do an account rec, I get this message and Sage50 up and quits :(

Thanks!

Kristine

Hi Daryl,

Not really, but, there is something I will be trying come the next time I do an account rec... see RandW's post on this very matter, at:

https://sagecity.na.sage.com/support_communities/sage_50_accounting_ca/f/159/t/101581

Here's a screen grab from that post, but it would be best if you gave it a read over and see what think... if you give RandyW's idea a try, I'd love to hear how this worked out for you! Especially since I will soon be upgrading our Sage50 at the office from 2013 to 2017.1 (I use 2017.1 at home).

Kristine2012 said:

I should really make an effort to remember to send a copy of the event log to Sage and Microsoft, I guess.

It's actually quite important to do this.  Most software developers have to work on the old premise:

Once is random chance

Twice is co-incidence

Three times is enemy action.

Bugs are the enemy, not all computer crashes are bugs.  Some are Cosmic Rays, hardware problems, other software, etc. 

It's impractical to investigate something that's only happened once or twice, and not enough data to track down the cause.  

When they see the same error coming in from a few dozen IP addresses, the problem is more likely:

 - fixable because there's more data, and

 - more likely an actual problem with the software.

So, please do send an error report.   Unless it's software you just wrote, or you know it crashed because a plug came out or something.

Sage can't fix something that's not broken inside their software. And 'the program stopped working' error message with a version number is unfortunately not much help in locating the cause. It's like an accident report that only has the newspaper headline "airplane crash".

All software (Microsoft Windows, the Microsoft .NET framework, the Microsoft compiler, Microsoft Office, Sage 50, your antimalware software) has bugs.

Please, always, if Microsoft Windows presents the option to send in a report, do that. It's an effective way of collecting the data needed. Reporting them to Microsoft helps get them found and hopefully fixed.

I'd add most users don't care who's fault it is, they just don't want their software to crash on them in the middle of task.

And software vendors generally don't want that, any more than the people who make cars and airplanes do.   As far as I understand, the automatic error reporting to / through Microsoft is one of the best ways to get them resolved.

All that said, because of the lack of bug testing by software companies (because I understand it is a VERY expensive process),

NASA has had software bugs that wrecked *billion* dollar programs, surely a lack of testing is not the problem.  Sage would presumably run batches of tests that will find nearly all significant bugs, that would affect all company files. 

Exhaustive testing is impossible - every company file is different, every workstation and printer and network is different, even the steps I use to do a bank reconciliation are different from the steps you use.   On top of that, the banking entries posted by other users while I'm doing a reconciliation are going to be present / not present, and different each time. 

I fully support sending bug reports back to both Sage50 and Microsoft, I do it all the time and won't be stopping any time soon.

Those automatic bug reports do have an effect.   The bug report / fix / release process is unfortunately painfully long for desktop software, but the likelihood of finding and implementing a fix increases with the number of reports.

Windows also may report software errors that don't actually cause a crash (these events in the Event Viewer log are mostly related to other programs, such as Internet Explorer:

Not exactly sure what a Radar Pre Leak is supposed to signify, but I don't have to.   Presumably it's "this program did something unwise", sort of the computer equivalent of jaywalking.  Hopefully someone at Sage will get the information if it happens regularly, and look into it.

Okay, RandyW, I got another one of these error messages today:

A few weeks back on a different machine, I upgraded to the latest version of Sage50 Pro Accounting, and this afternoon I just completed my first account rec since upgrading. It was upon hitting "Post" when I was finishing the account rec, when this happened.

So I tried to watch for a place where I would be prompted to send in a report, but Sage50 just up and quit and so I just clicked on the "Close Program" button.

I'm now in the EventViewer and here's what i'm seeing:

Any suggestions as to who would be the best to look at this? Should I send this to Sage50 or Microsoft or MySQL? Looks like there's an issue with the Connection Manager(?)

Best,

Kristine

There are filters to narrow down the event log list, in order to pick out more severe problems from among the thousands of routine ("information") messages.

Those 'information' messages are like "car entered parking lot".  Warnings are like "car overheating" and Errors are like "Car on fire"  

Kristine2012 said:

Should I send this to Sage50 or Microsoft or MySQL?

Since the crash is happening at a specific point in using Sage 50, I would call their Support.  They should be able to look at the 'crash dump' and figure it out.  And / or perhaps examine the company data and find the cause.

By comparison, Mysql bugs are uncommon, and bugs in the operating system are rare.

It's not impossible that the usual go-to Support suggestion of "uninstall and reinstall" will fix any problem, but it's more likely a waste of your time.

My guess is that there is a minor data anomaly in that company file, and the bank rec code crashes on post because it is particularly fragile or buggy. 

I've seen Sage 50 crash on a particular operation with a specific vendor name.  Reproduced it in the sample file and sent it in via Support.  Clearly that was a program bug, and by anomaly I mean only something that is not common.

Thanks for the reply, RandyW...

Re your point on something  buggy in the company file... I've had this same error with two companies now :(

My reaching out to you above is now the second company I am finding this happening with, and it was also just after upgrading to the latest version of Sage50, i.e. 2017.2.

I'll see what happens next account rec... and just start keeping a record.

I would have supported Randy's suggestion that there probably is an anomaly in the data set. I suggest this because I have been using 2017.2 Accountant's Edition since it first appeared for about 13 companies with a total of more than 30 account reconciliations each month with out ever see this error message.

Another possibility could be in the program but it matters little which Edition - Pro, Premium, Quantum or Accountant's Edition you are using as the code is all the same and features are only unlocked based on the installation key. The account reconciliation posting would be the same across the board.

The next thought might be the environment. As Randy suggested the other programs and applications running on the hardware in your unique installation may be a cause. But you have indicated it is happening on two different computers.

Having ruled out the obvious I would call Sage Technical Support. They can look at may other area that are not readily available to most users including things like the error log or even the transaction log and decipher what is happening. The last time this was happening, a couple of years ago, I did have a problem. A ten minute call solved the problem. They logged into my computer deciphered the code and suggested that I make a change to a setting in another application. They would not tell me how to change the other application as that is not their responsibility but I listened, made a change and have been happily posting entries ever since.

I know this does not give you an answer but I would urge you to call.