SMD Setup

[Former Member]

Hello Guru's,

I have configured solution manager diagnostics on solution manager and installed SMD agent on satellite system (BW). While starting the agents on solution manager both systems are keep dumping with “CALL_FUNCTION_NOT_FOUND” & “CALL_FUNCTION_REMOTE_ERROR” errors. I couldn’t able to figure out the problem.

Sequence of things done on Solution Manager

1. Change the Backend Client from 001 to 350

2. Deploy the SMD server package (SPS13).

3. Deployment of IS Agent (ISAGENTSMD71*.SCA)

4. Disable Maintenance Mode

5. Run SMD Upgrader

6. SMD Diagnostic Server Setup Wizard

7. Wily Enterprise Manager Installation

8. Install the SAP Management Modules

9. SMD Server Setup Wizard (Monitored System Setup)

10. Connect Managed System to SMD Server

11. SMSY Landscape Definition

Sequence of things done on Solution Manager

1.SMD AGENT Installation

2. Wily Introscope Agent Installation & Configure the Agent on BWS

3. Creating Auto Probe Connector

4. New JAVA VM Parameter on BWS for Auto Probe

5. Setup RFC Destinations to Managed System

ERROR 1:

Runtime Errors CALL_FUNCTION_NOT_FOUND

Date and Time 12/17/2007 14:05:33

Short text

Function module "SMD_DATA_LOADER100" not found.

What happened?

The function module "SMD_DATA_LOADER100" is called,

but cannot be found in the library.

Error in the ABAP Application Program

The current ABAP program "SAPLE2E_FUNC" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

The program "SAPLE2E_FUNC" contains the CALL FUNCTION statement.

The name of the function module to be called is "SMD_DATA_LOADER100".

No function module exists with the name "SMD_DATA_LOADER100".

All function modules are listed in the Function Library (SE37).

-

Possible reasons:

a) Wrong name specified. Pay particular attention to

upper/lower case and underscores ("_").

or

b) Transport error

c) In the case of an enqueue/dequeue module,

the lock object may not have been activated

(ABAP/4 Dictionary).

How to correct the error

Check the last transports to the SAP System.

Is the program "SAPLE2E_FUNC" currently being changed?

If an enqueue/dequeue module is involved, is the activation

of the lock object missing in the ABAP/4 Dictionary?

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"CALL_FUNCTION_NOT_FOUND" " "

"SAPLE2E_FUNC" or "LE2E_FUNCU15"

"E2E_ME_RFC"

Function modules with names similar to "SMD_DATA_LOADER100":

SMD_DOWNLOAD

SMSY_DATA_XML_UPLOAD

SAP_OI_LOAD_MIME_DATA

S_AUTH_ROLE_DATA_LOAD

SCPR_TR_READ_DATA_LOBJ

SMD_USAGE_DATA

SMSY_DATA_XML_DOWNLOAD

SMSYAD_GET_DATA_FROM_LCR

SMSYAD_GET_DATA_FROM_LIS

SMSYAD_GET_AC_DATA_FROM_LCR

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

ERROR 2

Runtime Errors CALL_FUNCTION_REMOTE_ERROR

Date and Time 12/12/2007 13:08:25

Short text

"Function module "SMD_MDX_QUERY_EXECUTE" not found."

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLE2E_FUNC" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The error occurred during an RFC call to another system.

In the target system, a short dump has been written as well.

More detailed information on the error cause can be found there.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An error occurred when executing a REMOTE FUNCTION CALL.

It was logged under the name "CALL_FUNCTION_NOT_FOUND"

on the called page.

How to correct the error

Please refer to the notes described in the

short dump.

Please help me ASAP....................

Regards,

Ravi.

[Former Member]

Hi!

Can you please help me with my issue?

I would like to setup SMD functionality.

I use SAP Solution Manager 4.0 with SP 13.

Here are the steps I already executed:

a) Installation of Wily Introscope Enterprise Server 7.1 (Location: Server of SOLMAN)

b) Deployment if file ISAGENTSMD71*.SCA (Location: Server of SOLMAN)

c) Setup steps on SOLMAN (conf. of at least 3 BTC processes, activation of BI source system, configuration of SLD according to tcode SPRO)

The errors I currently have:

1) Managed Systems Setup

I am about to set up the SMD for the monitored systems via http://server:50000/smd --> Diagnostics Setup --> Managed Systems --> Setup Wizard

Retrieval of selected solutions failed

The contents of at least one solution could not be retrieved from Solution Manager, or could not be uploaded to Diagnostics DB

Server->Server : java.lang.IllegalStateException: Warnings occured during Initial Upload : XML Template parsing generated warnings

Sat Jan 05 16:18:57 CET 2008 | storeHost(...):Host []

serverIP-Adressnull:Cannot insert/update the host

'[IHost: key=119954633765http://... (RC=2)

Do you still want to proceed to next step?

2) Acces to Root Cause Analysis --> Exceptions Error

Logon failed

What has happened?

Call of URL http://server:8000/SAP/BW/BEX terminated due to error in logon data.

Note

Logon performed in system <SID>.

Logon performed for client xxx and language EN.

What can I do?

Check the validity of your SSO ticket for this system.

If you do not yet have a user ID, contact your system administrator.

Error Code: ICF-LE-http-c:666-l:E-T:21-C:6-U:5-P:5-L:3

HTTP 401 - Unauthorized

My questions:

- Which additional settings for SDM setup (on SOLMAN and on the site of satellite systems) should be done?

- How can the errors (see above) be fixed?

- Should some additional SLD configurations be executed for the monitored systems?

[Former Member]

Hi,

1)Have you installed the SMD Agent on satellite system?

2) Activate the virtual host using SICF

3) Did you meet the prerequisites according to note 1061383?

4) Check the queries are activated or not using RSOR transaction. Follow note 1110013.

Thanks,

Ravi.

[Former Member]

Hi, RFC Trusted User in both systems..

Thanks

[Former Member]

Hi Ravikanth,

It is hapening because RFC user does not have proper authorizations. Please add S_RFC & S_RFCACL. It will work. I had same issue.

Thanks,

[Former Member]

Hi,

Which RFC user? You mean SOLMAN<SID> in solution manager. Please let me know.

Regards,

Ravi.

[markus_doehr2]

Do you have the ABAP addon ST-A/PI installed on both systems?

check http://service.sap.com/supporttools

--

Markus

[Former Member]

Hi Markus,

Thanks for the quick reply. Yes i do have addon ST-A/PI on both systems. Please see the details below.

SOLUTION MANAGER 4.0:

Support Pack level : SPS13

ST-PI : 2005_1_700 Patch level5

ST :400 patch level 13

ST-A/PI : 01J_CRM50 Patch level 0

Satellite system (BW): NW04s

Support Pack level : SPS10

ST-PI : 2005_1_700 Patch level5

ST-A/PI : 01J_BCO700 Patch level 0