HP ALM Lab Service installation on Unified Functional Testing host (detected in version: HP ALM 12.02 and UFT 12.02)
The issue is with HP ALM 12.02 and UFT 12.02 and installing the Lab Service on a Windows 2008 R2 Server.There are no issues with the installation and configuration of the Lab Service or the ability to add the Host in Lab Management. The issue comes when you use the check host operation and it will time out at 20%. After using check host it will time out.
To validate you are experiencing the same error log into our your host and review the \HP.ALM.Lab.Agent.RemoteService logs. The error is indicated as "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms".
Here is the full error log from activity "Task Getter":
Error processing new task HP.ALM.Lab.Agent.ExecutionAgentAPI.Exceptions.DecryptionException: Failed to decrypt ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.RijndaelManaged..ctor() --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture) at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object args) at System.Security.Cryptography.SymmetricAlgorithm.Create() at HP.ALM.Lab.Agent.ExecutionAgentAPI.Util.CryptoUtilities.Decrypt(String cryptotext) --- End of inner exception stack trace --- at HP.ALM.Lab.Agent.ExecutionAgentAPI.Util.CryptoUtilities.Decrypt(String cryptotext) at HP.ALM.Lab.Agent.ExecutionManager.Activities.AsyncGetTaskActivity.HandleExecutionItem(String encryptedXmlString) at HP.ALM.Lab.Agent.ExecutionManager.Activities.AsyncGetTaskActivity.DoExecute()
Screen Shot of Original Log Issue:
It has been confirmed by HP support that the HP ALM Lab Service is non FIPS compliant and will not work with this local security policy enabled. The "fix" for this issue is to disable the FIPS compliant hashing algorithm local security policy as seen in the screen shot below.
Screen shot of FIPS local security policy: