Trusting RFC, RFC Authorization Error

Q
RFC Authorization Error
runner to run Winshuttle.why we get error - "user had no RFC authorization" - authorization problem data not found.
You SAP user inside your RFC connection is missing S_RFC and similar security profiles.

Ans-: If you have mixed upper/lowercase characters in your password, please check out sap note 1023437 - ABAP syst: Downwardly incompatible passwords (since NW2004s)
Mostly when we submit the password which is wrong it displays the message such like that
actually rfc authorization is When a remote call of a function module is made, an automatic authorization check is performed, provided that the profile parameter auth/rfc_authority_check is set to 1. The authorization check uses the authorization object S_RFC to check whether the user defined in the destination has RFC authorization for the function group of the called function module.


Q
Why dump CALL_FUNCTION_SIGNON_REJECTED in our production system at regular interval (every 30 mins). This dump is generated only from all of the application servers, but not from the central instance. SAPSYS user is generating this dump.

An external system, is trying to login into your PRD system every 30 minutes. Check your other system to find failed jobs (SM37) or short dumps (ST22).
Ans-:
CALL_FUNCTION_REMOTE_ERROR shows when there is some issue on REMOTE server. Try to check the logs on that remote server where you want to execute this function.

You can also search for a function/program name on internet.
Another way
Note 171805 - Determining RFC client when sign-on problems occur
Note 313971 - Monitoring: RFC error messages for SAPSYS users

SAP Note 13347 - CALL_FUNCTION_SIGNON_REJECTED

The RFC using to connect to your system can have the wrong password or problem with the user id.
it may be issue-:
This is due to authorisation issues . This seems to be issues in RFC connections. Check all your connections



Q
Have offline backup of db. but need to restore it , so that we can restore to my previous state. how it can be done
Ans-: we can do it by using BRTOOLS (OR) BRRESTORE.
If you have brtools 7.00 and above then have a look at note 1003028 which talks about enhanced database copy in brtools.
Using brrecover is a good option
you can recover using the commance brrecover -c force -t complete -b last (This will do a complete recovery )
or do a point of time recovery using
brrecover -c force -t dbpit -b last -seq last
This will not only restore but also recover your database.

Another way to solve the problem
Just restore datafiles from the backup like sapdata1 to sapdata1 ,sapdata2
to sapdata2 ,sapdata3 to sapdata3 ,sapdata4 to sapdata4 and so on.

As it is offline backup so it does not requires redologs.





Q
What is Trusting RFC.After setting trust connection between ECC & SolMan one TRUSTING_SYSTEM@ rfc is generated by system automatically in system both side.

What is use of it and does it effect trust connection if it is deleted?
Ans
Solman is reading/writing data from other systems through this RFC
etc monitoring, transport management, key distributions, project management, ... whatever you use solman for

If this rfc is not working properly then the solman functions will not work either.

Q
Will the Trace File be Lost if the System is Restarted? will you loose the trace file, or can you see?

ans-:In SAP the st11 dev trace files are created anew for every system
restart...dev_w0 dev_w1 etc.. in /usr/sap/SID/DV*/work directory.
SAP only keeps one .old version.
If you want to keep more, rename it something other than .old.