CONFIG-WP-PTF-CF fails during upgrade from 8.0.0.0 to 8.0.0.1

Technote (troubleshooting)


Problem

ConfigEngine task CONFIG-WP-PTF-CF fails on upgrade to Portal 8 FP1 with error ADMN0022E.

Symptom

The following error appears in the ConfigTrace.log:

IBM\WebSphere\PortalServer\installer\wp.update\config\includes\cumulative_fix.xml:47: The following error occurred while executing this line:
D:\IBM\WebSphere\PortalServer\base\wp.base\config\includes\wp.base.fp_cfg.xml:73:
com.ibm.websphere.management.exception.ConfigServiceException:
javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.


Cause

Mixed use of uid and CN in wkplc.properties and security.xml files.

Diagnosing the problem

The following error appears in the ConfigTrace.log:

IBM\WebSphere\PortalServer\installer\wp.update\config\includes\cumulative_fix.xml:47: The following error occurred while executing this line:
D:\IBM\WebSphere\PortalServer\base\wp.base\config\includes\wp.base.fp_cf
g.xml:73:
com.ibm.websphere.management.exception.ConfigServiceException:
javax.management.JMRuntimeException: ADMN0022E: Access is denied for
the resolve operation on ConfigService MBean because of insufficient or
empty credentials.

Resolving the problem

In security.xml that the primaryAdminId is set using CN - e.g. CN=wpstest,CN=Users,DC=net,DC=ecom,DC=com

However, in the wkplc.properties, WasUserid set using uid - e.g. uid=wpstest,CN=Users,DC=net,DC=ecom,DC=com

The upgrade fails due to the mixed uid and CN usage.

The solution is to change WasUserid in wkplc.properties to use CN - e.g. CN=wpstest,CN=Users,DC=net,DC=ecom,DC=com

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal

Software version:

8.0

Operating system(s):

AIX, Linux, Windows

Reference #:

1636581

Modified date:

2013-05-10

Translate my page

Machine Translation

Content navigation