on 11-04-2015 10:54 AM
First, let's start with some basic information. We use PowerBuilder 12.5 (Classic) (build 5703) on our workstations with Windows 7. Our application runs great, no harm there.
We use a Windows 2012R2 server for our remote work, whenever we are not at the office, and our application crashes when we close a specific window. Only on that window. Closing other windows with the same technique (CloseWithReturn) works like you would expect.
Attached you will find a screenshot of the difference in pbdebug file (*.dbg) where the error occurred. On the left, the one form our workstation, thus working correct. On the right, the one from the remote server.
Also attached you see the error form the Windows event log and our setup for the remote server roles.
Hope you guys can help/point me in the right direction to fix this issue.
Hi Erik;
Have you tried ....
1) Full optimize on all your application's PBL's?
2) Restart PB IDE
3) Full build of your application's objects?
4) The redeploy your .EXE
Regards ... Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The reason I ask about the PBL optimization is that the PB IDE does not delete classes in the PBL's but can create a new entry and leave the old class intact but marked for space reclamation. Sometimes, the IDE can pick an old marked for deletion copy of a compiled class when creating the EXE / PBD's. The optimization process ensures that this scenario does not happen.
So now ... the issue becomes just that one window. I would now look at the following ...
1) Its ancestry & their behaviours
2) Any special User Events mapped & their processing
3) Review the code in the Close & CloseQuery events carefully.
Suggestion: Comment out all the code in this Window and see if it closes OK. Then start uncommenting the code until it fails. A bit of a PIA though, I must admit.
HTH
Hi Erik,
In the link it says:
Fault Module Name: pbdwe125.dll
If this crash location is correct then it crashes in the datawindow engine.
Do you perhaps have a heavy datawindow on it or have a datawindow is still shared or have ole object in it?
Maybe you can set the datawindow object to empty string or give it a bit more time with some yields.
Set the Use Hwnd is no in the ini.
The two traces in the other link don't seem to quite match either.
Ben
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ben;
That is a good observation. This is always the way I end my Close of a Window class with DC/DS's involved ...
1) DC/DS.Reset ( )
2) DC/DS.DataObject = ""
3) Destroy DS // no need for DC
FWIW: The above code cleans up the DWO's buffers first and then forces the DWO to be unloaded completely before the control is destroyed. This creates an orderly shutdown of the DW processing instead of trying to let the PBVM/DWE handle it all in one destroy command.
HTH
Regards ... Chris
A couple of questions:
1. Does it work on a Windows 8 PC?
2. If you the the application on the console of the Server not through RDP (Using VNC or something) does it still crash?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.