Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.
Consider the following scenario:
You have a computer that has Microsoft SQL Server 2008 Service Pack 1 (SP1) Cumulative Update 4 installed. This cumulative update is described in the following Microsoft Knowledge Base (KB) article:
973602 Cumulative update package 4 for SQL Server 2008 Service Pack 1
You have a Microsoft SQL Server 2008 Integration Services (SSIS 2008) package that uses Microsoft Connector 1.0 for SAP BI.
You run the package, and some data is being loaded in parallel in the package.
In this scenario, an exception may be thrown, and you receive the following error message:
Microsoft.SqlServer.Dts.SapBw.Connectivity.ERPException: The connection is not valid. at Microsoft.SqlServer.Dts.SapBw.Components.SapBwSourceBWLoader.ProcessInput(Int32 inputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket) SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "SAP BI Destination20" (234) failed with error code 0x80131500 while processing input "SAP BI Destination Input" (237). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal andwill cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
977443 Cumulative update package 6 for SQL Server 2008 Service Pack 1
Note 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 2008 fix release. We recommend 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Note The exception describe in the "Symptoms" section can also occur in other scenarios. For example, an internal server error can also cause this exception.Therefore, applying this cumulative update does not fix all problems that cause this exception.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates