Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
In Microsoft SQL Server 2005 with Service Pack 1 (SP1), when you use the BULK INSERT statement to bulk import a data file into a table, the bulk import operation fails. Additionally, you receive the following error message:
Location: lockbyte.cpp:445 Expression: colid > 0 SPID: [spidvalue] Process ID: [processIDvalue] Msg 7399, Level 16, State 1, Line 3 The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error. Msg 7330, Level 16, State 2, Line 3 Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)". Msg 3624, Level 20, State 1, Line 3 A system assertion check has failed. Check the SQL Server error log for details
This problem occurs if the following conditions are true:
You apply the hotfix that is described in Microsoft Knowledge Base (KB) article 935446 on the computer that is running Microsoft SQL Server 2005 SP1.
You have a table that has a column of large object (LOB) data.
You want to bulk import a particular data file into the table.
The data file contains a column of data. You want to import this column of data into the column of LOB data in the table.
The data file contains another column of LOB data that has no corresponding column in the table. You skip this column during the import process.
SQL Server 2005 uses an interface to set up the bulk load provider. The interface creates orphan LOB values for bulk operations. SQL Server 2005 sets up the bulk load provider for the following columns of LOB data:
The column that exists in the table.
The column that does not have the corresponding column in the table.
When SQL Server 2005 tries to create an orphan LOB value for the column that does not have the corresponding column in the table, an error occurs.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
How to obtain the latest service pack for SQL Server 2005
You do not have to restart the computer after you apply this hotfix.
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.