BUG: SQLExec Account > 30 Chars Can Cause AV in Repl Tasks

 Last reviewed: May 2, 1997
Article ID: Q150262

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG#: 13678 (6.00)

SYMPTOMS

If the account name for SQLExecutive as returned by sp_helpdistributor exceeds 30 characters, the LogReader and SYNC task can fail with an access violation. An error is reported in the Event Log as: 

   Event ID:  212  Source: SQLExecutive Category: Task Engine
   Event 2 - <task name> has caused an exception violation in the
   <LogReader or SYNC> subsystem, and has been terminated.

CAUSE

The problem should only occur if SQLExecutive is logged on with a domain account, because local accounts are returned in sp_helpdistributor with a ".\" proceeding the account name, and local accounts can only be maximum 20 characters in length.

WORKAROUND

Use an account for SQLExecutive so that the account name returned from sp_helpdistributor does not exceed 30 characters.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem has been corrected in Microsoft SQL Server 6.5. For more information, contact your primary support provider.

Additional query words:
Keywords : kbbug6.00 kbprg SSrvErr_Log SSrvProg
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.