BUG: Isql.exe Fails to Execute a Script Generated by SEM

Last reviewed: April 9, 1997
Article ID: Q156289

The information in this article applies to:

Microsoft SQL Server, versions 6.0 and 6.5

BUG #: 15617 (6.0)

       15813 (6.5)

SYMPTOMS

Isql.exe fails while running a script generated by SQL Enterprise Manager (SEM), if the script contains a line that is greater than 1,000 characters in length.

SQL Server 6.0 fails with the following error message:

   Application Error : The instruction at "0x0040756b" referenced memory at
   "0x00413000". The memory could not be "written."

SQL Server 6.5 fails with the following error message:

   Msg 170, Level 15, State 1: Incorrect syntax near '<some part of the
   script>.'

WORKAROUND

To work around this problem, run the script in either ISQL/w, or a Query Analyzer window of SQL Enterprise Manager.

STATUS

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

Additional query words: 6.0 6.5
Keywords : kbbug6.00 kbbug6.50 kbnetwork SSrvEntMan SSrvISQL
Version : 6.0 6.5
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 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.