Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/170338

From BetaArchive Wiki
Knowledge Base


PRB: Anti-Virus Programs May Cause Named Pipes Connection Problem

Article ID: 170338

Article Last Modified on 1/24/2005



APPLIES TO

  • Microsoft SQL Server 6.0 Standard Edition
  • Microsoft SQL Server 6.5 Standard Edition



This article was previously published under Q170338

Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.

SYMPTOMS

Anti-virus software running on client computers may cause Named Pipes connections to Microsoft SQL Server to fail. The client application may stop responding, take a long time, or sometimes receive error 231, "Connection Busy." In the SQL Server error log, error 17832 "Unable to read login packet" may be logged. Connections to SQL Server using a different network protocol work normally.

CAUSE

When the client application requests to open a pipe, and if the anti-virus software is configured to scan all files, the anti-virus software treats the pipe as a file, and attempts to scan it. This results in opening the pipe is a "deny all" mode that prevents the client software from reading or writing to the pipe while connected to the server. After the pipe is opened in this mode, the client is not able to send the login packet to the server. This results in raising error 17832 "Unable to read login packet" in the SQL Server error log.

Other Named Pipes connections from the same client fail because the pipe is already open in a "deny all" mode that prevents the usage of the same pipe by those connections. This scenario results in receiving error 231 "Pipe busy" or "Connection Busy."

WORKAROUND

Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

Important These steps may increase your security risk. These steps may also make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to, or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you choose to implement this process, take any appropriate additional steps to help protect your system. We recommend that you use this process only if you really require this process.

To work around this problem, try the following suggestions:

  • Configure the anti-virus software to scan program files only.
  • Remove the anti-virus software and evaluate the SQL Server Named Pipes connection.
  • Contact the anti-virus vendor for suggestions on configuring the software.




Additional query words: virus antivirus detection WIN95 WIN-95 WIN odbc hang dblib named pipes stress

Keywords: kbnetwork kbprb kb3rdparty KB170338