Kristine:

Are you running a stand alone server or is the server also a workstation for entering data into Sage 50? If it is a stand alone server there is a different installation process for the server. If your server is a workstation then ensuring the workstation is started first before having another workstation connect to the server could be your issue. You may also have an older version of the Connection manager on your server. These are only several thoughts on your situation.

Hi Agate,

Thanks for your reply.

We have an actual server, not a PC we call a server :) That said, everyone in the office has Sage 50 installed on their PCs, and then we grab any given client's Sage 50 file/data from the server.

Our IT guy came by our office yesterday, and he uninstalled previous versions of the Connection Manager on the server so that only the most current version of Connection Manager lives on the server (this speaks to your comment re older versions). He also replaced my ethernet cable. This seemed to correct things and I'm up and running again on my PC, although at the end of the day yesterday when I was closing Sage 50 for the day, I got an error message and was not able to back up the file I was working on.

As well, other people in the office are having the issue now... here are the error messages they are getting this morning:

While I seem to be up and running, I'm afraid to close out a file I'm working on this morning in the event it won't back up.

I tried calling Sage this morning, but they were not yet open.

That's the status of things... I'll be trying to call Sage again shortly.

Thanks again for your reply.

Best,

Kristine

Hi Agate,

It seems we have solved the issue... it was our virus protection software, Webroot. We have to disable it, then re-enable it, and then we are back in the game fully functioning with Sage.

Whoddathunk!

Thanks again for your help!

Cheers,

Kristine