2 Replies Latest reply on Feb 3, 2010 4:02 AM by JoeBidgood

    ePO 4 P3: Failed to load server keys

    Attila Polinger

      Hi,

       

      we'd like to test ePO 4.5 upgrade from ePO 4.0 Patch 6 by executing the upgrade in our test environment. First we wanted to bring the test ePO environment on par with our live environment (since the test env is at Patch 3 and some extensions need upgrading also). This was we we got our first problem (doing just a console login before anything).

       

      The console indicated that some dependency errors have occurred and that the master repository key is corrupt.

      The server log contains the following:

      20100115093535 I #7872 NAISIGN Loading fips module, current folder: C:\PROGRA~1\McAfee\EPOLIC~1
      20100115093535 I #7872 NAISIGN Checking for fips module in C:\PROGRA~1\McAfee\EPOLIC~1
      20100115093535 I #7872 NAISIGN Found fips module: C:\PROGRA~1\McAfee\EPOLIC~1\cryptocme2.dll
      20100115093535 I #7872 NAISIGN FIPS library initialized successfully
      20100115093535 I #7872 usermgr Attempting to add user: MOLT\Admin
      20100115093535 I #7872 usermgr Current user: SYSTEM
      20100115093535 E #7872 mod_epo Failed to load server keys
      20100115093535 E #7872 mod_epo Initialize epo handler failed

      (Some other errors beside a similar error like above are indicated in orion.log, too.)

       

      The Extensions list has some entries/extension names in red. These mostly due to "Dependency RepositoryMgmt had initialization errors". The Repository Management extension indicates that "The Master Repository key corrupt".

       

      Console login works, though.

       

      Where should we start fixing and with what?

       

      Any useful advice is highly appreciated.

       

      Thank you.

       

      Attila