If it happened once, no, it's a random occurrence.  If it happens regularly, then please post what what the situation is when you see the error.  (is it every time you run a report, start the program, etc.)  

If your question was "My car won't move, why", to give a useful answer, a person would have to know more about the situation - i.e. what do you see and hear when you turn the key, is the car buried under a snow bank, etc.

After installing Sage 50 2014.2 Professional to my PC (Windows XP Pro-SP3, 4Gb RAM) along with the 2013.4 there, I can't create new file, convert/open existing or sample data file from it at all. The program simply stops (wait for around 5 min.). The 2013.4 version works well so far. Do I need to uninstall V2013 first to get V2014 works?

Do you have any other versions of MySQL installed, other than the ones provided by Sage?

I had some difficulty with getting the 2014 release to work AT ALL, and it was all caused by having a version of the MySQL ODBC connector that was incompatible with the 2014 release, but had the same version number as the latest MySQL that I had downloaded from Oracle, except without an "A" at the end, and all versions of Sage / Simply stopped working when I installed the 2014.2 release.

The 2013 and the 2014 releases use different versions of MySQL, and one should not wreck or conflict with the other.   I have a laptop beside me that's got both the 2013.2 and 2014.2 releases installed, no problems.

No, you should not need to uninstall the 2013.4 software to have the 2014.2 release working.  I would say it's best to install the 2013 first as you did, if only because the default Windows file association will point to the most recent (2014) release, which is probably what you want.

The regular problems with firewalls, etc. can happen with any version of Simply / Sage 50.  

Randy, I'm not a tech person on this so I'll probably keep using the V2013.4 the first half of this year & hope the upcoming V2014.3 will fix this bug soon.

Randy,

I found these Oracle MySQL Connector files in my PC:

- ODBC 5.2(a), and

- ODBC 3.51.

Should I remove both to have V2014.2 works?

Hi,

The MySQL ODBC connector 5.2a is part of Version 2014.1 or 2014.2.  

The 3.51 (old) version is part of Sage 50 up to 2013.   The two shouldn't interfere with each other, removing the MySQL ODBC connector 5.2(a) should be done after removing the Sage 50 2014 release.

I had the exact problem you describe, but I had the 5.2  (without the A) connector installed, and the Sage 2014 install didn't put the needed (a) version on, so nothing worked.  I thought you may have had the same problem.  

If that doesn't work, and you're stuck, I believe Sage Support does cover some installation issues.

My installed ODBC 3.51 is 3.51.28 & according to Sage 50's support.na.sage.com/.../viewdocument.do, it should be the 3.51.19 (available at the bottom section).

If "ODBC 3.51.xx" is for V2013 & "ODBC 5.2(a)" is for V2014 and my V2013 works well so far, why "ODBC 3.51.xx" is the issue to me? I must miss something.

My installed ODBC 3.51 is 3.51.28 & according to Sage 50's support.na.sage.com/.../viewdocument.do, it should be the 3.51.19 (available at the bottom section).

If "ODBC 3.51.xx" is for V2013 & "ODBC 5.2(a)" is for V2014 and my V2013 works well so far, why "ODBC 3.51.xx" is the issue to me? I must miss something.

Hi Louis,

If you're not sure that the MySQL ODBC 3.51.xx connector is the right one, you can remove the 2013 software, remove the ODBC connector, restart, and reinstall the 2013 version + updates.  The document that specifies 3.51.19 may be out of date, or an installation of MySQL downloaded from Oracle may have installed the 3.51.28.  

My system here has the 3.51.28 connector, and it is working with both the 2013 and 2014 releases.

I would suggest first, as a test, try shutting down your security software and see if that makes any difference.  I've had some trouble with Panda antivirus installed, getting Sage 50 to work.  On another system I had to change the configuration of Norton Security.

And it's not a last resort, but you might want to call Sage directly.  It's a busy time for them right now, everyone's installing and starting new payroll periods.