In our experience, questions or problems with GuiXT often arise in the following areas:

Typical problems are described below. You can also find many specific questions and answers on our Q&A page.

1. Issues with the license for InputAssistant and GuiXT Controls

If GuiXT does not work as expected, check the GuiXT window under View->Protocol to see if any error messages are displayed:

1A: Missing license key for a specific SAP system

A missing license key will cause GuiXT to disable a component. For example, if the guixt.ini file contains the following entries:

IgnoreRegistry Yes
Component GuiXT
Component InputAssistant 
Key MyCompany_612.Q4H.ldmwphoskzrt
Key MyCompany_612.P4H.tkimnvoskzrt

GuiXT displays the following error message when logging into a S4H system:

"No License Key, component selection reduced to GuiXT. System:  S4H"

Solution : Request a valid license key from Synactive and add it to the guixt.ini file:

IgnoreRegistry Yes
Component GuiXT
Component InputAssistant
Key MyCompany_612.Q4H.ldmwphoskzrt
Key MyCompany_612.P4H.tkimnvoskzrt
Key MyCompany_612.S4H.hrxhfdoskzrt 
  

1B: Missing license file

In addition to the license key, a license file is required, which contains, for example, the number of licensed users. If this file is missing, the following message appears:

GuiXT then displays the following error popup when logging into the SAP system:

 

Solution : Add the path to the license file to the guixt.ini file:

IgnoreRegistry Yes
Component GuiXT
Component InputAssistant
Key MyCompany_612.Q4H.ldmwphoskzrt
Key MyCompany_612.P4H.tkimnvoskzrt
Key MyCompany_612.S4H.hrxhfdoskzrt 
LicenseFile H:\GuiXT\license\guixtlicensefile.txt
 

If you specified "LicenseFile" but the file was not found, the followng error message is shown:

 

Note: If you have a valid license for the "GuiXT Script Editor Pro", you can leave "LicenseFile" and "Key" empty in the GuiXT profile on your development computer and use all GuiXT components in all SAP systems.

The following message will appear in the GuiXT "Protocol" window:

 

2. Problems with the RFC connection

Problems with the RFC connection often occur when reading the central file guixt.ini from the SAP MIME repository.

2A: No RFC user or RFC password specified

If the guixt.ini file contains the following entries:

IgnoreRegistry Yes
SwitchTo SAPMR:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI

i.e., the RFC user and password are not specified, the RFC connection fails. Due to the missing password, the following popup appears:

Since no RFC user name is specified in our case, the RFC connection fails and a corresponding message appears in the "Protocol" window:

Solution : Add the required credentials to the guixt.ini file using RfcUser and RfcPasswordEnc.

 

2B: RFC user not present, locked or incorrect password

Example:

IgnoreRegistry Yes
RfcUser GUIXTRFC
RfcPasswordEnc AGIOOJKIFOMNPODGHCMNEOJLBMOKGFGMIMNIFBICEFEFOLMGLNAFDPEKGPDOJJNJ
SwitchTo SAPMR:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI

The error message indicates that the RFC login is in client 000. If the RFC user doesn't exist and the password is incorrect, GuiXT cannot establish an RFC connection. Typically, the login occurs in client 000 by default, which is not always desired. In this case, use the RfcCurrentClient option:

Solution : Use the RfcCurrentClient option.

IgnoreRegistry Yes
RfcCurrentClient Yes
RfcUser GUIXTRFC
RfcPasswordEnc AGIOOJKIFOMNPODGHCMNEOJLBMOKGFGMIMNIFBICEFEFOLMGLNAFDPEKGPDOJJNJ
SwitchTo SAPMR:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI

With "RfcCurrentClient Yes," the central guixt.ini file is read only after SAP logon, since the client is unknown beforehand. Alternatively, you can also read the central guixt.ini file in a fixed client, e.g., 100. To do this, omit RfcCurrentClient and specify the client in SwitchTo as follows:

SwitchTo SAPMR,client=100:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI

The error message (above) now shows the correct client 100. However, in our test case the encrypted password was incorrect, hence an error message.

After several failed attempts - the number is configurable in SAP - the SAP system locks the RFC user, so that even with a correct password, login is no longer possible:

 

The RFC user can be unlocked in transaction SU01:

With the correctly specified RFC password, access to the central guixt.ini file should then work - if it exists. Otherwise, the following message appears:

Insufficient permissions for the RFC user can also prevent the central guixt.ini file from being read. The necessary permissions can be found here: RFC authorizations.

Example:

We add the authorization for the function group RFC_METADATA of the module RFC_META_DATA_GET in the SAP system:

This is how it works:

 

3. Problems in a custom script or a specific SAP transaction

If a script does not work as expected, follow these steps:

3A: Check syntax errors

GuiXT script window

 

GuiXT Script Editor Pro

 

 

3B: Turn on the trace (GuiXT window or Script Editor Pro)  

If the problem is related to an InputScript , enable the trace in GuiXT:

 

GuiXT Trace Window / InputScript Trace in Script Editor Pro

 

Script Editor Pro: Display runtime errors directly in the Script Editor

 

 

3C: Use debugging

In Script Editor Pro you can display the field contents while debugging.

 

3D: Review recent changes

If the feature worked before, consider what might have changed:

  3E: The error only affects a specific user?

 

3F: The cause of the error is unclear

If you're still stuck despite all these steps, send a detailed request to Synactive (email to support@synactive.com). Please include the following attachments: