My company wants to start using managed laptops (InTune) (Windows 10)
I've had to change the login procedure of my applications to no longer use trustedconnections as those laptops are no longer in the local AD of the databases.
I'm having an issue with my applications just stopping.
I've regenerated, optimized, exported/imported I've even changed PB versions from 2019 to 2021 to 2022 but I'm always having this issue of the application stopping at a certain point on the InTune laptop and working as it should on our normal laptop.
The EXE, ini, xml and PB runtime files on both laptops are identical.
In debug PowerBuilder IDE (2019 R3 2703 same as the application, fresh install on both laptops) crashes on the InTune laptop when I reach the point where the application stops (simply setting a dataobject on a datastore)
In the PBDEBUG log there are some minor version differences in the windows system DLLs and order of when they load, the normal laptop seems to load more but the InTune is also loading some things that the other one doesn't like ATL100.dll the application starts and runs exactly the same until one stops still in the open event of the application (after a database login) and on the other laptop it just goes on.
This is a smallish application 4 pbl no PFC
In the PBDEBUG compare screenshots the InTune is on the left red is what the InTune loads extra (green on the right is what the other laptop loads extra)
Not really sure what I'm expecting here, seems like a very specific situation, maybe someone has the golden tip for some other test I can do as I'm really running out of ideas. And I do have other larger PFC application that need to get this change too.
I've tried newer PB versions with similar results (the crash points are sometimes different)
I think I've found it, it seems to be linked to calling windows DLL GetUserNameExA in SECUR32.DLL when I call it things don't immediately go wrong but eventually I'll get a crash in the next few lines or at least at the close of the application in debug it will crash and take the PB IDE with it (which points to something not being 100% in memory)