[NF] Network Request timed out

[Frank Cazabon]

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-period-has-expired/
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?
--
Frank.

Frank Cazabon


_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/de3f86f0-46e6-391a-db10-***@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who a

[Paul H. Tarver]

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-***@leafe.com] On Behalf Of Frank Cazabon
Sent: Wednesday, May 02, 2018 1:08 PM
To: ***@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-period-has-expired/
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?
--
Frank.

Frank Cazabon


[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/065e01d3e252$b0c2fa00$1248ee00$@tpcqpc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Frank Cazabon]

Thanks, I'm just going to pass the info over to them and tell them they need to hire a network consultant to investigate it. Just wanted to know if that level of timeouts is normal or not.

Post by Paul H. Tarver
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-----
Sent: Wednesday, May 02, 2018 1:08 PM
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.
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-period-has-expired/
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.
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?
--
Frank.
Frank Cazabon

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/18131C15-2F71-4C69-9F5B-***@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Michael Oke, II]

You are running pings over the internet, the result of those will be tied
to the level of service being provided at each site.

Post by Frank Cazabon
Thanks, I'm just going to pass the info over to them and tell them they
need to hire a network consultant to investigate it. Just wanted to know if
that level of timeouts is normal or not.

Post by Paul H. Tarver
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-----
Sent: Wednesday, May 02, 2018 1:08 PM
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.
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-period-has-expired/

Post by Paul H. Tarver
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.
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?
--
Frank.
Frank Cazabon

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACBEV=XtYfFHn+***@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Alan Bourke]

Frank

Post by Frank Cazabon
My client
doesn't have anyone who manages their network for them either.

Why not?

Anyway if it is a LAN I would expect the continous ping to come back under 10ms if not under 1ms at all times, without any timeouts.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm

Post by Frank Cazabon
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.
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-period-has-expired/
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.
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?
--
Frank.
Frank Cazabon

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers

[Frank Cazabon]

They are the cheapest client I have. Scrimp on everything.

This is running through log me in hamachi VPN over the internet, not a LAN.

Post by Alan Bourke
Frank

Post by Frank Cazabon
My client
doesn't have anyone who manages their network for them either.

Why not?
Anyway if it is a LAN I would expect the continous ping to come back
under 10ms if not under 1ms at all times, without any timeouts.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm

Post by Frank Cazabon
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.
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-period-has-expired/

Post by Frank Cazabon
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.
ping -t hostname > out.txt
so I did that  and left it running for about 4 and a half hours. In

that

Post by Frank Cazabon
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?
--
Frank.
Frank Cazabon

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/C1ADE2FE-4E01-4999-A55A-***@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages