SAGE50 Service BUG REPORT (???)

Is there an "Upgrade" for the server install that I should know about?

Are there any special 'server' patches upcoming that I should know about?

On Friday I installed SAGE50 2013 "server install" on a 2008 Server.

(Got the latest download link from our sales rep.)

Installed the full program on a couple of workstations, moved the old SIMPLY data files onto the 2008 file server, set up sharing.

Everything worked great out of the box, got all the companies upgraded, the workstations all have both been "updated" to latest release 4.

Everything working perfectly! So far so, good, or so I thought...

Today, the bookkeeper tried to open a company, and got the "can't connect to Sage50 Connection manager" error.

Pretty odd, since it was all working fine on Friday, all the proper firewall entries had been done automatically, and absolutely nothing has changed on server or workstation since then. I had a look on the server, and the Service showed it was running (in the tray, Status all looked good). But obviously, something was not as it seemed!

Went to STOP the service from the handy button provided - no go.

Went to restart the SAGE service in services control panel ... no go.

Just hung and hung... ARGH

Rebooted the server, and now all is well with SAGE (for the moment). This being the COMPANY FILE SERVER, I was not at all impressed with the need to reboot.

What's wrong with this picture?

I notice there are actually TWO SAGE services installed, SAGE50 DB Connection manager ( which was set to auto) and SAGE50 Transaction Manager 2013 CAN - which was set to manual, and was not running when i looked. Was this the cause of the GLITCH?

Parents
  • 0

    Disclaimer:  I'm not an employee of Sage, the following is only what I've observed / surmised when troubleshooting various issues:

    The program makes a (Samba) file connection to the <companyname>.SAI file, which it resolves to a server name in order to connect to the listener port of the Connection Manager service on the server.  If the service isn't running, or the server firewall stops the connection from the workstation to the server, you'll get that error message.  (can't connect to...)

    The Connection Manager starts the MySQL daemon if it isn't running, and passes it, and the workstation client the next available port.  If there's a firewall issue, this is where it can stop with a database error.

    The Sage 50 Transaction Manager runs in the background to manage posting conflicts and potential 'deadlock' situations between workstations.   It wasn't the problem.

    So the Connection Manager wasn't running when you checked, and wouldn't start.  That's where the problem was, but not necessarily the cause of the problem. 

    None of this will tell you why it crashed / couldn't run.  If it happens again you may find the answer in the event logs. 

    Yes, there's a newer version, it comes with Sage 50 2014, and uses newer versions of MySQL for data storage and the ODBC connector.  It is back-compatible.

    I hope that helps, please post back.

Reply
  • 0

    Disclaimer:  I'm not an employee of Sage, the following is only what I've observed / surmised when troubleshooting various issues:

    The program makes a (Samba) file connection to the <companyname>.SAI file, which it resolves to a server name in order to connect to the listener port of the Connection Manager service on the server.  If the service isn't running, or the server firewall stops the connection from the workstation to the server, you'll get that error message.  (can't connect to...)

    The Connection Manager starts the MySQL daemon if it isn't running, and passes it, and the workstation client the next available port.  If there's a firewall issue, this is where it can stop with a database error.

    The Sage 50 Transaction Manager runs in the background to manage posting conflicts and potential 'deadlock' situations between workstations.   It wasn't the problem.

    So the Connection Manager wasn't running when you checked, and wouldn't start.  That's where the problem was, but not necessarily the cause of the problem. 

    None of this will tell you why it crashed / couldn't run.  If it happens again you may find the answer in the event logs. 

    Yes, there's a newer version, it comes with Sage 50 2014, and uses newer versions of MySQL for data storage and the ODBC connector.  It is back-compatible.

    I hope that helps, please post back.

Children
  • 0 in reply to RandyW

    Thanks Randy! Actually the Connection Manager ostensibly WAS running when I looked in on the problem. At least, the tray program REPORTED it was, and it showed as "running" in the services control panel as well. But in it's allegedly 'running' condition, the operating system was unable to either stop or restart it - it just hung, at that point. At any rate, what you have shared is very helpful.  Incidentally, nothing of interest in the EVENT LOGS!

  • 0 in reply to rotech

    I believe there's another, similar case on this forum.  Similar thing in that it wouldn't run properly after the initial install, until they did a full restart of the server.