BUG: SQLExecutive, CmdExec Task Output Is Not Properly Reported (197243)
The information in this article applies to:
This article was previously published under Q197243 SYMPTOMS
The SQLExecutive, CmdExec task opens a file and redirects the stdout and
stderr to it. When the task is complete SQLExecutive reads through the
file in 231 byte increments. If the output is not on a boundary, > 231
bytes, the data is not reported.
For example, 245 bytes causes a second read loop to take place but the
bytes read does not equal the requested buffer size of 231 bytes. The task
ignores the second read and reports the first 231 bytes instead of the last
231 bytes.
WORKAROUND
To avoid the problem you can attempt to ensure that the output of the task
is less than 231 bytes total or that the task output ends on a 231 byte
boundary.
STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5.
Modification Type: | Major | Last Reviewed: | 10/3/2003 |
---|
Keywords: | kbBug KB197243 |
---|
|