A more obscure but possible cause is a corruption in the PowerBuilder Library (PBL) file itself, specifically in the stored binary data for an OLE control on a window or user object. One developer described a situation where a window containing an OLE object would always crash with the R0035 error when opened. They discovered that simply opening the window in the painter, making a trivial change (like adding a blank line), and saving it, had corrupted the OLE definition. The solution was to replace the corrupt binary data in the .srw (source) file from a backup copy, essentially restoring the OLE object to its previous state. This highlights the importance of version control and regular backups of source code.
If the cause is not immediately apparent, use these tools to trace the failure: PowerBuilder Application Execution Error R0035!
// Later in code... if IsNull(lnv_obj) OR NOT IsValid(lnv_obj) then return lnv_obj.SomeFunction() // This would crash if not checked
In PowerBuilder, Application Execution Error R0035 a runtime error that specifically occurs when an error occurs while calling an external object function powerbuilder application execution error r0035
If the DLL or OCX file is missing from the application path, or if the file is corrupted, the application cannot execute the function. 3. Missing 32-bit/64-bit Compatibility
Manually register the external file using the command prompt. Users on the SAP Community suggest navigating to the control's directory and running regsvr32 controlname.vbx or .ocx .
At its core, the R0035 error is PowerBuilder's way of saying it cannot communicate with an external object it has been instructed to use. This could be an OLE Object (like a Microsoft Office application), an ActiveX control, a .NET Assembly exposed as COM, a VBX (Visual Basic eXtension) control, or a function from a standard DLL. A more obscure but possible cause is a
Ensure the folder containing the PowerBuilder runtime DLLs is in the system PATH :
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.
Upgrading legacy client infrastructures using Crystal Reports automation frequently introduces this exception when old RDC engines are replaced. PowerBuilder Application Execution Error R0035! The solution was to replace the corrupt binary data in the
The application expects a specific version of a COM object (e.g., MS Excel 2016), but the client machine has a different version, or the object has changed, causing the method call to fail. 3. Permissions Issues
A less obvious but officially documented cause of the R0035 error is an OLE automation timeout. When PowerBuilder calls a function in an external OLE server (e.g., Microsoft Word or Excel), it waits for a response. The default timeout period for this operation is .
The structural breakdown of an R0035 error centers around execution environment conflicts, dynamic binding failures, and host system discrepancies. 1. Missing or Corrupted DLL/OCX Registration