HPC - FIPS
-
Thursday, 14 June, 2012 2:13 PM
Hi
I've installed HPC 2008 R2 and the cluster is working fine. However, when local security setting "System cryptography: Use FIPS compliant algorithms for ..." was enabled, HPC Scheduler was unable to start.
- Wonder if this is due to failure when connecting to DB server? Verified DB Server doesn't have FIPS enabled.
- Is there any other setting to tweak HPC server to bypass FIPS while enabling the "System cryptography: Use FIPS..." above?
Tks for your advise.
All Replies
-
Friday, 15 June, 2012 7:21 AM
Exception logged in event. Anyone can help? Tks in advance! :)
Exception detail: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.RijndaelManaged..ctor() at Microsoft.Hpc.Activation.Cipher.CreateCipher() at Microsoft.Hpc.Activation.Cipher..ctor(Byte[] key) at Microsoft.Hpc.Scheduler.Communicator.Remoting.NodeController..ctor() at Microsoft.Hpc.Scheduler.Communicator.Remoting.NodeController.Start(Boolean nodeSim) at Microsoft.Hpc.Scheduler.Communicator.Remoting.RemotingNodeCommunicator.Start() at Microsoft.Hpc.Scheduler.ResourceController.NodeCommunicationManager..ctor(ISchedulerStore store, Boolean nodeSim) at Microsoft.Hpc.Scheduler.ResourceController.ResourceController.Start(ISchedulerStore store, GlobalNodeCache nodeCache, Boolean nodeSim, Int32 port) at Microsoft.Hpc.Scheduler.SchedulerSvc.StartSvc() Current stack: at Microsoft.Hpc.Scheduler.SchedulerTracing.TraceException(String facility, Exception exception) at Microsoft.Hpc.Scheduler.SchedulerSvc.StartSvc() at Microsoft.Hpc.Scheduler.SchedulerSvc.OnStart(String[] args) at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)