: The application was compiled in one version of PowerBuilder (e.g., PowerBuilder 2019), but the client machine is running a different version of the PowerBuilder Runtime.
"Error calling external object function [function_name] at line [X]" Appeon Community 1. Root Causes Unregistered or Missing Components : The OLE/COM component (e.g., an
PowerBuilder applications rely heavily on specific dynamic link libraries (DLLs) like pbvm.dll , pbdwe.dll , and pbshr.dll . If the client machine has a different version of these DLLs than the version used to compile the application, the system will crash with an R0035 error. 2. Corrupted PowerBuilder Dynamic Libraries (PBDs)
: The external server (like a background instance of Excel) has crashed, "died," or been closed by the user while the PowerBuilder application was still trying to communicate with it. Automation Timeout powerbuilder application execution error r0035
. This usually indicates that the application successfully located the external object (such as an OLE or ActiveX control) but failed to execute a specific function within it. SAP Community Common Causes Unregistered Components
If the error occurs during a long-running OLE operation, you can increase the timeout period using the SetAutomationTimeout function.
, such as an OLE server (e.g., Excel, Word) or a COM control. The error message typically reads: : The application was compiled in one version
In PowerBuilder (a legacy enterprise RAD tool from Sybase/SAP), R0035 is a fatal runtime error: "Application terminated." It typically fires when the PowerBuilder Virtual Machine hits a critical, unrecoverable state, such as:
If an application is compiled as a 32-bit executable and deployed to a 64-bit Windows Server, it may look for database connection settings or registry endpoints under the Wow6432Node , failing if the component is registered only in the 64-bit environment.
Since R0035 is a runtime error that crashes the application, you should wrap your external function calls in a TRY-CATCH block to handle the error gracefully and get more info. If the client machine has a different version
Look for an level entry at the exact timestamp of the crash.
Examine your local system error log or review user-submitted crash reports. Pinpoint the exact object and event line throwing the exception. The structure of the error usually points directly to the failing method:
means the bridge between PowerBuilder and the outside world is broken. 90% of the time, it is a registration issue (OCX not registered) or a Name Typo (Case sensitivity in the function name).