BUG: BCP Fails with Unhandled Exception on MIPS Servers

Last reviewed: May 5, 1997
Article ID: Q153416
The information in this article applies to:
  • Microsoft SQL Server version 6.0

SYMPTOMS

The bulk copy of data into a table on a MIPS computer will fail with an unhandled exception in Bcp.exe. The exception occurs only when a format file is used to conduct the bulk copy operation. Character mode BCP works correctly. The bulk copy operation of a data file, when using a format file fails with the following error message on the MIPS computer:

    BCP.exe  Application error.
     The instruction at "----" referenced memory at " ----". The memory
   could not be written.
     C++ debugger says "Unhandled exception in BCP.exe [NTWDBLIB.DLL]:
   0xc0000005 :: Access Violation.

WORKAROUND

You can work around this problem by remotely conducting the operation from an Intel machine. Thereafter, from a local MIPS computer, you can use character-mode BCP to store data in a file. This data file can then be used to bulk copy into the table using character mode BCP as need be.

STATUS

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


Additional query words: BCP MIPS format character mode
Keywords : kbbug6.00 SSrvDRI
Version : 6.0
Platform : WINDOWS
Issue type : kbref


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