cancel
Showing results for 
Search instead for 
Did you mean: 

Display problems in View Designer when loading view

Former Member
0 Kudos

Dears,

We just ended successfully the upgrade of our Solution Manager to 71 SPS 4.

We went through Oss note 1639266 and performed the  post-actions, importing also the suggested Java patches.

Doing note 1639266 we discovered in our system the following problem; the urls:

http://saphost.mydomain:50000/sld

http://saphost.mydomain:50000/nwa

returns a completely white page.

We tested the links on the deault J2EE page :

http://saphost.mydomain:50000/

and we found working the followings (at list the first page):

System Information

UDDI client

Webservice

Navigator

while

User Management

Netweaver

Administration

show the white, empty page.

The Webdympro tools show the next page with "Content Administrator" and "Web dympro COnsole" , but then both of them show and empty white

page.

The std_server0.out show the server is running properly , whitout memory error or other, and the sld service is started. The icm log does not show any error in SMICM.

No dumps in ST22 or SM21 errors on the Abap side.

Then we tested the transaction transactions :

SM_WORKCENTER

SOLMAN_SETUP

the logon is not possible here too; we provide the correct User/password and Client but the action to click  on the Logon button

give not results. If we insert directly user/password and client into the bsp object then doing the test of the service in SICF  the first page appears but remains in hangs and sometime appear a popup into the browser internet with errors durin the execution of Script like 'Object missing' or 'object needed'

The kernel in use is 720_REL, pl 201.

We did the test above WHITHOUT setting a Proxy in the  Browser Internet and using IE versions 7.05 and 9.08 and also Firefox 10.0.2

We checked Note 1009930 and we did anything because :

- the table HTTPURLLOC is already empty.

- the note 979039 is obsolete for our system

- we are not using proxy in the Browser connection

- we are not using HTTPS

- the value of parameter icm/host_name_full is already saphost.mydomain

We check note 1088717 and here what we did :

- we activated all the services

- we run report rsicf_service_activation for all the packages and they are all green

- we tested the "WDA test applications for troubleshooting" and the first page of them appears, then we are not able to click on whatever element.

We check note 1122599, even if we are not using HTTPS and if we try to apply via SNOTE it's found to be obsolete

So we do not know how to solve this problem.

It's stopping our Solution Manager configuration and as conseguence our ERP upgrade to EHPx will be delayed...

Any advise ?

regards

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Have you gone through this thread

http://scn.sap.com/message/10256249#10256249

Regards,

Venkata S Pagolu.

Former Member
0 Kudos

Hi, thanks I read all of them.

The hostfile of the sap system already contains the row:

<ip address>     <hostname>     <hostname.domain>

In  SICF transaction I applied pratically note 1088717, even if I have been more large activating pratically all the services availables.

What else could be the matter ?

regards

Former Member
0 Kudos

Addendum on other test I did over the bsp:

I set in SICF for the services wd_sise_main_app and ags_workcenter used by the tx SOLMAN_SETUP and SOLMAN_WORKCENTER the flag 'Do not switch', in place of HTTPS

I assigned the role SAP_SMWORK_ADMINISTRATOR_COMP to the user who run these transactions, and generated all the roles part of this composite role.

Now running the SOLMAN_WORKCENTER the logon screen are working and it's possible to click the logon button, but at the end there is always the same error of the execution of scripts opening the page; errors like 'Object needed'.

Also running the SOLMAN_SETUP tx at the end the page is opened with script errors.

regards

Former Member
0 Kudos

It seems to me these two errors are not related each other:

1) the error that is generating script errors opening the browser page like 'object needed' running the tx SOLMAN_SETUP and SOLMAN_TRANSACTION. It affects the bsp pages

2) the error that is generating the blank page trying to run the /nwa , or the /sld or /useradmin from the J2EE home page, which is affecting the webympro

I observed every time I do refresh in the INternet Browser trying to open one of /nwa , or the /sld or /useradmin into the default trace file of the J2EE the following error occur :

........

#1.#D2F75EB47F03006400000001006100340004BD3141E08734#1333919163123#com.sap.engine.services.security.authentication.logonapplication#sap.com/com.sap.security.core.admin#com.sap.engine.services.security.authentication.logonapplication.executeRequest#J2EE_GUEST#0##A646031181BE11E1AC2500000035F4B2#a646031181be11e1ac2500000035f4b2-0#a646031181be11e1ac2500000035f4b2#SAPEngine_Application_Thread[impl:3]_12##0#0#Fatal##Java###Fatal Logon error

[EXCEPTION]

{0}#1#com.sap.security.core.logonadmin.AccessToLogicException: Error while executing the compilation process: [/usr/sap/TSM/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.security.core.admin/servlet_jsp/logon/work/jsp_umLogonPage1333919161861.java:97: cannot resolve symbol

symbol  : variable BLOCK_EXT_LOGON_APP_EMBEDDING

location: class com.sap.security.core.util.imp.LogonUtils

boolean isFrameEmbeddingDisabled = UMFactory.getProperties().getBoolean(LogonUtils.BLOCK_EXT_LOGON_APP_EMBEDDING, false);

                                                                                  ^

1 error

].

        at com.sap.security.core.logonadmin.ServletAccessToLogic.gotoPage(ServletAccessToLogic.java:146)

        at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:345)

        at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doPost(SAPMLogonServlet.java:69)

        at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doGet(SAPMLogonServlet.java:89)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)

        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

        at java.security.AccessController.doPrivileged(AccessController.java:219)

        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Any advise ?

regards

Former Member
0 Kudos

An addendum; into the default trace for the J2EE we found as latest the error :

#1.#D2F75EB47F0300660000000700B800760004BD02C8DF7899#1333719564515#com.sap.engine.services.security.authentication.logonapplication#sap.c                           om/com.sap.security.core.admin#com.sap.engine.services.security.authentication.logonapplication.executeRequest#J2EE_GUEST#0##EC3BB5AB7FED                           11E1A6B400000035F4B2#ec3bb5ab7fed11e1a6b400000035f4b2-0#ec3bb5ab7fed11e1a6b400000035f4b2#SAPEngine_Application_Thread[impl:3]_10##0#0#Fat                           al##Java###Fatal Logon error

[EXCEPTION]

{0}#1#com.sap.security.core.logonadmin.AccessToLogicException: Error while executing the compilation process: [/usr/sap/ABC/DVEBMGS00/j2                           ee/cluster/server0/apps/sap.com/com.sap.security.core.admin/servlet_jsp/logon/work/jsp_umLogonPage1333719563219.java:97: cannot resolve s                           ymbol

symbol  : variable BLOCK_EXT_LOGON_APP_EMBEDDING

location: class com.sap.security.core.util.imp.LogonUtils

boolean isFrameEmbeddingDisabled = UMFactory.getProperties().getBoolean(LogonUtils.BLOCK_EXT_LOGON_APP_EMBEDDING, false);

But we are not able to find out any Oss note for that.

Regards