Problems in SMD

[Former Member]

Hi all,

I have setup a solution (SAP Portal 7) in Solution Manager 4.

I sent this solution to Solution Manager Diagnostics. Now I get problems in the Root Cause Analysis by clicking on Java System Info I get the error message "Cannot retrieve remote port, please check if Scheduler tasks have successfully completed".

I checked the scheduler and get the error "com.sap.admin.scheduler.exception.WarnTaskExecution: startInstance |Server] Attributes <Types> or <ID> cannot be null or empty".

Maybe I missed a step by setting up the solution in SMSY?

Thanks a lot for your responses.

BR,

Andreas

[Former Member · Accepted solution]

Dear Andreas,

It seems that he datacollect task found some remaining files of disabled server nodes on your applications servers. This is the caused of the warnings.

The location of the files is /usr/sap/SID/XXXXX/j2ee/cluster/server0,

server1, server2 ...

You should check in the configtool which server are not used and delete

the corresponding files.

Hope this solution helps.

Regards

Amit

[Former Member · Accepted solution]

Hi,

thanks for your response.

I'll check.

DO you think that this problem is related to my problem with "Cannot retrieve remote port"?

BR,

Andreas

[Former Member]

Dear Andreas

In most of the cases that I have seen it is related.

Regards

Amit

[Former Member]

Hi,

thanks for your response.

I've checked the files in /usr/sap/<SID>... cluster/serverx.

There's only server0 in the filesystem and this server is used in the configtool.

Strange...

BR,

Andreas

[patrice_palazzolo]

Hi Andreas,

Could you please check if the user running SMDAgent has read permission on the /usr/sap/<SID> directory ? if not please add it and run again the DataCollect.

Another cause of this warning message could be that the installation path is not set correctly at the mainInstance level. Is the MainInstance Path set to /usr/sap/<SID> ?

In fact the datacollect is reading the server id node from the following file

/usr/sap/<SID>/JC??/j2ee/cluster/instance.properties

if for permission reason or wrong installation path, this could end up in warning message " ... <ID> cannot empty ..."

Regards

Patrice.

[Former Member]

Hi Patrice,

thanks for your response.

The user has read permissions on all directories.

What do you mean by "MainInstance Path"?

You mean by transferring data from SM to SMD by the wizard?

BR,

Andreas

[patrice_palazzolo]

Hi Andreas,

the mainInstance Path is set by the user when running transaction SMDIAG_WIZARD in SolMan.

Note : on a SMD SPS12 version the MainInstance path is set in the Managed System Setup Wizard.

Another point, are the J2EE Engine and SMD Agent installed on the same Hard Drive ? if not please insure that the Drive letter is also specified in the InstallationPath. Usually for a SAP J2EE Engine the installation path looks like

<DriveLetter>:/usr/sap/<SID>

Regards

Patrice.

[Former Member]

Hi Patrice,

thanks for your response.

The maintance path is set correctly.

The J2EE and SMD Agent are installed on the same hard drive, the operating system is Unix --> I don't need to setup a drive letter.

BR,

Andreas

[patrice_palazzolo]

Hello,

Are you able to use the following application in SMD : File System Browser ?

are you able to go and download following file : /usr/sap/<SID>/J??/j2ee/cluster/instance.properties ?

Patrice.

[Former Member]

Hi Patrice,

yes that's both working.

BR,

Andreas

[patrice_palazzolo]

Hi Andreas,

sounds quite strange to me. Is it possible to give me an access to your system in order for me to have a look ? I'm just out of suggestion.

Regards.

Patrice.

[Former Member]

Hi,

same for me

I'm sorry but it's not possible for me to give you access to the system.

Not allowed by the customer... still waiting for a solution from SAP.

BR,

Andreas

[Former Member]

Hi Andreas,

Did you already have the solution for this issue from SAP?

-adhi

[Former Member]

Hi,

the problem occurred because there was a wrong setup for the message server in the solman_diag wizard. After resetting it to the default values it was working.

BR,

Andreas

[Former Member]

Dear Andreas,

Is your Datacollect task run successfully?

Is the monitored setup showing error?

Did you try to connect your monitored system using telnet from the

monitoring system?

Please have a look to Diagnostics Setup -> Managed System - > Monitored

Setup. You will see configuration error/warning for all systems. In Most cases,

Either telnet is not found, Database is not setup, or Data collect did

not run.

Note 1023380 might help in resolving the known issues.

Finally it might be an issue with an wrong path entered in smdiag_wizard.

Hope that the above suggestions help resolve the issue.

Regards

Amit

[Former Member]

Hi Amit,

thanks for your repsonse.

I the datacollect scheulder task I get the error

"com.sap.admin.scheduler.exception.WarnTaskExecution: startInstance |Server] Attributes <Types> or <ID> cannot be null or empty".

Do you know where I can maintain this Attributes??

Thanks a lot.

BR,

Andreas