0
Fixed

SapHR Test Harness Issues

Richard Courtenay 6 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 3 years ago 7

A new version of the test harness was provided to us for testing this solution, version is 3.0.1.

I've extracted the archive and run the executable. The executable is not in the Identity Broker directory.

I get an error regarding missing DLLs

System.IO.FileNotFoundException: Could not load file or assembly 'SAP.Connector.Rfc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' or one of its dependencies. The system cannot find the file specified.
File name: 'SAP.Connector.Rfc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
   at SAP.Connector.RfcConnectorLoader.LoadRfcConnector()
   at SAP.Connector.RfcConnectorLoader.GetRfcConnection(IDestination dest)
   at SAP.Connector.Connection.GetNewConnection(IDestination dest)
   at SAP.Connector.Connection.GetConnection(IDestination dest)
   at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 451
   at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

To try to get around this, I copied the missing DLL (there are two) from the Identity Broker service directory, but I then get the error

System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
   at SAP.Connector.Connection.Open()
   at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 455
   at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58

Event log error

Fault bucket , type 0
Event Name: PCA2
Response: Not available
Cab Id: 0

Problem signature:
P1: Unify.TestHarness.SapHrCommunicator.exe
P2: 3.0.1.3
P3: Unify.TestHarness.SapHrCommunicator
P4: UNIFY Identity Broker for SAP HCM
P5: UNIFY Solutions Pty Ltd
P6: 200
P7: -1
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\Users\a16716.TESTINTERNAL\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_Unify.TestHarnes_18e927a83648e251bb989378285ab8f6680a1e1_2d5cb42b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2076e8d0-3f55-11e2-8a8f-005056ba0004
Report Status: 4
Affected Versions:
Fixed by Version:

Adam, are you the correct person to assign this to?

Updated second error message, which was to be

System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
   at SAP.Connector.Connection.Open()
   at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 455
   at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58

Richard, I have uploaded Identity Broker for SAP HCM v3.0.1 x86 test harness.zip on [SUBIDBSAP:Downloads].

Please let me know how it goes.

Hi Adam, that appears to have resolved the issue. The DLL's SAP.Connector.Rfc.dll and librfc32.dll were both required and missing from the zip archive. I got them from the Identity Broker Services folder for now however.

Once I added those two dll's, everything appeared to function fine.

please see previous comment. I'm happy with the resolution, but want to assign back in case you want to get those dlls into the archive.

Otherwise all good.

I've added those two dll's into the archive.

Thanks.