Menu Close

Powerbuilder Application Execution Error R0035 ((free))

Powerbuilder Application Execution Error R0035 ((free))

Here’s a comprehensive review of the PowerBuilder Application Execution Error R0035, including what it means, common causes, symptoms, and step-by-step troubleshooting solutions.

Step-by-Step Troubleshooting

How to diagnose (step-by-step)

  1. Note the exact module name in the error dialog (if shown).
  2. Check application folder and deployment package for that module.
  3. Use Dependency Walker (depends.exe) or Dependencies (modern fork) on the app EXE and on the named DLL to find missing transitive dependencies.
  4. Verify 32-bit vs 64-bit: ensure app and DLL bitness match.
  5. Temporarily disable antivirus or check quarantine logs to ensure DLL not blocked.
  6. Check Windows Event Viewer (Application/System) for related errors.
  7. If module is an OCX/DLL COM component, confirm it is registered:
    • regsvr32 "path\component.dll" (run elevated for system directories).
  8. Search for referenced modules in PATH and current working directory. Use Process Monitor (ProcMon) to trace file-not-found attempts.
  9. If module is in GAC or system folder, ensure correct installation of runtime frameworks (e.g., MSVC runtime, .NET, PowerBuilder Runtime Packager components).

Common Causes

  1. Missing or corrupted PBR file – The compiled executable expects a specific PBR file (PowerBuilder Resource file) containing bitmap, icon, or other resource references.
  2. Incorrect file path – The PBR file is not in the expected directory or the path is hardcoded incorrectly.
  3. Deployment issue – The PBR file was not included when deploying the application.
  4. Runtime DLL mismatch – Incompatible versions of PowerBuilder runtime DLLs (e.g., pbrtcrt*.dll, pbvm*.dll).
  5. Registry corruption – Missing or invalid registry entries for PowerBuilder runtime.
  6. File permissions – The application or user does not have read access to the PBR file or its directory.
  7. Antivirus/security software – Blocking or quarantining the PBR file.

References & Further Reading

  • Appeon (now part of SAP) Official PowerBuilder Documentation – Deploying Applications and Components
  • Microsoft Sysinternals – Process Monitor v3.89
  • PowerBuilder Developer’s Journal: “Diagnosing Runtime Library Errors”
  • Community thread: “R0035 – The Silent Killer of PB Deployments” (Sybase/PB Forums)

Last updated: October 2025. Applies to PowerBuilder versions 9.0 through 2022.

That is an interesting error message to see in a paper title! It immediately sounds like a postmortem or a forensic case study, rather than a traditional research paper.

While I cannot browse live links to find the exact paper you are referencing (if it is pre-print or in a specific journal), I can infer exactly what kind of "interesting paper" this would be based on the error code PowerBuilder R0035.

Here is the likely premise of that paper:

The Core Error: R0035 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:

  • A stack overflow due to infinite recursion.
  • Memory corruption or illegal memory access (often from a misbehaving external DLL).
  • Missing or invalid PBD (dynamic library) that the main executable absolutely requires.

What makes the paper "interesting"? An academic or engineering paper focused on this error would likely cover one of three fascinating scenarios: powerbuilder application execution error r0035

  1. The Migration Nightmare (Legacy Systems)
    • Context: A large bank, insurance firm, or hospital trying to move a PB 9/10 application to Windows 10/11 or a 64-bit environment.
    • Finding: R0035 suddenly appears because old PBDs were inadvertently compiled with different byte-ordering or memory models. The paper would detail a heuristic for finding the exact bad library without source code.
  2. The Anti-Debugging Trick (Malware Analysis)
    • Context: Attackers used a PowerBuilder wrapper to evade EDR (Endpoint Detection). R0035 is triggered intentionally when a debugger is attached, causing the process to self-terminate.
    • Finding: The paper describes how to bypass this by hooking the PBVM (PowerBuilder Virtual Machine) DLL entry points.
  3. The Forensic Artifact (Data Recovery)
    • Context: A corrupt PowerBuilder executable threw R0035, but the database connection parameters and last executed SQL query were still in memory.
    • Finding: The paper demonstrates a memory forensics technique (Volatility) to extract the connection string and uncommitted transactions from the crash dump, bypassing the broken GUI.

