The information in this article applies to:
SYMPTOMSIf Proxy Server 2.0 is configured to log on to a SQL Server database and the database connection gets lost, Proxy Server 2.0 may stop logging until the corresponding Proxy Server service is restarted. The loss of the database connection may occur because SQL Server was stopped. CAUSEThe Proxy Server 2.0 ODBC logging module does not support the reconnection of lost database connections. RESOLUTION
A supported fix that corrects this problem is now available from
Microsoft, but has not been fully regression-tested and should be applied
only to systems experiencing this specific problem. http://support.microsoft.com/support/supportnet/default.asp The English version of this fix should have the following file attributes or later:
NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support STATUSMicrosoft has confirmed this to be a problem in Proxy Server version 2.0. MORE INFORMATIONWith the updated Msplog.dll installed, the Proxy Server logging module now detects a lost database connection whenever it attempts to write a log record. After a one-minute timeout, when another log request comes in, it tries to reconnect to the database and continues logging upon the next log request. If the reconnection to the database does not succeed, it will be retried once a minute whenever a log request comes in. This process is handled separately for every Proxy Server service. Additional query words: proxie hotfix hot fi x qfe quick engineering pa tch 4.00 2.00
Keywords : |
Last Reviewed: November 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |