Powerbuilder Application Execution Error R0035 May 2026
PowerBuilder execution error R0035 (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
This error generally stems from communication failures between PowerBuilder and external components like Microsoft Excel, Word, or custom DLLs: PowerBuilder Application Execution Error R0035!
PowerBuilder Application Execution Error R0035: Causes and Solutions
Are you experiencing the frustrating PowerBuilder application execution error R0035? This error can occur when running a PowerBuilder application, causing disruptions and hindering productivity. In this article, we'll explore the possible causes of error R0035 and provide step-by-step solutions to help you resolve the issue.
What is PowerBuilder Application Execution Error R0035?
Error R0035 is a runtime error that occurs when a PowerBuilder application fails to execute properly. The error message typically appears as:
"PowerBuilder Application Execution Error R0035: [Error message]"
The error can manifest in various ways, such as: powerbuilder application execution error r0035
- Application fails to launch
- Application crashes during execution
- Error message appears when accessing specific features or functions
Causes of PowerBuilder Application Execution Error R0035
After investigating various instances of error R0035, we've identified some common causes:
- Corrupted PowerBuilder installation: A corrupted or incomplete PowerBuilder installation can lead to runtime errors, including R0035.
- Incompatible PowerBuilder version: Using an incompatible version of PowerBuilder or mismatched DLLs can cause errors.
- Missing or outdated dependencies: Failing to install or update required dependencies, such as database drivers or third-party libraries, can lead to errors.
- Syntax errors or bugs in the application code: Errors in the application code, such as syntax errors or incorrect function calls, can cause runtime errors.
- System configuration issues: System configuration issues, such as incorrect environment variables or registry settings, can affect PowerBuilder application execution.
Solutions to PowerBuilder Application Execution Error R0035
To resolve error R0035, try the following step-by-step solutions:
Solution 1: Verify PowerBuilder Installation
- Check the PowerBuilder installation for corruption or incomplete installation.
- Reinstall PowerBuilder if necessary.
- Ensure that the PowerBuilder version is compatible with your system and application.
Solution 2: Update Dependencies and DLLs
- Check for updates to database drivers, third-party libraries, and other dependencies.
- Install or update the required dependencies.
- Verify that the DLLs are correctly registered and up-to-date.
Solution 3: Debug and Fix Application Code download these free tools:
- Review the application code for syntax errors or bugs.
- Use PowerBuilder's built-in debugging tools to identify and fix errors.
- Test the application thoroughly to ensure that the errors are resolved.
Solution 4: Check System Configuration
- Verify that environment variables, such as the PATH and LIBPATH, are correctly set.
- Check the registry settings for PowerBuilder and related components.
- Ensure that the system configuration is compatible with PowerBuilder and the application.
Conclusion
PowerBuilder application execution error R0035 can be caused by various factors, including corrupted installations, incompatible versions, missing dependencies, syntax errors, and system configuration issues. By following the step-by-step solutions outlined in this article, you should be able to identify and resolve the error, ensuring smooth execution of your PowerBuilder application. If the error persists, consider reaching out to Sybase support or a PowerBuilder expert for further assistance.
Application Execution Error R0035 in PowerBuilder is defined as: "System error."
This is a generic, low-level error indicating that the application attempted to perform an invalid operation at the system level. It is often the "catch-all" error when PowerBuilder encounters an issue it doesn't have a specific error code for.
Here is a comprehensive guide to troubleshooting and resolving R0035.
Step 3: Install or Copy Missing Files
- Option A (Recommended): Run the official PowerBuilder Runtime Packager (
.msior.exe) provided by the application vendor. - Option B (Manual): Copy all required DLLs from a working PowerBuilder installation or runtime distribution into:
- The application’s own folder, OR
C:\Windows\System32(for 64-bit) orSysWOW64(for 32-bit on 64-bit Windows), OR- A folder listed in the system
PATH.
2. Invalid DataWindow Operations
R0035 frequently occurs during DataWindow processing if the buffers are in an unexpected state. The application’s own folder
- GetItem/SetItem Errors: Trying to get or set data in a row or column that does not exist, or accessing a deleted row.
- Buffer Issues: Accessing the
Delete!buffer when it is empty. - Fix: Always check
RowCount()andFindRowresults before manipulating data.Long ll_row ll_row = dw_1.GetRow() If ll_row < 1 Then Return // Prevents crash if no row selected// Check column existence If dw_1.Describe("my_column.Visible") = "!" Then Return
What is PowerBuilder Error R0035?
Error R0035 is a runtime execution error in PowerBuilder applications. It typically occurs when the PowerBuilder runtime engine cannot locate or load a required PowerBuilder resource file (PBR) or when there is a mismatch between the compiled application and the runtime environment.
The full error message usually reads:
PowerBuilder Application Execution Error (R0035) Application terminated. Unable to find required PBR file.
or simply:
R0035: Unable to locate the application's resource file.
5. Tools You Need
To effectively solve R0035, download these free tools:
- Dependency Walker (depends.exe): Essential for seeing exactly what functions are inside a DLL and what other DLLs it needs.
- RegShot: Useful for taking a snapshot of the registry before and after installing a component to see where it registers.