000033981 - RSA Archer 6.1 Advanced Workflow Hangs on Workflow Start without on-screen error

Document created by RSA Customer Support Employee on Sep 9, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033981
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 6.1
Platform: Windows

 
IssueAfter building an Advanced Workflow in RSA Archer 6.1 the workflow does not get past initial step after the Start.
User Screen will hang indefinitely.
The workflow log only points to a FIPS exception for Microsoft Server. 
Error Message from Archer.AdvancedWorkflow.xml log.

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
  <EventID>0</EventID>
  <Type>3</Type>
  <SubType Name="Error">0</SubType>
  <Level>2</Level>
  <TimeCreated SystemTime="M/D/YYYY h:mm:ss PM" />
  <Source Name="Archer.NET" />
  <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
  <Execution ProcessName="WpJobMonitor" ProcessID="xxxx" ThreadID="xxxx"/>
  <Computer>SERVER_NAME</Computer>
</System>
<ApplicationData>
  <TraceData>
   <DataItem>
    <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
     <TraceIdentifier>Archer.NET</TraceIdentifier>
     <Description>This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.</Description>
     <AppDomain>WpJobMonitor.exe-WpAppDomain</AppDomain>
     <Exception>
      <Message>
      ---------- Exception ----------
      [System.InvalidOperationException]
      This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
         at System.Security.Cryptography.SHA1Managed..ctor()
         at Workpoint.BPM.Util.CryptoHelper.RsaCreateSignature(String stringIn, RSACryptoServiceProvider rsa)
         at Workpoint.BPM.Security.m.m(String a)
         at Workpoint.Monitors.PollingMonitorBase.GetServiceChannel[I](String endpointKey, String dsn)
         at Workpoint.Monitors.Job.a.n(a a)
         at Workpoint.Monitors.Job.a.b(Object a)
      </Message>

                    </Exception>
    </TraceRecord>
   </DataItem>
  </TraceData>
    </ApplicationData>
</E2ETraceEvent>

 
 

 

 


 
CauseThis implementation is not part of the Windows Platform FIPS validated cryptographic.
ResolutionImport Note: Please ensure to take a backup Registry prior to making changes in registry. Detail information on how to backup registry can be found on Microsoft website: https://support.microsoft.com/en-us/kb/322756 
  1. From the Start menu, in the search box, type regedit.exe, and then press Enter. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
  2. In Registry Editor, locate HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
  3. Under a subkey locate FipsAlgorithmPolicy
  4. Change the "Enabled" DWORD from 1 to 0 .
  5. Restart the system.
Reference information is available on Microsoft website:
https://support.microsoft.com/en-us/kb/811833

Attachments

    Outcomes