cancel
Showing results for 
Search instead for 
Did you mean: 

SMD Agent can't connect to Solution Manager

former_member192350
Active Participant
0 Kudos

I recently installed the SMD Agent 7.11 on a server, along with the host agent. Our solution manager is instance 01 on another host, running 7.01 EHP1 SP19.

After installation, I stopped the SMD agent (stopsap SMDA97) and ran:

/usr/sap/SMD/SMDA97/scripts/smdsetup.sh managingconf hostname:"sapms//[solman_hostname.domain.com]" port:50104 user:SMD_ADMIN pwd:"[password]"

I then restarted the SMD agent (startsap SMDA97), but see the following in the SMDAgent/log/SMDSystem.0.log file:

Aug 31, 2009 10:30:07 AM [Thread[Connector,5,main]] Info [ms://host.domain.com:50104/P4] Checking server availability...

Aug 31, 2009 10:30:07 AM [Thread[Connector,5,main]] Error Failed to connect to SMD server - user: SMD_ADMIN

Aug 31, 2009 10:30:07 AM [Thread[Connector,5,main]] Warning Connecting to SMD server ms://host.domain.com:50104/P4 failed - error counter: 0 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: invalid response from message server: v1#p#4None:192.168.46.13:50104]

I have validated the P4 URL returns this string, but I'm not sure what the SMDA agent is expecting it to return. The SMD agent install documentation says this is the "http_port_message_server" port. If I use anything other than the P4 port (50104), e.g. the ms/http_port of 8101, I get an "HTTP/1.1 404 Not Found" error, so I'm pretty sure I've got the correct port, since it's looking for the /P4 URL....

Any ideas?

Thanks,

Rich

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi rich. I see two things. No ":" between SAPMS and //, and also, I dont think you enter the "http://" as part of your host name.

here's my script...hostname and p/w redacted, of course.

smdsetup.sh managingconf hostname:"sapms://host@domain" port:"8100" user:"smd_admin" pwd:"password"

also, you may want to check the servername setting in SMD, prior to pointing it to solman, too.

smdsetup.sh changeservername servername:"<value>"

Regards,

Phillip

Answers (5)

Answers (5)

Former Member
0 Kudos

Yes, the sapms prefix is not used with the P4 port. If you are using the P4 port, command syntax is:

smdsetup managingconf hostname:"<fqn>" port:"<p4 port>" user:"<value>" pwd:"<value>" servername:"<value>"

so for you it would be:

/usr/sap/SMD/SMDA97/scripts/smdsetup.sh managingconf hostname:"solman_hostname.domain.com" port:50104 user:SMD_ADMIN pwd:"password"

Not

/usr/sap/SMD/SMDA97/scripts/smdsetup.sh managingconf hostname:"sapms://solman_hostname.domain.com" port:50104 user:SMD_ADMIN pwd:"password"

former_member192350
Active Participant
0 Kudos

Well, I changed the port to 8100 and it connected successfully, even though "http://host.domain.com:8100/P4" returns a 404 error.

Thanks!

Rich

former_member192350
Active Participant
0 Kudos

Sorry, I fat-fingered the config line. This is what I actually typed:

/usr/sap/SMD/SMDA97/scripts/smdsetup.sh managingconf hostname:"sapms://solman_hostname.domain.com" port:50104 user:SMD_ADMIN pwd:"password"

The SCS instance is 00 (with ms/server_port_0 = 81$$, or 8100).

http://solman_hostname.domain.com:8100/P4 returns an HTTP/1.1 404 error

http://solman_hostname.domain.com:8101/P4 returns an HTTP/1.1 404 error

http://solman_hostname.domain.com:50104/P4 returns the string "v1 #p#4None:192.168.46.13:50104"

http://solman_hostname.domain.com:8100/ redirects to http://solman_hostname.domain.com:50100/index.html; clicking on 'System Information' shows 50104 as the "P4 Port"

Any other suggestions?

Rich

Former Member
0 Kudos

Correction...

host.domain.suffix Not "Host@domain" Apologies.

Phillip

Former Member
0 Kudos

Hi,

Check the port,

the Connection is established to the SCS isntance of solution manager. if the SCS instace is on instance no 01. then the port should connect to 8101 and ideally p4 connection to 50104. Hope its mentioned in the installation documents.

confirm whether you are not trying with the Instace of XX Instance(DVEBMGSXX).

kindly revert for any issues.

Thanks,

Jagan