cancel
Showing results for 
Search instead for 
Did you mean: 

Role 'Administrator' does not exist! in phase of SLD

Former Member
0 Kudos

Hi All

We are installing NW EHP1. We got error in Configure SLD step.

here java.exe log

ConfigMainExt state200

TYPE=A<BR>STATE=<BR>INFO_SHORT=java.lang.Exception: java.lang.Exception: Role 'Administrator' does not exist!

at com.sap.ctc.util.UserConfig.addActionToRole(UserConfig.java:238)

at com.sap.ctc.util.UserConfig.performFunction(UserConfig.java:65)

at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:74)

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:1039)

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(Native Method)

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

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

//<BR>CONFIGURATION=

when I log on portal and search Administrator role, no element found. but when I type adm* and search portal can find the role

any idea?

Regards

ABH

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

The role Administrator should exist in your java engine.. If it doesn't, you should create it.

Kind regards,

Mark

Former Member
0 Kudos

Hello, Mark

As I said Administrator role already exist but when I type Administrator in role search area, portal can not find the role (no element found.) when I type adm* and search, portal can find the role. it is weird but it is like that. I also try to create Administrator role, portal do not allow that.

here is also sapinst_dev

ARNING[E] 2011-02-08 10:56:46.521

CJSlibModule::writeError_impl()

CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of log file java.log: 'java.lang.Exception: java.lang.Exception: Role 'Administrator' does not exist!

at com.sap.ctc.util.UserConfig.addActionToRole(UserConfig.java:238)

at com.sap.ctc.util.UserConfig.performFunction(UserConfig.java:65)

at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:74)

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:1039)

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(Native Method)

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

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

// '.

TRACE 2011-02-08 10:56:46.522 [iaxxejsbas.hpp:483]

EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.

ERROR 2011-02-08 10:56:46.569 [sixxcstepexecute.cpp:950]

FCO-00011 The step configSLDMainLocalAddAction with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|6|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|configSLDMainLocalAddAction was executed with status ERROR .

TRACE 2011-02-08 10:56:46.602 [iaxxgenimp.cpp:752]

CGuiEngineImp::showMessageBox

<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > SAP Application Server Java > MS SQL Server > Central System > Central System. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW701/AS-JAVA/MSS/CENTRAL/. </p> </body></html>

TRACE 2011-02-08 10:56:46.603 [iaxxgenimp.cpp:1255]

CGuiEngineImp::acceptAnswerForBlockingRequest

Waiting for an answer from GUI

Regards

ABH

Former Member
0 Kudos

What happens if you execute the SLD configuration via the configuration wizard in the NWA?

Kind regards,

Mark

Former Member
0 Kudos

Hi,

SLD not configured; configure the SLD in Administration first, When I click Administration, I got error.

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!

at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)

at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)

at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)

at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)

at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)

... 29 more

Detailed Exception Chain

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!

at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)

at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)

at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)

at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)

at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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

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:1039)

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(Native Method)

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

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

Regards

ABH

Former Member
0 Kudos

But did you execute the wizard from the NetWeaver Administrator, or did you go directly to /sld ?

Kind regards,

Mark

Former Member
0 Kudos

hello,

First, I run wizard,

NWA_03_Creating a connection to the SLD and Setting required authorizations for SLD (CIM client settings) Finished successfully

then go to /sld

same error

Regards

ABH

Former Member
0 Kudos

That's weird.... Have you tried to retry the installation?

Kind regards,

Mark

Former Member
0 Kudos

hi,

this is the fourth one bu no success. I opened a message to OSS, waiting for answer?

Regards

ABH

Former Member
0 Kudos

hi,

I tried to import Administrator role from other system. I have an error .

Error: Action sap.com_tcsigntprovider~actions.Signature_Administration does not exist

Regards