is a critical runtime error that occurs when a PowerBuilder application fails to communicate with an external Object Linking and Embedding (OLE) server, a Component Object Model (COM) library, or an external Dynamic Link Library (DLL). The core error message text— "Error calling external object function" —indicates that PowerScript successfully recognized the OLE object container but failed to execute the specific method or function called within the external resource.
: The OLE procedure call took longer than the internal timeout period (default is 5 minutes). If the request is expected to be long, the default may need adjustment.
PowerBuilder applications can be deployed as 32-bit or 64-bit binaries. An architecture mismatch will prevent components from communicating:
Troubleshooting PowerBuilder Application Execution Error R0035 powerbuilder application execution error r0035
is a common runtime exception that occurs when an application fails to invoke a function or method on an external Object Linking and Embedding (OLE) or Component Object Model (COM) object. Because PowerBuilder resolves dynamic OLE/COM calls at runtime rather than during compilation, the compiler will not catch these errors. This comprehensive troubleshooting guide covers why this error occurs, how to locate its root cause, and how to resolve it across different client environments. Comprehensive Overview of Error R0035
Whether the error happens on or just specific ones.
: Check that the COM object class (CLSID) exists in the Windows Registry on the machine where the error occurs. Check Return Codes is a critical runtime error that occurs when
Ensure a 32-bit application is not accidentally trying to load 64-bit PowerBuilder runtime DLLs, or vice versa. Step 2: Implement Isolated Deployment (Local DLLs)
The typically occurs when PowerBuilder tries to communicate with a Windows-level component or an external DLL and the interaction fails. The error message may look like this:
, 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 If the request is expected to be long,
Are you seeing this error with a specific , such as Excel, Crystal Reports, or a custom ActiveX control? PowerBuilder Application Execution Error R0035!
Re-run the app. The log will show exactly which PBD failed to load and why (file not found, access denied, bad format).
Resolving this error requires identifying where the memory violation occurs. The most frequent culprits include: 1. Corrupted DataWindow Objects or PBLs
Look for "FILE NOT FOUND" results. This will tell you exactly which DLL or PBD the application is searching for right before it throws the R0035 error. 5. Validate DataWindow Objects
Older PowerBuilder versions (pre-2019) are strictly 32-bit. If you deploy to a 64-bit system and place PBDs in C:\Program Files (which redirects to C:\Program Files (x86) for 32-bit apps), path redirection can confuse the PBVM.