Try each of the following steps in order until the error is resolved:

  1. If your SQL Server instance is installed and running on Windows Server 2008 or 2008 R2 operating system, and the errors occur on multiple workstations check the settings in Microsoft Article 942861
  2. Reboot the workstation
  3. Update/Repair the workstation
  4. Change Power Options to prevent the computer from shutting off after long periods of inactivity
  5. Disable the network card power management feature:
    1. Right-click My Computer and select Properties.
    2. Click Device Manager.
    3. Click the plus sign to expand the Network adapters tree.
    4. Select the appropriate Network Interface Card (NIC) from the list.
    5. Select Action, Properties from the menu bar.
    6. Select the Power Management tab.
    7. Unmark the 'Allow the computer to turn off this device to save power.' checkbox
    8. Click OK.
  6. Disable the wireless connection on the problem workstation:
    1. Open Control Panel.
    2. Click on Network and Sharing Center
    3. Click Change Adapter Settings
    4. Right-click on the wireless connection and select disable.
    5. Connect to a wired network.
    6. Log out and back in.
  7. Recreate the Windows user profile
  8. Download and install the latest version of the Microsoft Data Access Components (MDAC)
  9. Test for General Network errors using Microsoft TechNET article The Cable Guy: Network Diagnostics & Tracing in Windows 7
  10. Give the user the appropriate NTFS Permissions
  11. If the issue is occurring on multiple workstations, restart the SQL Server service:
    1. Click Start and type Services.msc, and press enter.
    2. Scroll down to your SQL Server instance.
    3. Right click and select Restart
  12. Run a continuous ping on a workstation experiencing the issue:
    1. Click Start, Select Run
    2. Type cmd and press Enter
    3. Click OK
    4. Type ping –t servername (where servername is the SQL server name)
    5. When the error occurs press Ctrl + C

The number of packets lost should be 0.  If the number of packets lost is higher than 0, you are experiencing a networking issue and losing connection with the database server. Refer to Microsoft Solution 325487 for assistance.

Note: We provide links to third-party websites in an effort to help you resolve your issue. We are not responsible for the information on third-party websites, and we cannot assist in implementing the solutions on these websites.