BUG: Unhandled Exception w/Executive If Return Code Not in Range

Last reviewed: October 27, 1997
Article ID: Q175487
The information in this article applies to:
  • Microsoft SQL Server version 6.5
BUG #: 17182 (Windows: 6.5)

SYMPTOMS

An unhandled exception error may occur in SQL Executive if the process exit code from a CmdExec task is not between -9999 and 99999 (that is, if the return code exceeds five positions when expanded with wsprintf). For example, if the return value is 123456, SQL Executive will cause an access violation (AV). The stack is corrupted and the only function on the stack is ntdll!RtlAllocateHeap. You may also encounter the following error when you try to start SQL Executive after receiving the AV:

   SQLExecutive - DLL initialization failure Initialization of the dynamic
   link library c:\windows\system32\user32.dll failed. The process is
   terminating abnormally.

WORKAROUND

To work around this problem, use the return code in the range of -9999 and 99999.

STATUS

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

MORE INFORMATION

This problem is compounded by the fact that the user interface of SQL Enterprise Manager lets you define a process exit code up to six characters wide (in the range of -99999 and 999999).


Additional query words: number SEM
Keywords : kbbug6.50 SSrvEntMan kbusage
Version : WINNT:6.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbworkaround


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: October 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.