Error: Symantec Installation Manager failed to initialize. See log for details.

Article:TECH159352  |  Created: 2011-05-03  |  Updated: 2012-12-12  |  Article URL http://www.symantec.com/docs/TECH159352
Article Type
Technical Solution


Issue



When attempting to load SIM, one or both of the following warnings or errors occurs: 

1. A Symantec Installation Manager box pops up with the following content:

 

The product listing located at http://www.solutionsam.com/solutions/pl/symantec.pl.xml.zip could not be accessed.

What would you like to do?  

 ( ) Try again

 ( ) Choose a different Product Listing

 ( ) Use the cached version of the currently selected Product Listing: symantec.pl.xml.zip, Created:....

 

 

 Usually the only thing that goes anywhere is the option to cancel. It results in the following error:

 

 

2. Symantec Installation Manager failed to initialize. See log for details.

 

The a.log file contains the following entries giving indication to what the problem is:

 

 


Error



Failed to read Xml file 'C:\Program Files\Altiris\Symantec Installation Manager\Installs\Altiris\symantec.pl.xml.zip'.

 

 

 

( Exception Details: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

 

   at Symantec.Installation.Xml.Reader.DecryptIrcSource(String encryptedData, String ircName)

 

   at Symantec.Installation.Xml.Reader.GetEncryptedProductListingInstallReadinessChecks(ProductListing& pl)

 

   at Symantec.Installation.Xml.Reader.Read()......

  

  

 

Another similar error was also encountered:

 

 

Failed to read Xml file 'C:\Program Files\Altiris\Symantec Installation Manager\Installs\Altiris\SSRMS.pl.xml'.

 

 

 

( Exception Details: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

 

   at Symantec.Installation.Xml.Reader.DecryptIrcSource(String encryptedData, String ircName)

 

   at Symantec.Installation.Xml.Reader.GetEncryptedProductListingInstallReadinessChecks(ProductListing& pl)

 

   at Symantec.Installation.Xml.Reader.Read()......

 


Environment



Symantec Management Platform 7.1


Cause



The FIPS security method is enabled on the server.  SMP 7.1 is not currently FIPS compliant.


Solution



  1. Open the Local Security Policy editor (found under "Start > Administrative Tools")
  2. Under Security Settings browse down to "Local Policies > Security Options"
  3. In the right pane look for "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing"
  4. Double-click on the setting and change to Disabled.
  5. Open a command prompt and run the command:   gpupdate /force

Sometimes, after making the change the registry value governing the setting does not get changed, although the policy editor reflects that it is disabled. If the error continues, check the following registry values:

  • HKLM/SYSTEM/CurrentControlSet/Control/Lsa/FipsAlgorithmPolicy "Enabled" DWORD 
  • HKLM/SYSTEM/CurrentControlSet/Control/Lsa "FipsAlgorithmPolicy" DWORD

If either of these are set to 1, change the setting to 0.
Note: The second value does not exist on all systems. If it does not exist do NOT add it.

Also, in some random situations, you may want to check the following regkeys as well:

HKLM\SYSTEM\ControlSet001\Control\Lsa\FIPSAlgorithmPolicy   --change it from 1 to 0
HKLM\SYSTEM\ControlSet001\Control\Lsa\FipsAlgorithmPolicy\Enabled   --change it from 1 to 0

HKLM\SYSTEM\ControlSet002\Control\Lsa\FIPSAlgorithmPolicy   --change it from 1 to 0
HKLM\SYSTEM\ControlSet002\Control\Lsa\FipsAlgorithmPolicy\Enabled   --change it from 1 to 0

SIM should be able to load at this point. If the problem returns then there is probably an AD GPO that is being enforced.

 




Article URL http://www.symantec.com/docs/TECH159352


Terms of use for this information are found in Legal Notices