IBM Support

Creating virtual portal using the Virtual Portal Manager results in EJPAH2012E

Technote (troubleshooting)


Attempting to create a virtual portal from the Virtual Portal Manager portlet results in:

EJPAH2012E: Can not find xmlaccess script


The virtual portal is created. However, when users access this virtual portal, the page just displays:

Loading ...
This page does not support content.

If the Portal administrator attempts to re-initialize the virtual portal from the Virtual Portal Manager portlet, the same exception (EJPAH2012E) is thrown.


Initially, when WebSphere Portal was installed, the user "wasadmin" was used as the administrative ID for both WebSphere Application Server (WAS) and Portal. Sometime afterward, the ConfigEngine task "wp-change-portal-admin-user" was run to change the Portal administrative user from "wasadmin" to "portaladmin". The "portaladmin" is the administrative user for Portal but has no proper privileges on the WAS, thus cannot access the file used to initialize the virtual portal.

(In a Portal 7.0 stand-alone installation, the is located in the directory:

.../<profile_name>/config/cells/<cell_name>/assets/ )

Diagnosing the problem

Collect data as noted in the related URLs. With tracing enabled, trace.log records the following:

[3/3/11 12:12:02:281 EST] 00000033 AssetMgrImpl  1   Created exportAsset

[3/3/11 12:12:02:281 EST] 00000033 AssetMgrImpl  1   Set assetID parameter to


[3/3/11 12:12:02:531 EST] 00000033 AssetMgrImpl  E   Cannot process command parameters Cannot process command parameters




Caused by: CWWMH0276E: Authorization failure. Insufficient authority to access asset "". This operation requires "monitor" role on the cell or on the asset.



Resolving the problem

This issue was reported under APAR PM39581, which was released as part of Cumulative Fix CF006 for Portal, but unfortunately the WAR is not redeployed in CF06, CF07, or CF08. The WAR is properly redeployed in CF09.

Therefore, in CF06, CF07, or CF08 to take advantage of this fix, customers should manually redeploy the WAR by copying PortalServer/ap/wp.ap.virtualportal/installableApps/ManageVirtualPortals.war to PortalServer/installableApps/ManageVirtualPortals.war and then running the deploy-portlet-upgrade-wp.ap.virtualportal

If you cannot upgrade the Portal, the following workaround will also resolve the issue.

Log in to the IBM® WebSphere® Integrated Solutions Console (ISC) admin console as the WAS administrative user and give the "portaladmin" "Monitor" role, which is the minimum requirement.

* Steps to add "Monitor" role for a user:

Go to: Users and Groups >> Administrative user roles >> Add

Highlight the "Monitor" role in the Role(s) box

Search for the user and select the user from the search results

Click the "Add" button

Click "OK". Then save to the master configuration.

Restart Portal

After these steps, user should be able to create virtual portals using the Virtual Portal Manager portlet and to initialize the virtual portal created previously that failed to initialize.

Related information

Administering virtual portals: wp7
Collecting Data and Traces: Virtual Portals

Document information

More support for: WebSphere Portal
Virtual portals

Software version: 7.0

Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS

Reference #: 1469910

Modified date: 22 September 2011

Translate this page: