This article provides a comprehensive overview of the R0035 error, its common causes, and actionable steps to resolve it. What is PowerBuilder Error R0035?
Never assume the user has PowerBuilder installed. Deploy the official PowerBuilder runtime merge modules or the standalone PB Runtime Pack (e.g., PB105_RuntimePack.msi ).
Copy the application EXE and all required PBD/DLL files into a single folder on a clean test machine. If it works, the issue is environmental.
A corrupted or unregistered DLL or ActiveX control is a common cause. PowerBuilder cannot call functions from a component that the operating system does not recognize. powerbuilder application execution error r0035
Is the error happening on a or a client workstation ? Share public link
Understanding and Fixing PowerBuilder Application Execution Error R0035
If the error occurs during an API call or integration with a third-party tool, verify your local external function declarations. This article provides a comprehensive overview of the
The full error message typically reads: PowerBuilder Application Execution Error (R0035): Error calling external object function [function_name] at line [line_number] in [event/function] of object [object_name].
This error can appear in version (from PB 6.5 to PB 2022), but the DLL filename varies:
If the external object's software was updated on the client machine, its public interface (API) might have changed. If a function signature was modified, renamed, or deprecated in the new version, PowerBuilder will look for the old method definition, fail to find it, and trigger the runtime error. 4. Invalid or Incompatible Arguments Deploy the official PowerBuilder runtime merge modules or
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.
PowerBuilder allows compilation in both 32-bit and 64-bit formats. Mixing these up will trigger execution errors.
