Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
We've run into a problem using PG9 on a system with both PB 12.1 and 12.6 installed. At some point in a PB 12.6-based build using pwrgn126.exe, we get a GPF and our build aborts with a <bignum> error code. Usually when this happens we get some message about an access exception (0xC0000005) in MSVCR100. The only workaround we have found reliable is to uninstall the version of Powerbuilder we don't want to build with for the given run.
The system is Windows Server 2012 R2 Standard. PG version is 9.0.0.24, PB 12.1 version is 12.6 Build 4081. The 12.1 version is 12.1 Build 6807.
We've also had endless problems with SySAM on this system.
The build attempts start normally but fail at some point between the Phase 1 initial object load to phase 3 object regeneration.
At build start, we delete all the PBLs and use Synchronize load with the PBG option to reduce the overall run time (17 separate projects are being built; most rely on a set of core PBLs that should only need to be loaded/compiled once). The failure occurs in the first, largest project.
Do you all know about any particular compatibility issues we should look for? Do we need to have a a particular version of the MS VC runtimes installed?
Last edited by DaveE (2016-05-02 14:22:07)
Offline
This message was answered by email:
Can you send an output log (powergen.log, by default) for a failed build? Is the problem repeatable? Did this start happening when a particular component (Windows OS, PB, or PowerGen) version changed?
Subsequently, the customer said he would get to back to this after other work was completed.
We'll post any follow-up here.
Regards,
Phil
Offline