cancel
Showing results for 
Search instead for 
Did you mean: 

Error in UM Configuration

Former Member
0 Kudos

I get following message when I click on UM Configuration :

"Could not access the System Landscape Directory. Cannot select an SAP Reference System."

I created a system in landscape and deleted it. After this I get this message.

I would appreciate your input to troubleshoot the error.

Thanks,

Digesh

Accepted Solutions (0)

Answers (2)

Answers (2)

H_Ettelbrueck
Employee
Employee
0 Kudos

Hi Digesh,

please open Visual Admin > Server > Services > Log Configuration and set the severity level for location "com.sap.security.portal.service.usermapping" to "Info". Save the changes, open UM Configuration in the Portal again and check the defaultTrace file for messages on the named location.

My first guess would be that, when you deleted the system in the system landscape, the assigned system alias was not deleted for some reason, so you'd have a dangling alias without assigned system object.

Please tell me the messages you find in defaultTrace.

Best regards

Heiko

Former Member
0 Kudos

Here is contents of default trace file :

---

#1.5#0002B3BF354D004C0000001000000A480003FAAF1A28F98F#1120054895258#com.sap.security.core.server.userstore.UserContextUME#sap.com/irj#com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(String)#Guest#0####1915b3b0e8a911d9cbf90002b3bf354d#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Security/UserStoreUME#Plain####

#1.5#0002B3BF354D004C0000001100000A480003FAAF1A28FAF2#1120054895258#com.sap.security.core.server.userstore.UserContextUME#sap.com/irj#com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(String)#Guest#0####1915b3b0e8a911d9cbf90002b3bf354d#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###com.sap.security.core.server.userstore.UserstoreException: Could not get user ji78sbd#

#1.5#0002B3BF354D004C0000001200000A480003FAAF1A28FBF8#1120054895258#com.sap.security.core.server.userstore.UserContextUME#sap.com/irj#com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(String)#Guest#0####1915b3b0e8a911d9cbf90002b3bf354d#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###com.sap.security.core.server.userstore.UserstoreException: Could not get user ji78sbd

at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:193)

at com.sap.engine.services.security.userstore.context.UserContext.getUserInfo(UserContext.java:87)

at com.sap.engine.services.security.server.jaas.LogonInfoLogger.logInfo(LogonInfoLogger.java:267)

at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.writeLogonStatistics(LoginModuleHelperImpl.java:300)

at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:219)

at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)

at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)

at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)

at java.security.AccessController.doPrivileged(Native Method)

at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)

at javax.security.auth.login.LoginContext.login(LoginContext.java:534)

at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:230)

at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.login(AuthenticationService.java:344)

at com.sapportals.portal.prt.connection.UMHandler.handleUM(UMHandler.java:126)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:178)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)

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

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)

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

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:290)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:346)

at com.sap.portal.navigation.Gateway.service(Gateway.java:68)

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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

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

Caused by: com.sap.security.api.NoSuchUserAccountException: USER_AUTH_FAILED: User account for logonid "ji78sbd" not found!

at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:334)

at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56)

at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:339)

at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:277)

at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:371)

at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:366)

at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:189)

Please advise.

Thanks,

Digesh

H_Ettelbrueck
Employee
Employee
0 Kudos

Hi Digesh,

I'm sorry, I forgot to mention that only lines containing the location name "com.sap.security.portal.service.usermapping" may be relevant for this issue. Please check for matching methods again. There will probably messages like "All systems retrieved from System Landscape: ...", and hopefully also some message telling more about the reason for the error message in the iView.

Best regards

Heiko

Former Member
0 Kudos

Hi Heiko,

Here is description of an error :

UserMappingService: Could not find system by unique ID (PCD location) 'pcd:portal_content/com.sap.portal.migrated/com.companyname.us.SID'.

Context: UME principal to be mapped = "(unknown)", principal's type: (unknown), mapped user in target system = "(null)" system alias = "(unknown)"

Exception: javax.naming.NameNotFoundException: Child not found: com.companyname.us.SID at portal_content/com.sap.portal.migrated [Root exception is javax.naming.NameNotFoundException: Child not found: com.companyname.us.SID at portal_content/com.sap.portal.migrated]#

I appreciate your prompt reply.

H_Ettelbrueck
Employee
Employee
0 Kudos

Hi Digesh,

is the system mentioned in the message (portal_content/com.sap.portal.migrated/com.companyname.us.SID) the system that you deleted?

I guess, directly after that message, there should be another message like "Could not find system by system ID "(PCD URL)", therefore could not retrieve system's attributes.". At the end of the message, you should also find the associated system alias.

Please logon to the portal and navigate to the following portal component: http://host:port/irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.system.console.PCDBrowser

Navigate to com.sap.portal.system/aliases and click the link with the corrupted system alias. The alias object's attribute "com.sap.portal.private.system.Target" should point to the PCD URL of the deleted system.

If the reason for the problem is really the system alias of the deleted system being left in the PCD, please open an OSS message for this issue on component EP-PIN-PSL so that the support colleagues can help you clean up the system alias. This is necessary because, as far as I know, there's no official tool for SAP customers that allows the necessary operations on PCD content. Please tell the support colleagues about the system alias that has not been deleted when the system itself was deleted and perhaps reference this thread.

Best regards

Heiko

Former Member
0 Kudos

Hi Heiko,

I see that the target is pointed to the PCD URL of the system. I restarted EP and again I checked the default trace file and I found following :

UserMappingService successfully initialized.

Context: UME principal to be mapped = "(unknown)", principal's type: (unknown), mapped user in target system = "(null)" system alias = "(unknown)"

Exception: (none)#

#1.5#0002B3BF354D00490000000800000BC40003FAB22F6EEE2B#1120068137063#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0####edd5ad80e8c711d986e90002b3bf354d#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Java###Exception ID:01:02_29/06/05_0001_2093950

[EXCEPTION]

#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is denied: com.sap.portal.runtime.system.console.PCDBrowser - user: Guest

See if you get any solution from this.

H_Ettelbrueck
Employee
Employee
0 Kudos

Hi Digesh,

"UserMappingService successfully initialized" is the normal message when that service has started up - unfortunately, this doesn't help in this issue, it's just what I expect when you restart the portal.

The main question is whether there's really the system alias object left in the PCD after the system object itself has been deleted. That's what I guess causes the error message in UM Configuration, and that's what my previous post tries to (make you) find out.

Please either follow the description about how to check that, or directly ask SAP support via an official OSS message to solve the problem. I guess this is nothing you can handle on your own with official customer tools.

Best regards

Heiko

jochen_spieth
Participant
0 Kudos

Hi Digesh,

can you still access the security settings tab in the uM Configuration? There is field for the R/3 Reference System. Maybe there is still some entry.

You can also try and have a look at the sapum.properties.bak file (if you are on SP 2).

Is there an entry called ume.r3.mastersystem?

If yes, delete it, rename the file and restart the portal.

The same can be done (in case it works) in the direct editing tab.

Best regards,

Jochen