Purpose With SwitchTo SAPMR:.. in your local guixt.ini file you can use a central configuration file in the SAP MIME repository. Example: SwitchTo SAPMR:SAP/PUBLIC/GUIXT/GUIXT.INI If this does not work, carry out the following steps. |
Solution 1. Is "IgnoreRegistry Yes" specified in the guixt.ini file? Without "IgnoreRegistry Yes", the settings in the guixt.ini file have no effect; instead, the GuiXT profile parameters are read from the registry. 2. Did you specify a valid RFC user? The RFC user setting is required before the SwitchTo SAPMR:... command. Example: IgnoreRegistry YesRfcCurrentClient YesRfcUser GUIXTRFC2RfcPasswordEnc EVUBYROILPBRGKZRFISLWNQFFXMPRRHPGTVHAUBXEGMJIWMXEWZNVCHR SwitchTo SAPMR:SAP/PUBLIC/GUIXT/GUIXT.INI The "RfcCUrrentClient Yes" is optional. If specified, the RFC call to read the guixt.ini file from the SAP MIME Repository is executed after logon in the logon client, otherwise in client 000. It is therefore important to create the RFC user with the appropriate authorizations in the correct client: 000 without "RfcCurrentClient Yes", and otherwise all clients in which the user can log on. 3. Does the RFC user have the necessary authorizations? We repeat the authorizations specified in RFC authorizations Authorization object S_RFC: RFC_TYPE=FUGR, RFC_NAME=SKWF_NAMESPACE, ACTVT=16 RFC_TYPE=FUGR, RFC_NAME=SKWF_IO, ACTVT=16 RFC_TYPE=FUGR, RFC_NAME=SKWF_CONTENT, ACTVT=16 RFC_TYPE=FUGR, RFC_NAME=RFC1, ACTVT=16 RFC_TYPE=FUGR, RFC_NAME=SDIFRUNTIME, ACTVT=16 RFC_TYPE=FUGR, RFC_NAME=RFC_METADATA, ACTVT=16 If the RFC user/password is incorrect or authorizations are missing, either an error message is displayed in the GuiXT "Protocol" window, or you must take a look at the SAP system log (transaction SM21) or the SAP ABAP dump display (transaction ST22). Here are some examples: Case RFC user name not found or wrong password
Case missing authorization, transaction SM21 (SAP system log). Please observe: The GuiXT protocol window probably does not show this error text.
Case missing authorization, transaction ST22 (SAP ABAP dumps) In transaction ST22 you see the missing authorization and, later on in the text, the RFC user name and client:
3. Does the central guixt.ini file with the specified path exist in the SAP MIME repository? Compare the path in the local guixt.ini with the path in the SAP MIM Repository (transaction SE80-> MIME Repository, or transaction SO2_MIME_REPOSITORY).A more technical way to check the URL is to execute the function module SKWF_NMSPC_IO_FIND_BY_ADDRESS in transaction SE37, test environment. Copy the guixt.ini URL from your guixt.ini file, but without "SAPMR:", and enter "MIME" as the application. The result should look something like this, in particular the "ERROR" output should be "000":
4. Final resort: Generate a GuiXT system trace Add the following commands in your local guixt.ini file: Trace Yes with a suitable temporary folder on your PC. Then execute the login again. In the resulting trace file, search the line "Starting RFC connection": Starting RFC connection ""= NWRFC connection text=CLIENT=100 NWRFC connection text=USER=GUIXTRFC2 NWRFC connection text=CODEPAGE=4110 NWRFC connection text=PASSWD=*** NWRFC connection text=LANG=DE NWRFC connection text=ASHOST=S4HDEV NWRFC connection text=SYSNR=00 NWRFC connection text=USE_SAPGUI=0 NWRFC connection text=LCHECK=0 RFC connection done p_rfcc->RfcHandle=0B6E7758 RFC RfcCall RfcHandle=0B6E8ACC RFC RfcCall and RfcReceive done RfcRC=0 RFC Download from SAP Mime Repository text=SAP/PUBLIC/GUIXT/GUIXT.INI=URL not found Perhaps this will give you an indication of what is going wrong. Otherwise, please contact Synactive.
|
Components |