Advanced Workflow Hangs on the starting stage Without On-Screen Error

[KB-Sync1]

Article Number

000033981

Applies To

Product(s): Archer
Version(s): All Versions
Primary Deployment: On Premises

---

Description

After building an Advanced Workflow in Archer, the workflow does not get past the starting stage after content enrollment. The user screen will hang indefinitely.

The Advanced 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>

   

Cause

This implementation is not part of the Windows Platform FIPS validated cryptographic.

Resolution

Import 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