Many legacy PowerBuilder applications automate Microsoft Office applications (Word, Excel). This integration is a common source of r0035. For example, one user encountered the error when their system attempted to generate a letter in Word, with the error referencing a function initregistration . This is often caused by missing Office installations or misconfigured OLE automation.
: Missing required parameters in the function call or the application lacks the permissions to invoke the external service. SAP Community 2. Immediate Solutions Register the Component : Open a Command Prompt as Administrator and use to manually register the required files. For example: regsvr32.exe "C:\path\to\your\control.ocx" Check for Missing Prerequisites : Ensure dependencies like the Microsoft Visual C++ Redistributables
Yes, antivirus programs can block or interfere with PowerBuilder's attempts to load external DLLs or create OLE objects. Temporarily disable your antivirus to test, and if the error resolves, add your application's directory to the antivirus exclusion list.
If an external function (e.g., Function Long MyFunc() Library "mydll.dll" ) is called, but mydll.dll is missing, in the wrong directory, or requires another DLL that is missing, the application will fail with R0035. 3. Bit-Depth Incompatibility (32-bit vs. 64-bit) powerbuilder application execution error r0035
// In the Global External Functions or in a function's Local External Functions: Function long GetDecryptedFile(ref string content) Library "MyCustomLibrary.dll"
A 32-bit PowerBuilder application cannot call a 64-bit OLE object, and vice versa. This is a frequent issue when migrating older applications to 64-bit environments.
: The application is trying to call a 16-bit DLL from a 32-bit application, or there is a mismatch between 32-bit and 64-bit environments. Incorrect Function Signature This is often caused by missing Office installations
Use process monitoring tools like Process Monitor (ProcMon) from Microsoft Sysinternals. Filter by your application's process name and look for "NAME NOT FOUND" or "PATH NOT FOUND" errors around the time your application crashes.
I can provide more targeted code examples or configuration steps based on your setup. Share public link
What (e.g., 2019, 2022, 2025) are you using? Immediate Solutions Register the Component : Open a
If the application crashes on a specific user workstation but works on a development machine, DEP might be blocking the runtime execution.
Deploy the freshly generated files to the target environment. 5. Confirm Bit Architecture (32-bit vs. 64-bit)
Here is a comprehensive guide to troubleshooting and resolving R0035.
PowerBuilder remains a reliable framework for building data-driven enterprise applications. However, migrating legacy code or deploying apps to modern Windows environments can surface runtime errors. One such disruptive issue is the .