Skip to Content
author's profile photo Former Member
Former Member

Installing EHP4 in Suse SLES 11 SP2 fails in Phase 24 of 29 (Start central services instance)

Hi,

I am installing “SAP ERP 6.0 EHP4 Ready – Support Release 1” -> “SAP Application Server ABAP” -> “Oracle” -> “Central System”, the installation stops in phase 24 of 29 (Start central services instance).

Does anyone have an idea of what may be the problem, the warnings and errors I have in sapinst_xxx.log are:

WARNING[E] 2012-04-12 18:13:19.270

CJSlibModule::writeError_impl()

FSL-02015 Node /usr/sap/DEV/SYS/exe/run/rfcexec.sec does not exist.

ERROR 2012-04-12 18:13:19.737 [sixxcstepexecute.cpp:950]

FCO-00011 The step copyRFCExecSec with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|copyRFCExecSec was executed with status ERROR .

Kind regards

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Apr 13, 2012 at 05:17 PM

    Hello,

    From error the installation is failing due to RFC issues. Can you

    logon to the sapsystem using DDIC with the default password? If so

    run the reports RSWBOINS and RADDBDIF from SE38. Do you get errors?

    regards,

    John Feely

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 02, 2013 at 04:21 PM

    Basically it's a text file you can create manually to your likings.

    It should contain access priviliges as follows:

    Information for the access control is maintained in the 'rfcexec.sec' operating system file and the RFCEXEC program reads the information from this file. You can select the storage location as you wish. If the 'rfcexec.sec' file is not contained in the work directory of RFCEXEC, you must find the storage location of the file using the 'RFCEXEC_SEC_FILE_PATH' environment variable on RFCEXEC.

    The system administrator is responsible for protecting the 'rfcexec.sec' file against unauthorized access.

    Structure of 'rfcexec.sec' file

    The format of the file is similar to the format of Saprouter strings and has the following syntax:

    /U/<user name>/C/<client>/T/< list of allowed connection types>/F/<list of allowed functions>/O/<list of not allowed operating system commands>/S/<allowed partner snc name>/

    Optional specifications and an alternative syntax are not permitted. If an entry is to be treated as irrelevant, an asterix #*# is used as a value for positive lists and a blank ' ' is used for negative lists.

    A comma ',' is used as a list separator.

    Examples for the 'rfcexec.sec' file

    Contents of the file if no particular restriction has been made (delivery status of the file):

    /U/*/C/*/T/*/F/*/O/ /S/*/

    Contents of the file if calls are only allowed from an ABAP system:

    /U/*/C/*/T/3/F/*/O/ /S/*/

    Contents of the file if calls are only allowed from an ABAP system by user "SMITH". The user is allowed to call all functions.

    /U/SMITH/C/*/T/3/F/*/O/ /S/*/

    Contents of the file if access to the RFC_REMOTE_EXEC and RFCPING functions is restricted. In this case, the "rm" statement must not be executed by the functions.

    /U/*/C/*/T/*/F/RFC_REMOTE_EXEC,RFCPING/O/rm/S/*/

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.