Brandie Tarvin (2/2/2015)

---

Jeff Moden (2/2/2015)

---

Brandie Tarvin (2/2/2015)

---

UPDATE:

We have some issues with changing the TCP Chimney Offset (corporate owns these servers and our server guy is leery of playing with the settings). The suggestion of changing the packet size in SQL Server didn't work. And given the earlier comment of not turning off IPv6, we opted not to play with that (also another corporate issue involved here).

A coworker, however, was following a different tack.

Given that the problem exists not just with SQL Server, but with the OS copying of the files, he went searching and found a registry key (Session Info) that could be causing the problem. So he went in and changed the key last week. This weekend we had a bunch of restores happening in Dev and lo and behold, nothing failed!

So he seems to be on to something.

What did he change it from/to?

He created a new key at \HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\ParametersValue type: Dword

Value name: SessTimeout

Value: 360

He mentioned that it could be any value, but he chose 360 because all the research he did indicated that was a good consistent value.

This change was made in all our environments, Dev, Test and QC, but we've only tested it so far in Dev. I still had issues in Test right after he changed it, so I don't know if that had anything to do with Test needing to be restarted or not. We have NOT restarted any of our servers (that I am aware of), so I'll probably try Test again as soon as we're done with month end support.