-
- Enthusiast
- Posts: 59
- Liked: 3 times
- Joined: Sep 30, 2011 11:59 pm
- Full Name: Sam Pierce
- Contact:
FIPS error creating virtual lab
Hello,
I am having a strange message when creating a virutal lab on Veeam 5.
During the creation of the virutal lab at the "copying proxy appliance files" step it throws an error message of:
"This Implementation is not part of the WIndows FIPS validated Cryptographic alorithms"
I experienced this and there are several forum messages in relation to Enterprise Manger. I resolved it for VBEM by making the change to the web.config file.
However, I can't find any references to this error occuring during virtual lab creation.
Has anyone else seen this.
Thank you.
I am having a strange message when creating a virutal lab on Veeam 5.
During the creation of the virutal lab at the "copying proxy appliance files" step it throws an error message of:
"This Implementation is not part of the WIndows FIPS validated Cryptographic alorithms"
I experienced this and there are several forum messages in relation to Enterprise Manger. I resolved it for VBEM by making the change to the web.config file.
However, I can't find any references to this error occuring during virtual lab creation.
Has anyone else seen this.
Thank you.
-
- Chief Product Officer
- Posts: 31780
- Liked: 7280 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: FIPS error creating virtual lab
Hi Sam, I have never seen this, and have absolutely no idea what could be throwing this error?! Are you using clean Windows install without any 3rd party tools? Thanks.
-
- Enthusiast
- Posts: 59
- Liked: 3 times
- Joined: Sep 30, 2011 11:59 pm
- Full Name: Sam Pierce
- Contact:
Re: FIPS error creating virtual lab
Yes it is a clean Windows 2008 install.
-
- Veeam Software
- Posts: 21137
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: FIPS error creating virtual lab
Sam, please open a support case on this error as logs investigation is required here. Thanks.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 18, 2011 10:58 am
- Full Name: Colin McAdam
- Contact:
Re: FIPS error creating virtual lab
Sam, did you ever get this resolved? I am getting the same error on VEEAM 5 with vShere 5
(i understand this is not supported but this is a new installation of VEEAM and we had already upgraded our vSphere servers)
Thanks
Colin
(i understand this is not supported but this is a new installation of VEEAM and we had already upgraded our vSphere servers)
Thanks
Colin
-
- Veeam Software
- Posts: 21137
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: FIPS error creating virtual lab
Colin, I would recommend to wait until the official support of vSphere 5 in your case (please monitor this topic for the news). If the issue still persists, then please address our support team for investigation.
-
- Enthusiast
- Posts: 59
- Liked: 3 times
- Joined: Sep 30, 2011 11:59 pm
- Full Name: Sam Pierce
- Contact:
Re: FIPS error creating virtual lab
Support told me that Veeam wasn't FIPS compliant and to disable FIPS. Once I did the issue was resolved. Not certain I will be able to continue to run with FIPS disabled but for now it is working for me.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 18, 2011 10:58 am
- Full Name: Colin McAdam
- Contact:
Re: FIPS error creating virtual lab
I can confirm that the vSphere 5 support hotfix resolved this issue
Cheers
Colin
Cheers
Colin
-
- Expert
- Posts: 205
- Liked: 5 times
- Joined: Nov 22, 2010 7:57 pm
- Full Name: DS
- Contact:
[MERGED] : FIPS Error during SureBackup setup
Re: Veeam Support - Case # 00200218
I'm adding a Virtual Lab to our vSphere environment. At the end of the setup, I'm receiving a error.
What the issue? I've unchecked the proxy option and still getting the same error.
I'm adding a Virtual Lab to our vSphere environment. At the end of the setup, I'm receiving a error.
Code: Select all
4/23/2013 9:01:32 AM Getting infrastructure info
4/23/2013 9:01:44 AM Mounting vPower NFS datastore
4/23/2013 9:01:44 AM Creating resource pool 'Veeam Backup Lab'
4/23/2013 9:01:45 AM Creating VM folder 'Veeam Backup Lab'
4/23/2013 9:01:46 AM Creating virtual switch 'Veeam Backup Lab'
4/23/2013 9:01:53 AM Creating port groups
4/23/2013 9:01:54 AM Fail Copying proxy appliance files Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
4/23/2013 9:02:01 AM Deleting port groups
4/23/2013 9:02:06 AM Deleting virtual switch
4/23/2013 9:02:07 AM Deleting VM folder
4/23/2013 9:02:08 AM Deleting resource pool
4/23/2013 9:02:08 AM Fail Failed to create Virtual Lab
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
-
- Expert
- Posts: 205
- Liked: 5 times
- Joined: Nov 22, 2010 7:57 pm
- Full Name: DS
- Contact:
Re: FIPS error creating virtual lab
here is the solution...
Basically the way that our software is written has not been certified by NIST in where it is considered compliant with FIPS. Because of this when we try and make a call to the host using our cryptographic algorithm it is denied due to the implementation of the FIPs compliance policy in the GPO or Local Security Policy.
Any GPO that enforces FIPS compliance (or other encryption) will need to have Veeam products excluded, or you can disable this temporarily on the server by changing the requirement for a FIPs compliant algorithm by changing the registry key in:
HKLM\System\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy from "1"
[enabled] to "0" [disabled].
sorry for the bother. Veeam support responded very quick...
Basically the way that our software is written has not been certified by NIST in where it is considered compliant with FIPS. Because of this when we try and make a call to the host using our cryptographic algorithm it is denied due to the implementation of the FIPs compliance policy in the GPO or Local Security Policy.
Any GPO that enforces FIPS compliance (or other encryption) will need to have Veeam products excluded, or you can disable this temporarily on the server by changing the requirement for a FIPs compliant algorithm by changing the registry key in:
HKLM\System\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy from "1"
[enabled] to "0" [disabled].
sorry for the bother. Veeam support responded very quick...
Who is online
Users browsing this forum: Google [Bot] and 106 guests