Without further information about did it work and then didn't it?...does the sample file open?...do any of the options in the knowledgebase article about this work?, all I can suggest is to try the knowledgebase article on the topic.

Hi Dan,

Did you see my Jan. 30th post on this exact issue? Not that it answers your question, but I'm glad to know I'm not the only one having this problem... for me it's when I hit "Post" on an account reconciliation.

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

Kristine

Kristine2012 said:

Did you see my Jan. 30th post on this exact issue?

The error message from Windows has the an error number (type of error) + the internal name of the software that crashed / stopped working, so it's not really a specific issue.   The error number 0057 is mentioned in the link in Richard's post.

The error message doesn't have a single, specific cause.

Hi Randy,

I guess it's kind of a case of learning to live with it then? If there's no single, specific cause? That link to the knowledge base article seems pretty technical... while I'd be willing to give it a whirl, I'd rather have some assurance from Sage that that'd REALLY fix things LOL before embarking on all that work :)

Searching around the internet I came across this:

From http://www.sagenumber.support/fix-sage-50-error-0057-rel-2013-2/

Anyway...

That site may well be legitimate, but it bears an unfortunate resemblance to a malware phishing site.  Their kindly offer of a 'scan' may be a malware installation program.

The explanation of the error is a mashup of irrelevant technical-sounding babble that didn't come from Sage software.

As Richard suggested, if the problem doesn't occur in the sample file, the problem isn't with the installation of the software, and can't be fixed there because it isn't broken there.  

If the sample file works, but the company file doesn't, the problem is within the company data.  Not likely with the accounting data, but perhaps with something that tells the software to put a message box on the screen 100 pixels down and to the right of 1920 divided by zero.

If the Edition of Sage 50 that you have allows creating additional user IDs, do a backup, create a new user profile, and try that one.

There are a series of other steps in the (actual Sage) technical document that Richard referenced that should be tried too

Hi Randy,

You had me until "...message box on the screen 100 pixels down and..."  I take it you are being facetious here? LOL Sorry if I'm thick on picking that up in text...

Anyway, I can wrap my head around trying an account rec in the sample company and see what happens. Thing is, there's nothing unusual in my company's data that I can think of... as in, there's no 3rd party add-ons, etc... just a regular company in ol' Sage50 Pro... I must have done something to bugger it up, I guess!! [:D]

Thanks for your help...

Kristine

Kristine2012 said:

I take it you are being facetious here?

Perhaps somewhat, but because Sage 50 stores the position of each window on screen, for each user, for each monitor resolution (i.e. you log in on multiple workstations with different screens, sometimes multiple monitors, sometimes not, there's an external monitor that's a different resolution than the laptop screen, a projector that you used one day for training last year), it can go a bit sideways if that doesn't go 100% correctly.

So that's why setting up another user ID can resolve it - there are no stored window positions for a new user login.  (if you're not typing in a password to open the company file, as when opening the Sample File, then you're the 'sysadmin' user, and no other users are set up.)  There's a utility included with Sage 50 that can clear all the screen position info without doing that, but logging in with another user ID is a good, quick test of whether that is the issue.

Kristine2012 said:

Thing is, there's nothing unusual in my company's data that I can think of... as in, there's no 3rd party add-ons, etc... just a regular company in ol' Sage50 Pro

There's the possibility that something went wrong with storing a bank reconciliation once in the past, and the software keeps hitting that historical 'bad data' and crashing after saving the data.  Bank reconciliations are stored in a database with linked IDs that reference each other.  If some data is broken / missing it may still function mostly normally until the posting / saving process.   The software more or less takes the details of the reconciliation you've been working on and gives it a permanent ID, leaving the working data as the next working reconciliation.  A lot of things are happening right then.

Kristine2012 said:

trying an account rec in the sample company and see what happens

The process of troubleshooting anything is usually to change the operating environment and see what happens.  If you don't isolate the problem to either the company file vs. the software vs. the workstation, you can go a long way down the rabbit hole of reinstalling Windows parts that aren't broken before you start, but get mangled when you poke at them. 

Kristine2012 said:

I must have done something to bugger it up, I guess!! [:D]

Well... something piled up while you were using it, but that's not the same thing!   As an example, there could be ten thousand video drivers in use in Windows, any of which could have slight imperfections that normally don't cause a problem.  But perhaps one day, you moved the reconciliation window, the Sage software asked Windows where you moved it to, and the video driver was having a problem, so it gave an answer that works out to be just outside the perihelion of the orbit of Neptune.  The Sage software says 'allright' and dutifully bashes that huge number into the tiny space meant to hold a screen position between 1 and 65535.  The next time the software tries to position that window on screen exactly where you like it, on that particular laptop... it crashes.  

The reality is that all software has bugs, but like a few misfiled documents in 10 years of backup paperwork, the overall system works nearly perfectly. 

"Perhaps somewhat, but because Sage 50 stores the position of each window on screen, for each user, for each monitor resolution (i.e. you log in on multiple workstations with different screens, sometimes multiple monitors, sometimes not, there's an external monitor that's a different resolution than the laptop screen, a projector that you used one day for training last year), it can go a bit sideways if that doesn't go 100% correctly."

Ah! Well that's instructive... that I can wrap my head around and explains your comment, "...100 pixels down and to the right of 1920 divided by zero." Initially, that reference was completely over my head and it's why I didn't get what you were saying, but now I understand.

I'll definitely give the setting up a new user ID a whirl come my next account rec and see what happens--wish me luck and thanks for all your time taken to explain that [:)]