PowerBuilder 2021 Build 1311. Windows 10 Enterprise.
My program is running in 64bit mode and the first folder in the path is C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 21.0.0.1311\x64.
This works:
lds_categories.SaveAs(ls_filename, Excel8!, True)
This aborts:
lds_categories.SaveAs(ls_filename, XLSX!, True)
I get two entries in the Event Log:
Application: MyProgram.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at <Module>.TestEnviormentInfo()
Faulting application name: MyProgram.exe, version: 1.0.0.0, time stamp: 0x61fee899
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1466, time stamp: 0xe01c7650
Exception code: 0xe0434352
Fault offset: 0x0000000000034f69
Faulting process id: 0x6110
Faulting application start time: 0x01d81b09bea583d9
Faulting application path: C:\Program Files (x86)\???\MyProgram.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: be2e0cea-46f8-4b6d-8dda-19637a23b76c
Faulting package full name:
Faulting package-relative application ID:
The highlighted lines appear to point to the problem. Interesting that the function name misspells Environment.
Other pertinent info: the EXE is a C++ program that uses PBNI to execute PB code. I know there isn't a 64bit specific version of the PBNI files. This is only the second issue I have run into. The other is the PBNI method that is used to access a PB array from the C++ code.
Anyone have a suggestion?
That makes sense because the .Net 2.0 features like PB Web Service, Excel export to XLSX, etc was dependent on the PB.Net deployment - which of course, was installed with the PB IDE. Now that the .Net 2.0 WS's are deprecated, the PB.net feature is not there unless, you run the PB Packager with PBPack.ini setting to expose the .Net 2.0 runtime feature set. So placing that .Net Assembly with the App EXE or in your case TopWizWeb NVUO location, should allow the XLXS feature to work ok.
Regards ... Chris