Article ID: 972365 - View products that this article applies to.
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.
Consider the following scenario.
In this scenario, you run the SSIS package. When SSIS tries to write the BLOB data to the temporary storage, you receive the following error messages:
Error message 1
Error message 2
Error: 0x80070050 at Data Flow Task, DTS.Pipeline: The file exists.
Error message 3
Error: 0xC0048019 at Data Flow Task, DTS.Pipeline: The buffer manager could not get a temporary file name. The call to GetTempFileName failed.
Error message 4
Error: 0xC0048013 at Data Flow Task, DTS.Pipeline: The buffer manager could not create a temporary file on the path "Path". The path will not be considered for temporary storage again.
Error message 5
Error: 0xC0047070 at Data Flow Task, DTS.Pipeline: The buffer manager cannot create a file to spool a long object on the directories named in the BLOBTempStoragePath property. Either an incorrect file name was provided, or there are no permissions.
Error message 6
Error: 0xC02020E5 at Data Flow Task, Flat File Source : Writing long object data of type DT_TEXT, DT_NTEXT, or DT_IMAGE to Data Flow task buffer failed for column "ColumnName".
Error: 0xC0208266 at Data Flow Task, DTS.Pipeline: Long data was retrieved for a column but cannot be added to the Data Flow task buffer.
It is theoretically possible that a similar problem may also occur in the following scenario:
If you specify additional folders in the BLOBTempStoragePath property or in the BufferTempStoragePath property, and then run the SSIS package again, you find the additional paths are ignored and the SSIS package still does not run successfully.
The folders that are designated in the BufferTempStoragePath or BLOBTempStoragePath properties contain temporary files. These temporary files are named in a range from DTS.tmp through DTSFFFF.tmp. The number range is from 0x0 through 0xFFFF. For example, possible temporary file names include DTS.tmp, DTS1.tmp…, and DTSFFFF.tmp. There are 65,536 possible file names in total. When there are more than 65,536 files, SSIS may run out of file names and throw the errors that are mentioned in the Symptom section.
The fix for this issue was first released in Cumulative Update 5 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972511Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/972511 /LN/ )Cumulative update package 5 for SQL Server 2005 Service Pack 3
960598Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(https://support.microsoft.com/kb/960598/LN/ )The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
To work around this issue, use one of the following methods:
Method 1Increase the buffer size by setting the DefaultBufferSize property to the maximum value of 104,857,600.
Note If you use this method, there may be more memory consumption when you run the SSIS package.
Method 2In the design stage, try to reduce blocking transforms or downstream bottlenecks after the point where the BLOB columns are introduced to the data flow task. This method may reduce the possibility that the limit will be reached.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply this hotfix, the following two problems are resolved:
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/935897/ )An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
913089For more information about the new features in SQL Server 2005 Service Pack 3 (SP3) and about the improvements in SQL Server 2005 SP3, visit the following Microsoft Web site:
(https://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
http://go.microsoft.com/fwlink/?LinkId=131442For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 972365 - Last Review: August 17, 2009 - Revision: 1.1