Powerbuilder Application Execution Error R0035

This is the most common cause for applications migrated from older versions of PowerBuilder (such as PB 6.5 or PB 9) to modern Windows environments (Windows 10/11 or Windows Server 2016+).

A: Frequently. Citrix environments often have restrictive file system redirection. Ensure the runtime DLLs are copied to each session host locally, not on a network drive.

: Upgrading the application (e.g., moving to a newer Crystal Reports version) without updating the corresponding runtime objects. Recommended Fixes powerbuilder application execution error r0035

To effectively troubleshoot, one must understand the mechanics behind the error. Here are the primary scenarios that trigger R0035.

Without these, the operating system literally does not know how to "run" your PowerBuilder executable. This is the most common cause for applications

: Ensure all required runtime files, such as pbshr.dll , are in the application path or the PowerBuilder Runtime directory.

: The external object relies on other system files (e.g., Visual C++ Redistributables) that are missing from the environment. Ensure the runtime DLLs are copied to each

A: No. It almost always points to a missing or blocked runtime DLL, not your compiled application logic.

. This occurs when the application attempts to access a function or property of an external component—such as an OLE object, ActiveX control, or DLL—that is either missing, unregistered, or incompatible with the current environment. SAP Community Common Causes Unregistered External Controls: The most frequent cause is a required

Write a small bootstrapper (in C# or batch script) that checks for pbvm*.dll before launching the main PB executable. Example batch script:

PowerBuilder Runtime / Deployed Application Error Code: R0035 Full Error Message: Application execution error (R0035)