With a new Sage update comes some more sage bugs - and this one threw me totally. After fixing problems with the sage data service on a server a client was still receiving the following error when trying to backup their data:
"unable to connect to the sage data service"
This didn't make any sense, as we were logged into sage which meant the service was working.
Eventually, we tracked this down to a bug in the new sage update which meant that if you connect to your sage data using a mapped drive (s: for example as most of our clients do) the local sage wasn't able to talk to the data service on the server.
This solution? Simply edit your company file to use a UNC instead of a mapped drive:
So what was: S:
Became: //servername/sage
Problem solved!
"unable to connect to the sage data service"
This didn't make any sense, as we were logged into sage which meant the service was working.
Eventually, we tracked this down to a bug in the new sage update which meant that if you connect to your sage data using a mapped drive (s: for example as most of our clients do) the local sage wasn't able to talk to the data service on the server.
This solution? Simply edit your company file to use a UNC instead of a mapped drive:
So what was: S:
Became: //servername/sage
Problem solved!
No comments:
Post a Comment