Skip to Content
0
Former Member
Oct 25, 2006 at 02:37 PM

Portal crashes and intermittant problems..urgent help needed.

61 Views

Portal Runtime Error

An exception occurred while processing a request for :

iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.themes/com.sap.portal.theme_editor/com.sap.portal.styleeditor

Component Name : null

Page could not create the iView.

I briefly describe the system setup.

sptltrex = central instance

sptl1 = app1

sptl2 = app2

sptldb = database instance.

sptltrex built with virtual name ourworld-0

sptldb built with virtual name ourworld-db

System setup with Oracle dataguard feature, so ourworld-0 and ourworld-db can fail over to disaster recovery systems sptldr and sptldevdb at another site. Although we installed using the SAPINST_USE_HOSTNAME for SCS/central instance the visual administrator and message server still pick

up sptltrex. We though setting the SAPLOCALHOSTFULL to ourworld-0.sap.serco.com had fixed this issue, but this generated many iview errors that

could not be found. When the SAPLOCALHOSTFULL was backed out everything

began to display again. Although there is still intermittant errors of screens not acting as required.

message server output

http://sptltrex:8100/msgserver/text/logon

version 1.0

J2EE1666800

J2EE sptl2.sap.serco.com 50000 LB=2

J2EES sptl2.sap.serco.com 50001 LB=2

P4 sptl2.sap.serco.com 50004 LB=2

P4S sptl2.sap.serco.com 50006 LB=2

J2EE13975600

J2EE sptltrex.sap.serco.com 50100 LB=2

J2EES sptltrex.sap.serco.com 50101 LB=2

P4 sptltrex.sap.serco.com 50104 LB=2

P4S sptltrex.sap.serco.com 50106 LB=2

P4HTTP sptltrex.sap.serco.com 50105 LB=2

JC_ourworld-0_PP1_01

SDM ourworld-0 50118

We have had numerous OSS messages for various continuing problems on the system. Today we have an complete up-to-date as possible patched system. SPS 9 with all the latest sub patches also. We have installed AIX TL 05 with service pack 2 so oslevel -s shows 5300-05-02 + a related db APAR, the IBM java JDK is SRS06. Full earlywatch go-live check parameters and options have been completed.

But still we have problems.

can anybody help......it's urgent....

thanks

saurabh