The domain upgrade phase of the automatic upgrade of a FileNet® P8 domain that contains dozens or more object stores might last more than a few seconds. This lag time can cause the automatic upgrade to fail if you use the FileNet P8 System Health page or log on to the FileNet P8 domain from the administration console or other applications during this domain upgrade phase of the automatic upgrade from version 4.5.1 to version 5.2.0 of FileNet P8.
SEC FNRCE0000W - WARN Exception getting named user: xxx
java.lang.NullPointerException
ENG FNRCS0025E - ERROR DomainUpgrade(HugeDomain) Exception encountered with upgrader task, attempt #0 com.filenet.api.exception.EngineRuntimeException: FNRCS0025E: SECURITY_LDAP_PROVIDER_FAILED: The server was not able to access the LDAP provider while attempting the operation getUser for the security principal xxx.
The domain upgrade phase of the automatic upgrade of a FileNet P8 domain that contains dozens or more object stores might last more than a few seconds. The automatic upgrade can fail during this phase if the FileNet P8 System Health page or an application such as the administration console accesses the domain and its properties (or even attempts to log on to the domain) before the domain upgrade transaction is committed.
To prevent the automatic upgrade from failing, refrain from accessing the domain until after the automatic upgrade status page shows that the domain upgrade is in the Completed state.
IBM® FileNet Content Manager version 4.5.1
Scan the p8_server_error.log file for Reattempting domain upgrade messages and examine the cause of the exception that is noted in the message:
If the exception is caused by a failure in accessing the LDAP provider, verify that the LDAP provider is functioning properly.
If the exception is caused by some other system component, verify that the component is functioning properly.
Determine if an application has accessed the FileNet P8 domain during the domain upgrade phase of the automatic upgrade.
For information about the location of the p8_server_error.log file, see the Content Platform Engine table entry in the "Viewing the FileNet P8 log files" topic in the FileNet P8 documentation.
Ensure that no application accesses the FileNet P8 domain until after the automatic upgrade status web page indicates Completed status for the domain upgrade.
To verify that the Content Platform Engine is deployed, utilize the Content Platform Engine Startup Context (Ping Page) web page instead of the FileNet P8 System Health page. You can view the Content Platform Engine Startup Context web page at http://server_name:port/FileNet/Engine.
server_name is the name of the computer or virtual server where the application server is installed.
port is the port number used by the application server.