Microsoft KB Archive/101607

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 08:19, 20 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



BUG: BCP Fails with Text Greater than 255 Bytes and Format

Last reviewed: May 5, 1997
Article ID: Q101607

The information in this article applies to:

  • Microsoft SQL Server Programmer's Toolkit, version 4.2

BUG# 8939 (4.2a)

SYMPTOMS

BCP fails to load data into SQL Server when attempting to load data files including long text fields and a format file specifying the length of the text data to be greater than 255 bytes. Versions of BCP 4.2a and later fail without generating an error message. BCP 4.2 fails to load data and generate a "bcp_readfmt() failed" error. BCP version 1.11 loads the data, but the following error message appears:

   operating system error:
      (null)
   DB-Lib error
      I/O Error while reading bcp data file

CAUSE

The BCP utility does not handle format files specifying data field lengths of greater than 255 characters correctly.

WORKAROUND

A character mode bulk insert using appropriate field delimiters allows the data to be loaded using the BCP.EXE utility.

STATUS

Microsoft has confirmed this to be a problem in BCP versions 4.2 and 4.2a. 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.20 kbbug4.20a kbtool SSrvBCP SSrvWinNT
Version : 4.2a | 4.2a | 4.2 4.2a
Platform : MS-DOS OS/2 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: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.