CALL_FUNCTION_SIGNON_REJECTED in SM21 - syslog

[former_member233385]

Hi Basis Expert,

We completed refresh of our entire landscape.

After the refresh we found few defect which was raised.

One of the defect which we have in our EHP6 for ERP6.0 system is "Runtime error "CALL_FUNCTION_SIGNON_REJECTED" occurred".

In sm21 - syslog we found entries related to "CALL_FUNCTION_SIGNON_REJECTED". This is coming from SAPSYS user.

Also checked the parameter rfc/signon_error_log and value is 0.

Appreciate your help.

Regards,

Anil Shenoy

[isaias_freitas]

Hello Anil,

It looks like a remote system is trying to logon with incorrect credentials.

Check out the "server-side information" section of the dump.

It will show information about the client (source) of the connection.

The next step is to go to this remote system and identify the wrong credentials there, and fix it.

Regards,

Isaías

[alwina_enns]

Hello Isaías,

we need the dump in ST22 first. With the setting "rfc/signon_error_log and value is 0" no dumps in ST22 are created, only entries in the syslog. According to documentation in RZ11:

"If you set the value of the profile parameter to 0 (that is,

rfc/signon_error_log = 0), no ABAP short dump is written, but an entry

is created in the syslog."

Regards,
Alwina

[isaias_freitas]

Yes, of course you need to get the dump first (by setting "rfc/signon_error_log = 1") .

[former_member233385]

Hi Alwina / Isaias,

Thanks a lot for providing the information.

Regards,

Anil

[alwina_enns]

Hello Anil,

you should set

rfc/signon_error_log = 1

and restart the system, so that the dump is created in ST22 and you can check details in the dump, for which user and which program it is created. Only from the syslog entry you will not be able to find the causer.

Regards,
Alwina

[former_member233385]

I forgot to give the system details in my previous message. Below are the details.

OS - Windows NT

DB - MS SQL

Regards,

Anil Shenoy