Background: PB 12.1 build 6639 (lots of clients with legacy s/w) against MS SQL Server 2012 R2
Scenario:
* 2 app users
* same group, so same app access rights
* same PC, using same autologin/generic Windows account
* one user occasionally crashes on a null object reference, the other never does
* the user who crashes out of app restarts app, repeats the same crash steps, and does not crash
Any advice on diagnosing the problem is appreciated.
The key point here is that the PB App codes the System Error event to trap & record the error (like a Null Object) so that the PB developer can then go straight to the faulting line of code and resolve the logic error. Which is typically, a pointer that has not been initialized for some reason.
In the worst case, the PB developers can place an IsValid() around the PowerScipt command that is getting the Null Object error in order to recover from the surrounding code that may not be doing its job correctly (ie such as a CREATE at the right time).
HTH
Finally, thanks for the "worst case" suggestion, which I may need to code to get this client by.
Thanks for your help - it's an honor to get advice from you.
Since the error does not reoccur on a typical App restart, my guess would be that another process is doing a "Destroy" on a resource that the later executing PowerScript code is depending on (and thinks that its still there). Have a look at your "Destroy xxxx" commands for that resource that gets the Null Object error.
HTH
Regards ... Chris