It means you have FIPS mode turned on, but at least one of your modules (DLLs etc) are not FIPS approved.
You can either turn FIPS mode off, or make sure you are indeed only deploying FIPS approved versions of all the code.
How do I know which module, If any, are not FIPS approved. In regards to turning FIPS off, I thought you could only activate FIPS when you install the product. Do I have to reinstall it without checking FIPS mode? Also, how can I make sure that I'm deploying FIPS approved versions of all the code?
No, FIPS covers the entire solution, and both the management and client are FIPS certified.
To check what you're deploying, just look at the modules list - it will tell you what version you are using.
you may have some tokens or something selected which is not FIPS certified - that's why you'd be getting the error.
How can I check the modules if I can't log onto EEM? Is there an INI file that I can check. Also, when I did the migration, nothing new was added (as far as tokens). We are using the same tokens in 5.2.12 that we used in 5.2.4. When I installed 5.2.12 for EEM and PC, I used the same options.
If you can no longer login to EEM, then you have a few options
1) Start a clean install in another path, and point it to your old DB
2) Turn off FIPS mode temporarily
3) Start the upgrade again
When you upgraded, did you follow all the steps in the Migration guide - for example did you remember to stop all the services etc? That's one way I can imagine this would happen - if you left something running while upgrading etc.
I didn't stop the EE service, because this is a stand alone EE server. No clients are connected, ever. How do you turn FIPS off?
If you had anything running, you needed to have stopped it.
The FIPS instructions are at the back of the Admin guide - there are registry settings you need to change.
Are you talking about the section of EEPC Admin guide Creating the FIPS Enabled Script? Isn't that script to turn On FIPS from it being Off? As another option, can I build another machine, install 5.2.12 and add the old database?
The solution is described here:
Disable FIPS mode on the Management Console using the registry edit described in the above KB article.