FIX: CmdExec May Cause Exception Violation on Scheduled Tasks (171323)
The information in this article applies to:
This article was previously published under Q171323
BUG #: 17090 (SQLBUG_65)
SYMPTOMS
Scheduled tasks of type CmdExec may cause an exception violation. A message
similar to the following will appear in the Event Viewer:
EventID: 212
Source: SQLExecutive
User: N/A
Type: Error
Category: Task Engine
Task <task no>, '<task name>' has caused an exception violation in the
CmdExec subsystem, and has been terminated.
Even if the scheduled task, (that is, SQLMaint), completes successfully, it
shows a Last Run Status of "Failed" in the Manage Scheduled Tasks screen
within SQL Enterprise Manager. The Task History screen does not display any
error message to explain the failure.
CAUSE
This behavior is a result of a problem with the CmdExec utility. While
running, Cmdexec.dll creates a temporary file that holds the redirected
stdio and stderr output for the task. If the number of bytes within this
file happens to be within certain ranges, an exception violation is
generated.
WORKAROUND
To work around this problem, adjust the size of the output written to stdio
and stderr by the CmdExec task being scheduled. If you are unsure about
what output is being generated, try running the task at a command prompt
and observing the results written to the screen. Increase or reduce the
number of bytes written by at least two bytes to avoid exposure to this
problem.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a For more information, contact your primary support provider.
Modification Type: | Major | Last Reviewed: | 3/14/2006 |
---|
Keywords: | kbBug kbfix kbusage KB171323 |
---|
|