on 01-09-2012 2:03 PM
Hi Friends
We have configured the SMD agents and ISA agents for monitoring of
managed systems.We have also configured the Wily Introscope in Solution
manager Prod system (P50).Everything went properly, but recently,when wemonitored, we found that IS Agent status is Unknown.
I have restarted the DAA instance also. Wily Introscope is running.
Totally, we have 4 Java Systems, out of which we are facing problem with2 systems.
Error: Failed to connect via P4 channel -
com.sap.smdagent.vmmanager.VMManagerP4Exception:
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [P40/00]: check the connection
credentials.More details about the error in agent 'piprodsvc' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Jan 9, 2012 11:46:20 AM [Thread[Thread-37,5,main]] Error J2EE Node Settings Rerieval: P40 - 4635050 - It sounds like the remote system is stopped!
Jan 9, 2012 11:46:20 AM [Thread[Thread-37,5,main]] Error J2EE Node Settings Rerieval: P40 - 4635050 - Failed to connect via P4 channel
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid [P40/00]: check the connection credentials.More details about the error in agent 'piprodsvc' log file (SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
at com.sap.smdagent.vmmanager.VMManagerBootstrap._getInitialContext(VMManagerBootstrap.java:220)
at com.sap.smdagent.vmmanager.VMManagerBootstrap.getVMManagerFactory(VMManagerBootstrap.java:167)
at com.sap.smdagent.vmmanager.VMManagerBootstrap.getVMManager(VMManagerBootstrap.java:137)
at com.sap.smd.wily.WilyHandlerService.getVMManager(WilyHandlerService.java:1974)
at com.sap.smd.wily.WilyHandlerService.retrieveISAgentSettings(WilyHandlerService.java:1328)
at com.sap.smd.wily.WilyHandlerServicep4_Skel.dispatch(WilyHandlerServicep4_Skel.java:114)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:679)
Caused by: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid [P40/00]: check the connection credentials.More details about the error in agent 'piprodsvc' log file (SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.prepareP4AcessDeniedException(P4ConnectionService.java:153)
at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.establishP4Connection(P4ConnectionService.java:91)
at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:57)
at com.sap.smdagent.vmmanager.VMManagerBootstrap._getInitialContext(VMManagerBootstrap.java:212)
... 9 more
Appreciate your help[ on this
Regards,
venkat
Hi Guilherme,
SMDAgentApplication log:
Feb 20, 2012 2:00:08 PM [Thread[Thread-54,5,main]] Error P4 connection error to SAP system [SED/00]
[EXCEPTION]
com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleUserProblem(InitialContextFactoryImpl.java:512)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:366)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.establishP4Connection(P4ConnectionService.java:80)
at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:65)
at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:43)
at com.sap.smdagent.vmmanager.VMManagerBootstrap._getInitialContext(VMManagerBootstrap.java:214)
at com.sap.smdagent.vmmanager.VMManagerBootstrap.getVMManagerFactory(VMManagerBootstrap.java:169)
at com.sap.smdagent.vmmanager.VMManagerBootstrap.getVMManager(VMManagerBootstrap.java:137)
at com.sap.smd.wily.WilyHandlerService.getVMManager(WilyHandlerService.java:3021)
at com.sap.smd.wily.WilyHandlerService._configureISAgent(WilyHandlerService.java:1311)
at com.sap.smd.wily.WilyHandlerService.configureISAgent(WilyHandlerService.java:885)
at com.sap.smd.wily.WilyHandlerServicep4_Skel.dispatch(WilyHandlerServicep4_Skel.java:135)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:579)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:178)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
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)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:175)
... 13 more
I've already used smdsetup.bat script to force connection with SMD_ADMIN but that didn't solve the problem.
Thanks in advance
Rafael Veloso
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm having the same problem, after upgrading SM from 7.0EHP1 to 7.1
I'm trying to install/upgrade bytecodeagent, and that's when the same error occurs.
According to logs the connection that is failing is the one to the managed system, and not to SMD.
Anyone went thru this problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Guilherme,
I am facing the same issue. here is the error log from Byte code adapter installation setup from Solman 7.1
Operation Failed - XYZ - 31030320 - java.rmi.RemoteException: Problem
getting VMManager; nested exception is:
com.sap.smdagent.vmmanager.VMManagerP4Exception:
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid [XYZ/01]: check the connection
credentials.More details about the error in agent 'grtpmd12' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Please assist.
Thanks,
Rohan
Hello,
You must use user SMD_ADMIN to connect the agent to the Solution Manager.
The SMD_ADMIN is created in the Diagnostics Configuration in solman_setup -> Basic Configuration -> Automatic Configuration;
Or it's acessible as well in the URL http://<solman>:<port>/smd -> diagnostics system -> Setup Wizard.
Make sure is executed.
Afterwards issue the command in the agent's script directory
smdsetup managingconf hostname:"myhost.domain.corp" port:"50004"
user:"SMD_ADMIN" pwd:"init1234"
Adjust the paramters accordingly.
More information is available at the Diagnostics Agent Troubleshooting guide at
http://service.sap.com/diagnostics -> media library
And in our SDN
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents
Best regards,
Guilherme Balbinot
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
As per the error message:
"com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid P40/00: check the connection credentials.More details about the error in agent 'piprodsvc' log file (SMDAgentApplication.X.log).; "
It seems that this is a problem related to user/password. Which user have you used to execute the managed system config? could you check the file SMDAgentApplication.X.log in the managed system??
Cheers,
Diego.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.