Does the error happen on a 64-bit or 32-bit operating system?
Copy the entire application folder from the network to the local C:\temp . Run it from there. If it works, the issue is network latency, permissions, or path length.
Ensure the path to the PowerBuilder Runtime folder (e.g., C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime [Version] ) is present. 3. Deploy Missing PowerBuilder DLLs Locally
A cannot execute functions inside a 64-bit COM DLL .
, verifying file paths, ensuring proper runtime files are installed, and checking for 32-bit/64-bit mismatches. For a detailed troubleshooting guide, visit Appeon Community Appeon Community powerbuilder application execution error r0035
interval = 900000 // 15 minutes in milliseconds ole1 = CREATE OLEObject rs = ole1.ConnectToObject("Excel.Application") rs = ole1.SetAutomationTimeout(interval)
What (e.g., 2019, 2022, 2025) are you using?
Right-click each library (PBL) and select . This removes deleted object fragments and defragments the library file. Right-click the Target and select Full Build . Step 2: Implement Strict Null Object Checking
PowerBuilder execution error (typically displayed as "Error calling external object function") is a runtime error that occurs when a PowerBuilder application attempts to invoke a method or property on an external object—usually an OLEObject or ActiveX control —that the system cannot find or execute. Core Causes Does the error happen on a 64-bit or 32-bit operating system
In the PowerBuilder IDE:
This cause is more common in development. The R0035 error can appear when the way PowerBuilder calls an external function does not match the function's expected parameters. This can happen when calling functions in standard DLLs or COM objects.
| Cause | Description | |-------|-------------| | | The core pbvm*.dll (e.g., pbvm170.dll , pbvm125.dll ) is not in the system path or application directory. | | Wrong DLL version | The installed runtime files do not match the PowerBuilder version used to compile the app. | | Missing runtime files | Other required files like libjcc.dll , pbdwe*.dll , or pbrtc*.dll are absent. | | PATH environment issue | The system PATH does not include the directory containing PowerBuilder runtime DLLs. | | 64-bit vs 32-bit mismatch | The application is 32-bit, but the runtime is 64-bit (or vice versa). | | Dependency corruption | A required C++ runtime or Windows system DLL is damaged. |
Before modifying any code, ensure that your compilation environment is clean. Incremental builds can leave behind ghost references. Open your PowerBuilder IDE. Right-click on your Target and select . Reopen the Target. If it works, the issue is network latency,
Incorrect data types in external function declarations often lead to r0035. Ensure that the PowerScript declaration matches the DLL function signature exactly.
: In PowerBuilder, use the OLE Browser (found under Tools -> Browser -> OLE tab) to verify that the properties and functions you are calling actually exist in the registered object. Debugging with pbdebug
Modern Windows security features, such as Data Execution Prevention (DEP), are designed to block code execution from non-executable memory regions. Older PowerBuilder runtimes (especially versions prior to PB 12.5 or PB 2017) often violate these security rules, prompting Windows to shut down the app. Step-by-Step Troubleshooting and Solutions