Jason Laskey
asked on
Sage error: Error: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error:0 - The semaphore timeout period has expired.)"
When people connect to Sage the receive the following error, even when the program is just opened
Error: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error:0 - The semaphore timeout period has expired.)
Error: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error:0 - The semaphore timeout period has expired.)
Which product from Sage? They have a few on the market.
ASKER
From what I can see it's Sage 200 (Finance)
Could be a dodgy port on a switch, try power cycling the switch and moving to a different port.
ASKER
OK thanks I will have to arrange for this any other ideas whats this could be?
I just recently now also switched off his PC from going into hibernation too as he says this happens every 2 hours or so
I just recently now also switched off his PC from going into hibernation too as he says this happens every 2 hours or so
ASKER
Hi Bruce, I had the server restarted last night and the same error has occurred . I was informed this happens after every 2 hours, please any help would be greatly appreciated
This usually happens when it loss connection to the database so you'll need to reconnect.
Now you should see why connection to the database is breaking after 2 hours. Check in SQL Server for any log that can help you understand this issue.
Now you should see why connection to the database is breaking after 2 hours. Check in SQL Server for any log that can help you understand this issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ahh good. I did post an objection but deleted it as I had misread what was happening :)
Glad you solved it.
Glad you solved it.
ASKER
My College manged to resolve this as it was a VEEAM snapshot causing the disconnection
Have you tried rebooting?