Skip to Content
avatar image
Former Member

SMD: there are no access point s for service: P4 registered on the message

After I was fiddling some time ago with SMD I tried to start again today - and I'm stuck with the following error while setting up SMD:

- STEP 5: checking P4 Connection

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

P4 Connection to SMD Server failed

Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while try

ing to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: there

are no access points for service: P4 registered on the message server]

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialC

ontext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: there are no access point

s for service: P4 registered on the message server]

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryI

mpl.java:455)

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.setup.CheckPrerequisiteSetup.checkP4Connection(CheckPrerequisiteSetup.java:510)

at com.sap.smd.setup.CheckPrerequisiteSetup.setup(CheckPrerequisiteSetup.java:173)

at com.sap.smd.setup.CheckPrerequisiteSetup.main(CheckPrerequisiteSetup.java:63)

Caused by: com.sap.engine.interfaces.cross.DestinationException: there are no access points for service: P

4 registered on the message server

The message server on the solution manager host on the specified port (8150) is running:

bash-3.00# netstat -f inet -an | grep 8150

*.8150 . 0 0 49152 0 LISTEN

I can resolve names backward and forward, since the system connects I assume it's no network issue.

What do I need to do in order to "register the P4 port" on the ABAP message server?

Regards,

Markus

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Jan 08, 2008 at 09:00 PM

    Hi Markus,

    I think you should run first the Diagnostics Setup Wizard, in order to desactivate the maintenance mode who desactivates the JNDI context.

    Regards,

    Frederic

    Add comment
    10|10000 characters needed characters exceeded

    • Just got the answer:

      <...>

      This seems to be a bug and was reported to the development; this should

      be fixed for the next version;

      <...>

      Great! "In the next version"...

      It's a BASIC tool for the administration and if it's not working correctly, I can't wait "for the next version".

      Markus

  • avatar image
    Former Member
    Apr 22, 2008 at 07:33 AM

    Hi Markus

    your problem is the SerialVersionID that you are using in the Satellite...

    emote call to setup service on epjava failed : Unexpected exception.(cause=java.io.InvalidClassException com.sap.smd.agent.plugins.remotesetup.SapInstance; local class incompatible: stream classdesc serialVersionUID = -5590655822421529031, local class serialVersionUID = 1033110310377736492)

    Please try this..

    1) Remove any wily agent installed manually in the Satellite..

    2) Download the last Wily_Agent...but use the Wily Agent for SDM deployment.... (ISAGENTSMD72_01-10005468.SCA Introscope Java Agent for SAP, deployment via SMD ) Is the last one..

    3) Restart the JavaStack. Use this one..is really nice http://help.sap.com/saphelp_nw04s/helpdata/en/d5/84a5428295c911e10000000a1550b0/frameset.htm

    4) In the Solution Manager go to --> Diagnostics Setup --> Managed System --> Introscope Agent..

    5) Select your landscape and then Setup Introscope Agent..

    Let me know how was..;-)))

    Wence Lacaze

    http://www.linkedin.com/in/solutionmanager

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 11, 2011 at 02:27 PM

    For anyone who comes accross this old thread with the error "there are no access point s for service: P4 registered on the message server". Make sure you are using the SCS message server port, it will look up the available P4 port/connections and then connect.

    Standard SCS port scheme: 81<SCS instance number> (do not confuse with instance message server)

    Add comment
    10|10000 characters needed characters exceeded

    • Hello,

      I am trying to setup a managed system in Solution Manager 7.1 SPS 12. At step 4 Enter System Parameters, when entering the Java Parameters and then hitting the Test Logon link, I am getting exactly the same error, so I found this thread and tried with 81<SCS instance number>, but it doesn't work... Can you please suggest another solution ? (for the production system it works, for the development it doesn't)