November 13, 2018 at 5:09 am
We have recently migrated a virtualised server hosting SQL server 2014 to a new physical machine. Since the migration we have noticed an increase number of these errors, and they are causing issues for users of a legacy web application.
I have checked the configuration for the NIC, and Chimney Offload State is disabled. However, Receive-Side Scaling state is enabled.
Please can anyone tell me if Receive-Side Scaling should be disabled and if so why.
Thank you.
November 13, 2018 at 6:22 am
jon.cox - Tuesday, November 13, 2018 5:09 AMWe have recently migrated a virtualised server hosting SQL server 2014 to a new physical machine. Since the migration we have noticed an increase number of these errors, and they are causing issues for users of a legacy web application.I have checked the configuration for the NIC, and Chimney Offload State is disabled. However, Receive-Side Scaling state is enabled.
Please can anyone tell me if Receive-Side Scaling should be disabled and if so why.
Thank you.
There have been some issues with network communications when Microsoft introduced the Scalable Network Pack. Chimney offload, RSS, and NetDMA are all features of SNP so when issues have been seen, it's usually suggested to disable all as the NIC may not support the features. And some NICs that do support the features have had problems with it. It's not as much of an issue on the later OS versions but it depends on the NIC and the drivers. For more information:
"General Network error", "Communication link failure", or "A transport-level error" message when an application connects to SQL Server
Sue
November 16, 2018 at 11:10 pm
Recieve Side Scaling enables the network load from a network adapter to be distributed across multiple CPUs in a multiprocessor computer. We disabled it to prevent it from a lot of weird issues done by NIC drivers. Get an update from the NIC vendor or use a better NIC driver that can use these features in an effective way. Make sure that all latest updates are installed on the server machine. BIOS update for the Server, it may resolve your problem.
Take a look at this article, it discusses various possible reasons and workaround of SQL error 4014:
https://www.sqlserverlogexplorer.com/causes-of-sql-error-4014/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply