2

In Sql Server2008 R2 and Windows Server 2008R2, when I start Replication I have this error:

TCP Provider: The semaphore timeout period has expired

Please help me to solve it.

dario
  • 5,149
  • 12
  • 28
  • 32
Nima MashhadiZadeh
  • 167
  • 1
  • 4
  • 13
  • Do a web search on "TCP Provider: The semaphore timeout period has expired". There are many results which explain what's happening and with various possible solutions.# – simon at rcl May 23 '15 at 08:31
  • We Use Merge Publication & "pull subscription " ,This error was appeared recently , – Nima MashhadiZadeh May 23 '15 at 08:55
  • Fine. So go read the many links a se arch will provide you with and see what you can find out and try. Come back with what you've tried and what happened. We don't do your research for you, I'm afraid.# – simon at rcl May 23 '15 at 09:03
  • OK,i read some link for Example [https://support.microsoft.com/en-us/kb/942861] but, it didn't work – Nima MashhadiZadeh May 23 '15 at 09:15

1 Answers1

6

in order to fix the error:

System.IO.IOException: The semaphore timeout period has expired.

​Solution​

I have done below NIC changes to resolve this error.

  1. Open the Network and Sharing Center.
  2. Right click on Ethernet Adapter>>Properties
  3. Select Client for Microsoft Networks
  4. Click on Configure Tab
  5. Click on Advanced Tab

  6. And then - Disable the below settings

    • IPv4 Checksum offload
    • Large Send Offload V1(Ipv4)
    • Large Send Offload V2(Ipv4)
    • TCP Checksum Offload(IPv4)
    • UDP Checksum Offload(IPv4)

After disabling the above settings; it resolved our Semaphore error.