Portal screen grey , error in default trace

[nicola_blasi]

Hello,

i have a problem in a java instance 7.00 SP18 in Linux environemnt.

When i start it all processes are running and i can log in NWA , useradmin etc.

If i try to go in irj/portal, i can put login and password (j2ee_admin) but the output is a grey screen .

By default trace i have this error:

#1.#0050569D0090003D00000019000039970004C58144EEDD7A#1343058904800#System.err##System.err#J2EE_GUEST#0##n/a##c4d5a6f0d4de11e1836f0050569d0090#Thread[PRT-Async 13,5,PRT-Async]##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:991)#

#1.#0050569D0090003D0000001A000039970004C58144EEDDA0#1343058904800#System.err##System.err#J2EE_GUEST#0##n/a##c4d5a6f0d4de11e1836f0050569d0090#Thread[PRT-Async 13,5,PRT-Async]##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)#

#1.#0050569D0090003D0000001B000039970004C58144EEDDCF#1343058904800#System.err##System.err#J2EE_GUEST#0##n/a##c4d5a6f0d4de11e1836f0050569d0090#Thread[PRT-Async 13,5,PRT-Async]##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#

#1.#0050569D0090003D0000001C000039970004C58144EEDDF4#1343058904800#System.err##System.err#J2EE_GUEST#0##n/a##c4d5a6f0d4de11e1836f0050569d0090#Thread[PRT-Async 13,5,PRT-Async]##0#0#Error##Plain###     ... 6 more#

I've noted also from the directory

/usr/sap/SID/JCXX/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd

some packages in error :

com.sap.portal.appintegrator.sap.bwc.par.err

com.sap.portal.xmltransformationiview.par.err

com.sap.portal.pcd.admintools.lockadmin.par.err

com.sap.portal.httpconnectivity.iviewcatcher.designtime.par.err

com.sap.portal.wsrp.coreconsumer.par.err

com.sap.workflow.apps.par.err

com.sap.portal.systemlandscapeoverview.par.err

Tring to redeploy it without success.

The kind of error in their corrispective logs is for example:

Upload handler failed com.sapportals.portal.application.applicationrepository.ResourceBundleExtractor@6a296a29^M

com.sapportals.portal.prt.deployment.hook.DeploymentHookException: Unable to store bundle com.sap.workflow.apps - wf_localization

        at com.sapportals.portal.application.applicationrepository.ResourceBundleExtractor.handleEntry(ResourceBundleExtractor.java:144).........................

..........................etc

Any Idea?

Thanks

Nickk

[nicola_blasi · Accepted solution]

Hy

I solved the problem in this manner:

First of all

login to the NWA using the following:

http://<HOST>:<PORT>/nwa

After successful login run the following:

http://host:port/irj/servlet/prt/portal/prtroot/com.sap.portal.pcd.admintools.pcd_inspector.default

If it does work navigate to the relevant location where we store the

Text Containers;

com.sap.portal.system/resource_bundles/

try to delete the "com.sap.ip.bi.portalnavigation" context.

Then navigate into com.sap.workflow.apps and delete "wf_localization".

Then in #/deployment/pcd folder on server0, you should remove all the

.err & .bak extensions from the PAR files to force redeployment of them.

you should also do the same for EPA/APT files under

#/deployment/pcdContent folder  (but not for the no overwrite folder)

Restart the java and the pcd errors decreased to a less number.

After this through pcd inspector we deleted all content in com.sap.portal.system/resource_bundles/

To do that you need a super_admin permission in pcd inspector :

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/caf5eab6-0901-0010-7883-daf18dbda...  (page 4)

Now in #/deployment/pcd folder on server0 change files .err in .par; delete *.log  and restarting all java system , all pcd were deployed and finally i could enter in portal homepage without problems.

i hope is clear...

Thanks

Nicola

[nicola_blasi]

Hy

thanks but i can't understand the problem yet.

David: I changed the *.err in *.par and restart the instance several times but the error is always the same.

