--- title: "SAP GUI connection with ScriptBuilder issue - Connection Failed" slug: "sap-gui-connection-with-scriptbuilder-issue-connection-failed" updated: 2026-06-03T13:26:59Z published: 2026-06-03T13:26:59Z canonical: "success.panaya.com/sap-gui-connection-with-scriptbuilder-issue-connection-failed" --- > ## Documentation Index > Fetch the complete documentation index at: https://success.panaya.com/llms.txt > Use this file to discover all available pages before exploring further. # SAP GUI connection with ScriptBuilder issue - Connection Failed If you encounter this error message when trying to connect to SAP GUI with ScriptBuilder, please follow the instructions below to solve this issue. ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-6G12DSS0.png) 1. Check [SAP GUI Scripting and Security Settings](/v1/docs/sap-test-automation-setup#scripting-and-security-settings). 2. Check [SAP Authorizations](/v1/docs/sap-test-automation-setup#sap-authorizations) and [SAP Server Settings](/v1/docs/sap-test-automation-setup#sap-server-settings). You may need to contact your Basis team to **verify whether the server you’re trying to connect to has scripting enabled**, per Panaya’s specifications. 3. Please verify that you followed these steps to configure at least one [SAP connection](/v1/docs/sap-connections) for capturing scripts with Panaya ScriptBuilder. 4. Check your [SAP Connection Settings in ScriptBuilder](https://success.panaya.com/docs/sap-connection-settings-in-scriptbuilder) and see if changing it to to a different one (Direct/Interactive) helps to resolve the issue. 1. In ScriptBuilder, click on the main menu, and select Settings. Select the SAP GUI tab, and select **Direct Connection**. Click on ‘Browse’ (folder icon) and navigate to the path of your SAP GUI installation. ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-J8EQ7PWA.png) 2. By default, if you have the 32bit version of SAP GUI, the path will be: **C:\Program Files (x86)\SAP\FrontEnd\SAPGUI\sapshcut.exe** If you have the 64bit version of SAP GUI, the default path will be: **C:\Program Files\SAP\FrontEnd\SAPGUI\sapshcut.exe** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-M0JOL6XP.png) 3. After browsing to and selecting the sapshcut.exe, click **Save** to save the path, and try again to connect. 4. It is recommended to try the **Interactive Connection** as well. Open the ScriptBuilder Settings, click on the SAP GUI tab, and select the Interactive Connection. Use the folder icon to browse to the correct path. The default paths (if not changed during installation) are: 32bit SAP GUI: C:\Program Files (x86)\SAP\FrontEnd\SAPGUI\saplogon.exe 64bit SAP GUI: C:\Program Files\SAP\FrontEnd\SAPGUI\saplogon.exe ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-QXZNFOFD.png) 5. The **Interactive Connection** will only work if the *Connection Name in Panaya equals the Connection Name in the SAP Logon Pad*. To copy the connection name from SAP Logon, right-click onto the connection you wish to copy and select **Properties**: ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-OTY9RYCO.png) Copy the ‘Description’ - this needs to be the exact same in the Panaya Connection Name: ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-FB92634J.png) In Panaya: ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-R9CUB029.png) 6. It is recommended to add an instruction to ‘Connect to SAP’, select the correct SAP system, and select ‘Add instruction’. Once the instruction was added, click on ‘Play’ in ScriptBuilder. If there’s an error message showing that states RPC_E_SERVERFAULT, it means that the SAP Server does not have the required settings as [documented here](/v1/docs/sap-test-automation-setup#sap-server-settings). Request your SAP Basis team to verify and adjust the settings. 5. In this step, we will check the Executable file that runs under the **Task Manager**, as this can mean a Registry change is needed. To check this, please try to open ScriptBuilder again and connect it to the SAP system defined. Now, open the **Task Manager** and go to the **Details** tab. Check the SAP executable you are seeing: **SAPgui exe** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-ZWUK4AJA.png) OR **saplogon.exe** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-Y47KW3KS.png)If you see the **SAPgui.exe**file running, please follow the below steps to enable the **saplogon.exe** file on your machine, as this can be the reason for the error above. To resolve this and to modify the Registry settings on your machine: 1. Open the Registry Editor - under Windows Start type **Regedit** and click Enter 2. Search for **SAPGUI** (not “SAPGUI Front“) folder under both of these paths: 1. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP\**SAPGUI** 2. Computer\HKEY_CURRENT_USER\Software\SAP\**SAPGUI** 3. Look inside these paths above for the “StartSapLogon“ key and open it ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-RFSGFYTZ.png) 4. If the value is 0 - change it to 1. If it appears on both paths, change it in both locations. This is what you should see: ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-KO6AR4WM.png) 5. Close any open SAP GUI or SAPLogon windows. 6. Try again to connect to SAP from ScriptBuilder.