If you are looking for that specific paper:

It may be a whitepaper from Appeon (who now owns PowerBuilder) or a technical note from a maintenance company like WPC Software.

To find it exactly, you would search:

  • "PowerBuilder runtime error R0035" case study
  • "R0035" forensic analysis (in quotes)
  • Google Scholar: powerbuilder "r0035"

Could you provide a source or an author name? If you tell me where you saw it (e.g., ACM Digital Library, arXiv, a specific conference like ICSOFT), I can help you find the exact PDF or tell you its specific thesis.

PowerBuilder Application Execution Error (R0035) typically occurs when an application fails to call or execute a function on an external object , such as an OLE control, a COM object, or a DLL Appeon Community Core Cause

The error indicates that the PowerBuilder runtime cannot find or communicate with a specific method or property of an external object. This is often due to: Appeon Community Unregistered Components Note the exact module name in the error dialog (if shown)

file required by the OLE object is not registered on the target machine. Missing Dependencies

: A required system file or third-party library is missing from the application path or system folders. Mismatched Versions

: Upgrading components (like Crystal Reports or Office) without updating the calling code or runtime environment. NULL References

: Attempting to call a function on an object that failed to initialize (e.g., ConnectToNewObject returned an error code but the script continued). SAP Community Common Fixes Register the Control : Manually register the failing component using for OCX/DLL files or for .NET COM DLLs. regsvr32 "C:\Path\To\YourControl.ocx" Verify Registry

: Check that the COM object class (CLSID) exists in the Windows Registry on the machine where the error occurs. Check Return Codes

: Ensure your code validates the connection before calling functions. powerbuilder If your app is 32-bit

OLEObject lole_ext lole_ext = CREATE OLEObject li_rc = lole_ext.ConnectToNewObject("Your.Object") IF li_rc < 0 THEN MessageBox("Error", "Connection failed with code: " + String(li_rc)) RETURN END IF // Only then call the function lole_ext.ExternalFunction() Use code with caution. Copied to clipboard Standardize Environment

: Ensure the target machine has the same bitness (32-bit vs. 64-bit) and runtime versions as the development environment. SAP Community If you'd like to troubleshoot a specific instance: external object are you calling (e.g., Excel, Outlook, a custom DLL)? line of code function name triggers the error? PowerBuilder Application Execution Error R0035!

PowerBuilder Application Execution Error R0035 is a runtime exception typically described as an " Error calling external object function

". It occurs when a PowerBuilder application fails to execute a method or access a property on an external component, most commonly an OLE (Object Linking and Embedding) Experts Exchange Primary Causes Missing or Unregistered Components

file required by the application is not present on the machine or has not been registered in the Windows Registry. Version Mismatch

: Conflicts between 32-bit and 64-bit architectures, or incompatible versions of third-party software like Microsoft Office (e.g., Outlook or Word integration). OLE Automation Timeouts

: The external server (like Excel or a custom COM server) takes too long to respond, causing the request to time out. Invalid Object References : Attempting to call a function on an that has not been successfully connected using ConnectToNewObject ConnectToObject SAP Community Recommended Solutions PowerBuilder Application Execution Error R0035!

Windows 10/11 with Controlled Folder Access

  • Issue: Windows Ransomware Protection can block PowerBuilder from reading PBDs in Documents or Downloads.
  • Fix: Add the application EXE to the allowed list under Windows Security → Virus & threat protection → Ransomware protection → Allow an app.

Step 5: Check 32-bit vs 64-bit Compatibility

  • If your app is 32-bit, you must use 32-bit runtime DLLs.
  • On 64-bit Windows, 32-bit runtimes are typically in C:\Windows\SysWOW64, not System32.

Run dumpbin /headers pbvmXXX.dll or check file properties to confirm bitness.

Citrix / Terminal Services (RDS)

  • Issue: Multiple users accessing same PBDs. File locking can cause R0035 if a PBD is locked during an update.
  • Fix: Deploy PBDs to a per-user read-only cache (e.g., %APPDATA%\AppName\Cache\) instead of a shared network folder.