Shrikant: I can't apply the tool, i have a 7.00 SP18 ..minimum requirement si up to 23 ...

My idea is somw par corrupted. First that goes in error is

com.sap.portal.appintegrator.sap.bwc.par.err

and then the other....

Thanks

Nick

[hemanth2]

Hi Nick,

Hope you are doing good.

The most likely reason for this issue is inconsistency in the PCD. first apply sap notes 1086644 and  1003198.

If the issue persists, try a force bootstrap:

1)

Stop the server.

Under cluster directory (/usr/sap/<SID>/JC<nr>/cluster) rename dispatcher folder to dispatcher.old.

Rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename the bootstrap folder as this is needed for the sync proces

2)

Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.

3)

Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.

4)

Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.

This should solve the issue. Else, there is no other go other than depoyment of the EP related patches:

EPBC*.SCA

EPBC2*.SCA

EPPSERV*.SCA

Thank you and have a nice day :).

_____________
Kind Regards,
Hemanth

[Former Member]

Hi Nicola,

Can you renamed all .err to .par and restarted the J2EE and check .

check the deployment by navigating to :

\usr\sap\<sid>\<instance-id>\j2ee\cluster\server0\apps\sap.
com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd and \pcdContent

If you find any files with .err extension there, kindly remove the .err extension and add .bak extension.

Then restart the J2EE engine.

Also make sure that all the deployed files are having the correct SP version by checking it through System Administration -> Support -> Portal Runtime -> Deployment Overview

Regards

shrikant

[nicola_blasi]

Hy Hemanth

In the meanwhile i've tried to do the 4 point you described, because the link to download the pcdcheck inside the note 1086644 doesn't work.

I have the same problem , anyway i don't see anymore in dir pcd the component...i have no files inside

/usr/sap/SID/JCXX/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd

i think something not clear about it...what do you think?

Thanks

Nick

[hemanth2]

Hi Nicola,

Please try the force bootstrap as this will fix the folders not present issue..

Thank you and have a nice day :).

_____________
Kind Regards,
Hemanth

[nicola_blasi]

Hy,

i did it but i have the same problem.

Before it, i had /usr/sap/XJB/JC70/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd , all par files and also *.par.err .

After forced in bootstrap i don't have no more file inside.

Anyway it doesn't work .

From Default trace i have:

#1.5^H#0050569D009000290000000000004E160004C593C0A8A464#1343138289983#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#J2EE_ADMIN#113##xjbja.sapmi_XJB_704429350#J2EE_ADMIN#f42a6cd0d59511e1a9660050569d0090#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java###Exception ID:02:58_24/07/12_0010_704429350

[EXCEPTION]

{0}#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource^M

Component : pcd:portal_content/every_user/general/defaultDesktop/frameworkPages/frameworkpage^M

Component class : com.sapportals.portal.prt.component.CachablePortalComponent^M

User : J2EE_ADMIN

        at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)

        at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)

        at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)

...and so on....

Thanks

Nick

[nicola_blasi]

Hy Shrikant,

I did it, and ok, during startup there is no error , but because i changed the final extension so it bypass it. Anyway i think that error in that par continues, Infact i have always the same errors....grey page and default trace like first message...

Thanks

Nick

[nicola_blasi]

Hy Hemant,

after doing the force mode following 710663 , i have pcd folder empty.

I find the pcd file into temp directory.

I'd like to redeploy package

EPBC*.SCA

EPBC2*.SCA

EPPSERV*.SCA

Is it possible deploy the same package through JSPM? How?

Thanks

Nick

[hemanth2]

Just redeploy after activating the JSPM force mode as mentioned in: SAP Note Number: 1123333.

[Former Member]

Hi Nicola,

Apart from  the SAP Note  1130469 , also check the SAP Notes  1086644 & 1003198.

This will help you in resolving the issue.

Regards

shrikant

[david_liu1]

Hello,

Check SAP note:

1130469 - Deployment failure of PAR and EPA (EPT) files in the portal

Regards,

David