Author Topic: Dialog Crashing only on terminal server  (Read 106 times)

domvalle@comcast.net

  • Newbie
  • *
  • Posts: 13
Dialog Crashing only on terminal server
« on: October 29, 2019, 01:20:05 pm »
Hi,
I have a dialog that works perfectly on the desktop but on the terminal server has been recently crashing at the very end.
Right after the last dialog line and does not get to the ButtonPushed=Dialog("MyDialog")
No error or message and nothing in the www.batch.ini either.
How can I further troubleshoot as this is affecting our sales force...
thanks!

domvalle@comcast.net

domvalle@comcast.net

  • Newbie
  • *
  • Posts: 13
Re: Dialog Crashing only on terminal server
« Reply #1 on: October 29, 2019, 01:26:08 pm »
...actually exe is still running, dialog never appears.
debug file stops at last line: MyDialog010
here is the dialog that opens an excel file:

MyDialogFormat=`WWWDLGED,6.2`

MyDialogCaption=`%title% CUST:[%filecust% ][%doct%] %tmsg%`
MyDialogX=500
MyDialogY=500
MyDialogWidth=492
MyDialogHeight=340
MyDialogNumControls=010
MyDialogProcedure=`SubdCallbackProc`
MyDialogFont=`DEFAULT`
MyDialogTextColor=`DEFAULT`
MyDialogBackground=`DEFAULT,DEFAULT`
MyDialogConfig=0

MyDialog001=`061,323,064,012,PUSHBUTTON,"PushButton_OK",DEFAULT,"SAVE/CONTINUE",1,10,32,DEFAULT,DEFAULT,"0|255|0"`
MyDialog002=`001,001,486,318,COMCONTROL,"ComControl_1",DEFAULT,"%docx%",DEFAULT,30,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog003=`125,323,036,012,PUSHBUTTON,"PushButton_save",DEFAULT,"SAVE",2,20,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog004=`161,323,042,012,PUSHBUTTON,"customer",DEFAULT,"CUSTOMER",3,20,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog005=`203,323,046,012,PUSHBUTTON,"salesforce",DEFAULT,"SALESFORCE",4,20,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog006=`249,323,038,012,PUSHBUTTON,"date",DEFAULT,"DATE",5,20,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog007=`287,323,044,012,PUSHBUTTON,"pcodes",DEFAULT,"PRICE GUIDE",6,20,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog008=`331,323,038,012,PUSHBUTTON,"clipx",DEFAULT,"CLIP LIST",7,20,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog009=`369,323,052,012,PUSHBUTTON,"dslx",DEFAULT,"DELINQUENT",8,40,DEFAULT,DEFAULT,DEFAULT,DEFAULT`
MyDialog010=`001,319,486,018,GROUPBOX,"GroupBox_1",DEFAULT,"Helper Buttons",DEFAULT,100,DEFAULT,DEFAULT,DEFAULT,DEFAULT`

ButtonPushed=Dialog("MyDialog")

domvalle@comcast.net

  • Newbie
  • *
  • Posts: 13
Re: Dialog Crashing only on terminal server
« Reply #2 on: October 29, 2019, 01:54:06 pm »
Well after all that a server reboot seems to have corrected the issue.
Hmmm...

td

  • Tech Support
  • *****
  • Posts: 3103
    • WinBatch
Re: Dialog Crashing only on terminal server
« Reply #3 on: October 29, 2019, 02:08:45 pm »
Based on your description, your dialog was not "crashing" nor was the script not getting to the 'ButtonPushed=Dialog("MyDialog")' line.  What is more likely the case is that the dialog function is waiting for user-input but none is forthcoming because the dialog is not visible.   The DebugTrace function would not add the Dialog line to the trace file until after line finished and the line would not finish until a user dismissed the dialog in some fashion. 

You seem to be implying that your script did work in when running in RD session but is not now working.  If that is the case, you will need to consider what might have changed on the session host. 
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

domvalle@comcast.net

  • Newbie
  • *
  • Posts: 13
Re: Dialog Crashing only on terminal server
« Reply #4 on: October 31, 2019, 08:31:34 am »
thank you,
yes, a bit of a mystery.
so the screen goes blank in the remote session when this dialog is called for all users on Remote Desktop.
After a reboot it works normally again.
So what could upset the server in this way?

td

  • Tech Support
  • *****
  • Posts: 3103
    • WinBatch
Re: Dialog Crashing only on terminal server
« Reply #5 on: October 31, 2019, 01:58:02 pm »
I have had sessions become detached from the desktop because of buggy router firmware and because of the lock screen (screen saver) kicking in.   However, I have no idea what is causing your particular problem.  You might want to search Microsoft's site (assuming you are using there terminal client and server) for some insite.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

td

  • Tech Support
  • *****
  • Posts: 3103
    • WinBatch
Re: Dialog Crashing only on terminal server
« Reply #6 on: November 01, 2019, 01:41:07 pm »
Here is a link to MSFT's RD troubleshooting page for server 2008.  It's probably still applicable to 2012:

https://support.microsoft.com/en-us/help/2477176/troubleshoot-remote-desktop-disconnected-errors-in-windows-server-2008
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade