BUG: 32-bit ISQL.EXE Does Not Properly Set ERRORLEVEL

Last reviewed: April 30, 1997
Article ID: Q121832

The information in this article applies to:

  - Microsoft SQL Server version 4.21

BUG# NT: 10377 (4.21)

SYMPTOMS

The 32-bit version of ISQL.EXE does not properly set ERRORLEVEL under certain conditions. If arguments or data for arguments are invalid, the ERRORLEVEL used for batch file processing under Windows NT is not set to 1.

The following is an sample .CMD file run under Windows NT normally used for batch file processing:

   echo off
   isql /Usa /P /i test.sql
   if errorlevel 1 echo Error!
   echo on

In this situation, TEST.SQL does not exist. Therefore, ISQL will display an error to stdout indicating an invalid input file. However, errorlevel is not set to 1.

WORKAROUND

Use the 16-bit MS-DOS or OS/2 version of ISQL.EXE on Windows NT.

STATUS

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

Additional query words: Windows NT
Keywords : kbbug4.21 kbtool SSrvISQL
Version : 4.21
Platform : WINDOWS

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