BUG: Long Database Names Can Cause AV in the Distribution Task

ID: Q150258

The information in this article applies to:

Microsoft SQL Server version 6.0

BUG#: 13530 (6.00)

SYMPTOMS

Long published and subscribed database names can cause an access violation (AV) failure of the distribution task with the following error reported in the Event Log:

Event ID 212; Source: SQLExecutive; Category: Task Engine
Event <task id> - <dist task name> caused an exception violation in the
Distribution subsystem, and has been terminated.

The Task History for the distribution task will report "Failure" with no message explanation and the task will no longer be Active.

WORKAROUND

Avoid using long names for published and subscribed databases. To avoid this particular problem, a database name of no longer than 10 characters is recommended for both the published and subscribed database.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This problem does not occur SQL Server version 6.5.

Additional query words: av


Keywords          : kbprg SSrvProg kbbug6.00 
Version           : 6.0
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 25, 1999