Skip to Content
avatar image
Former Member

Connection to P4 port of managed system failed

Hi All,

I get the following error message during managed system configuration in SMD. Can anybody help with this?

Regards,

Masoud

Failed to connect, P4 port=50104 User=J2EE_Admin SID=PSE Instance Number=01

Connection error to SAP System sid [PSE/01], more details about the error in agent 'dbciPSE' log file (SMDAgentApplication.X.log).; nested exception is:

com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.(cause=com.sap.engine.services.security.exceptions.BaseLoginException Exception in creating new RemoteLoginContext instance.)

Exceptions

com.sap.smdagent.plugins.connectors.p4.exceptions.P4ConnectionException: Connection error to SAP System sid [PSE/01], more details about the error in agent 'dbciPSE' log file (SMDAgentApplication.X.log).; nested exception is:

com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.

at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.prepareP4Exception(P4ConnectionService.java:116)

at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:72)

at com.sap.smd.agent.plugins.remotesetup.SetupManager.newP4ctx(SetupManager.java:120)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService._setup(RemoteSetupService.java:125)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService.setup(RemoteSetupService.java:86)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupServicep4_Skel.dispatch(RemoteSetupServicep4_Skel.java:112)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)

at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)

at java.lang.Thread.run(Thread.java:534)

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.

at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)

at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)

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.getP4Connection(P4ConnectionService.java:57)

... 8 more

Caused by: java.net.SocketException: Connection reset

at java.net.SocketInputStream.read(SocketInputStream.java:173)

at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:395)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jun 15, 2009 at 05:07 PM

    Hi,

    Please post SMDAgentApplication.X.log here.

    Feel free to revert back.

    -=-Ragu

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi;

      I had same problem with wily introscope. After uninstalling the SMD agent, re-installing it and setting up wily the issue has been disappeared

      Regards

      Edited by: Christoph Ernst on Jan 29, 2010 1:06 PM

  • avatar image
    Former Member
    Nov 02, 2009 at 12:01 PM

    Hi,

    I had the same problem on our system. We have SMD on Solman and the managed system is Portals. Our systems are on AIX

    1) The connection to P4 error was resolved after shutting down the smdagent, kill all the related processes and then do a cleanipc ## remove. Then restart the smdagent and then retry the agent setup. For me it went green. I tried many things before I did this.

    2) There were other errors also when I was running th setup wizard. On the smd setup > diagnostics setup > upgrade agents. This resolves most of the errors.

    Manmath

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 02, 2009 at 12:01 PM

    Hi,

    I had the same problem on our system. We have SMD on Solman and the managed system is Portals. Our systems are on AIX

    1) The connection to P4 error was resolved after shutting down the smdagent, kill all the related processes and then do a cleanipc ## remove. Then restart the smdagent and then retry the agent setup. For me it went green. I tried many things before I did this.

    2) There were other errors also when I was running th setup wizard. On the smd setup > diagnostics setup > upgrade agents. This resolves most of the errors.

    Manmath

    Add comment
    10|10000 characters needed characters exceeded