I recently worked on a project where we were polling multiple SQL databases across multiple servers and there was one server that would occasionally get skipped due to timeout delays. We adjusted our wait times in VFP, but still on occasion this would happen. IT did further stress testing on the server and found the network card was going bad. Replaced card and problem vanished. If other locations are working doing the same process, then I would focus on local network environmental elements such as the network switches, cables or cards.
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Frank Cazabon Sent: Wednesday, May 02, 2018 1:08 PM To: profoxtech@leafe.com Subject: [NF] Network Request timed out
I am having some problems when running code that synchronises data between 2 SQL Servers using SM Sync Framework. This code runs fine at about 50 other sites.
I am getting time out errors reported:
TCP Provider, error: 0 - The semaphore timeout period has expired
Google has suggested this site https://sqlserverscribbles.com/2013/02/15/tcp-provider-the-semaphore-timeout... as possible solutions but I wanted to make sure there is actually a problem before I try to fix it as I am not a network guy. My client doesn't have anyone who manages their network for them either.
I found a suggestion to run this command:
ping -t hostname > out.txt
so I did that and left it running for about 4 and a half hours. In that period I got 38 Request timed out messages (out of 18,685 total messages, so 18,643 were successful, the majority in 3 or 4 ms but pretty regularly going up to 22 or 23ms).
Is this normal, or do you think they have a problem?