I have installed the Microsoft Connector 1.0 for SAP BI (April 2009 feature pack) on a Windows 2008 R2 server with SQL 2008 SP1 (Cum Update 6). I have established an SAP BI Connection and SAP BI Data Source. The Data Source is able identify the OHS_Destination, Process Chain, and respective Columns. Confirm that the librfc32.dll is installed correctly. The Output of the Data Source is connected to a simple OLEDB destination. When executing the package, it fails at the SAP BI Data Source with the following errors: [SAP BI Source] Error: Microsoft.SqlServer.Dts.SapBw.Connectivity.ERPException: FAILED Execution failed. at Microsoft.SqlServer.Dts.SapBw.Connectivity.RFCFunction.Execute() at Microsoft.SqlServer.Dts.SapBw.Components.OHSExtractor.ExtractNow(Boolean InRuntimeMode, String GatewayHost, String GatewayService, String ProgramID, String ProcessChain, String DestinationName, String ExecutionMode, String PropertyRequestID, Int32 Timeout) [SAP BI Source [61]] Error: Microsoft.SqlServer.Dts.SapBw.Connectivity.ERPException: FAILED Execution failed. at Microsoft.SqlServer.Dts.SapBw.Components.OHSExtractor.ExtractNow(Boolean InRuntimeMode, String GatewayHost, String GatewayService, String ProgramID, String ProcessChain, String DestinationName, String ExecutionMode, String PropertyRequestID, Int32 Timeout) at Microsoft.SqlServer.Dts.SapBw.Components.SapBwSourceOHS.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket) [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "SAP BI Source" (61) returned error code 0x80131500. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. Your assistance is appreciated. Let me know if I can provide any additional information that may be of help. Thanks

I received similar errors when I was connecting to DB2. I since then used the .net native provider instead and the connection worked, interestingly, I was able to set my data source and preview data w/o issues. There are should be another option(s) in the drop-down of available drivers in your Data Source, please try it.Arthur

I attempted your suggestion and created a data source (.NET SAP BW OLE DB provider) and then specified this new connection mgr to the data source. Unfortunately that did not resolve the underlying problem. Any further suggestions?

When configuring the SAP Data Source in SSIS, under the Connection Manager selection: the OHS list is correctly populated, the ProcessChain +lookup is correctly populated, thus confirming the SAPBI connection however the Gateway Server +Lookup and Preview buttons both return EXECUTION FAIL is there another option/setting to ensure that these functions return successful. the underlying issue is the errors upon execution the package.

I can NOT even make the SAP BI connection manager to work. it say"xxxx unable to load librdc.dll xxxxxx application configuration incorrectlyxxxxxxxxx" could some point me to right direction what is missing I have lib under system32 SQL 2008 S@ SAP BI connecter 2008 :)

Perhaps you should ask a question at an SAP related forum, too?Arthur My Blog

now: SSIS wait for notification...forever... From searching on web, there is but related to sQL 2008. But common sense: i have SQL 2008 R2, does later release should make up misisng in SQL 2008 accumulative SPs? (urgent!)

Hi, have you found some solution? I have the same problem - all connection settings from SSIS to SAP BW are set by MS definition. Server is 64bit, librfc32.dll inserted into windows\syswow64\, SAP BI connector 1.0 installed. Package can connect to SAP server, OHS destination extracts data but then it is waiting for notification...forever..and fails on timeout after cca 5 mins (as it is set). Please any advice is appreciated as I have already tried all I could even with MS guys assistance. This post is the only one which is describing just the same problem as I have... Thanks for any help, Jitka

Finally we resolved this issue: ProgramID for RFC was registered from another server then SAP BW => data extracted but tried to send to this server instead of MS BI. It was SAP issue not MS BI but maybe it will help somebody in the future. Now my SSIS package works fine. Jitka

How do you configure the RFC? the JCo provider, the jdbc driver? I have the same problem, the MS connector in BI Developer studio connects with BW and i can see the open hub and process chain from there, but when i execute the package sends this errors: [SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console. [SAP BI Source] Error: Proceso "Proceso transferencia datos", variante "0CRM_PROD -> ZCRMPRODT" tiene status "Finalizado con error" (inst."DTPR_4R9RUS7Y7OOEOLTL78C7RBIHI") [SAP BI Source] Error: The component is stopping because the Request ID is "0". [SAP BI Source] Error: No data was received. [SAP BI Source [1]] Error: System.Exception: No data was received. en Microsoft.SqlServer.Dts.SapBw.Components.SapBwPipelineComponent.FireErrorAndException(String message) en Microsoft.SqlServer.Dts.SapBw.Components.SapBwSourceOHS.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers) en Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket) [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "SAP BI Source" (1) returned error code 0x80131500. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. Task Data Flow Task failed Regards Jonathan

The warning at the top you can safely ignore. And the error needs to be checked against SAP KB, at the moment I am thinking you are using an incorrect driver. Perhaps you ought to opt for using the one from http://www.microsoft.com/en-us/download/details.aspx?id=8824 as per http://blogs.msdn.com/b/mattm/archive/2008/03/10/new-connectivity-options-in-2008.aspxArthur My Blog

Hi Jitka, We are facing same problem. Can you explain what did u exactly did n? thanks Saurabh