Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Microsoft Connector 1.1 for SAP BW - Connected and Mapped Table - Error Retrieving Data

$
0
0

We are able to connect and map the table from BW but the process does not bring over any of the rows populated via the SAP Process Chain.

Any help or insight would be greatly appreciated.

SQL Version: SQL 2008 R2 + SP1 / Microsoft Connector 1.1 for SAP BW

I have verified all of the following requirements for using the Microsoft Connector 1.1 for SAP BW:

  • OK - Windows Server 2003 and later, Windows Vista, or Microsoft Windows XP Professional with Service Pack 2.    
  • OK - SQL Server 2008 Integration Services. Microsoft Connector 1.1 for SAP BW needs to be installed on the same computer where Integration Services is installed.
  • OK - Windows Installer 4.5 and later.
  • OK - Extracting data using Microsoft Connector 1.1 for SAP BW from SAP BI system requires the SAP Open Hub license. For more information about SAP licensing, consult your SAP representative. 
  • OK - On the SAP BI system, SAP_BW component support package level 16 (as part of SAP NetWeaver Support Pack Stack 14) is required. SAP_BW component support package level 17 or higher is strongly recommended. 
  • OK - To use Microsoft Connector 1.1 for SAP BW in 32-bit (64-bit) mode on any 32-bit (64-bit) operating system, The 32-bit (64-bit) version of librfc32.dll needs to copied to the following location: %windir%\system32. 
  • N/A -To use Microsoft Connector 1.1 for SAP BW in 32-bit mode on a 64-bit operating system, the 32-bit librfc32.dll needs to be copied to the following location: %windir%\SysWow64.

What we know:

  1. In SAP they defined a simple process chain ( select f1, f2, etc. from Table_a - table_a has 32K rows )
  2. Using the new BI Connector we setup a data flow task that uses the "SAP BW Source", We can see the table structure and the test of the connection succeedsm and map source/target.
  3. We have verified that the SAP Process Chain is getting executed
  4. The temporary table that is defined on the SAP side is getting loaded with the 32000 rows of data ( confirmed by the BASIS team ) NOTE: The BASIS team was able to go into SAP and select the data from the table using our ID
  5. The data never gets to us ( see the results below ) and it has been confirmed that the two ports can talk.

SSIS Output:

SSIS package "Test_SAP_RemoteSQLSRVR.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at Data Flow Task, SSIS.Pipeline: Execute phase is beginning.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Process Start Process, variant Trigger Open hub ZOH_POS for SQL Interface has status Completed (instance 4OOO29EJ7YWPHMN46BB1BFMZ8)
Information: 0x3E8 at Data Flow Task, SAP BW Source: Process Data Transfer Process, variant ZCDPOSCP -> ZOH_POS_FULL LOAD has status Active (instance DTPR_4OOO29M7QXIF096KC5DDLHLP0)
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is waiting for a notification.
Information: 0x3E8 at Data Flow Task, SAP BW Source: A notification was received., RequestID=268507; NumberOfRows=33060; NumberOfPackets=1; OHS Destination=ZOH_POS
Information: 0x3E8 at Data Flow Task, SAP BW Source: The extraction process is finished.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Number of rows: 33060.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Number of packets: 1.
Information: 0x3E8 at Data Flow Task, SAP BW Source: RequestID: 268507
Information: 0x3E8 at Data Flow Task, SAP BW Source: OHS Metadata validation passed.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry.
Information: 0x3E8 at Data Flow Task, SAP BW Source: Current status of process chain "ZADHOC_SQL_OPEN_HUP" is: A.
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now retrieving PacketID, "1".
Information: 0x3E8 at Data Flow Task, SAP BW Source: The component is now processing an incoming packet that contains 0 rows.
Error: 0x3E8 at Data Flow Task, SAP BW Source: Fatal error during reading of database
Information: 0x3E8 at Data Flow Task, SAP BW Source: Wait for 20000 seconds and retry. 




Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>