FIX: dbopen Memory Leak of 32K On Failed Login Attempt

• Microsoft SQL Server, version 6.0

SYMPTOMS

A call to dbopen with an invalid password or an attempt to establish an invalid trusted connection causes a 32K memory leak. The private bytes for the process will climb by 32K each time the dbopen fails. You may also see Process\Non-Paged Pool bytes increase. Continued leaks may cause Windows NT to run to a low virtual memory state.

WORKAROUND

Ensure that all login attempts are valid.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.0. This problem was corrected in Service Pack 2 for version 6.0. To obtain this service pack or for more information, contact your primary support provider.

MORE INFORMATION

Some specific troubleshooting areas:

1. Check all passwords and password mappings. (Use the SQL Security Manager for mappings and the Control Panel Service application to verify startup information for the specific service.)

2. Enable failed and successful SQL Server logins. (Use the SQL Server Setup Security option.)

3. Logon as the secured user and use ISQL with the -E parameter to verify the user can establish a secured login.

4. Verify the net-library supports a trusted connection. (Use the SQL Server Client Configuration Utility to verify a named pipes or multi-protocol connection is being established.)

5. Verify the pipe name is correct. The pipe name must begin with \\.\pipe\... Anything else will cause an error when SQL Server attempts to create the pipe. Thus, named pipe connections will fail.

   Verify the pipe is opend by looking in the SQL Server errorlog.

6. Run SQLExecutive in debug mode. (sqlexec -c -v)

   **Specifically, retries of the replication processes can indicate failed

        logins.