8.2.5 Client Crashes when Logging into Remote Server - VisualCron - Forum

Community forum

AHTECH
2017-03-14T18:07:53Z
We have tried logging in using both AD enabled accounts and native accounts. Login works works fine when running client from server. But crashes when running client from a remote system.

3/14/2017 2:07:10 PM Incoming: XMLCommand
3/14/2017 2:07:10 PM In Connect (Remote)
3/14/2017 2:07:10 PM MessageReceivedByServer->(From: 758793a8-adb2-4a3d-8d20-eadf9880e89b) (mc.Id: a8993640-0556-47f5-84e1-2ff570c034f1) : XMLCommand
3/14/2017 2:07:10 PM Server Id: d177ca18-ea3e-4187-8342-c6e2e66ecdaf
3/14/2017 2:07:11 PM Received: 16 Job(s)
AHTECH
2017-03-14T18:11:54Z
Backing the client down to 8.2.4 resolves the remote connection issue. (server remains at 8.2.5)
Support
2017-03-16T18:09:42Z
Did you test using Client AND Server version 8.2.5?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
latkinson
2017-03-17T14:16:20Z
We just installed 8.2.5 last night. I can use the client on the remote server via remote desktop, but when I install the client on my local desktop to try and connect to the remote server, everything is grayed out, and then the app goes *poof* and disappears. No error, nothing to provide any hint.

And I cannot run the server on my local machine due to corporate security policies, so... how do I get a copy of the 8.2.4 install to see if that works?

Thanks,
Luther
2017-03-17T20:45:38Z
Hello,
I encountered the same type of crash on a Windows 10 install for a user. I just installed 8.2.5 Client/Server on my Windows 10 desktop. The program does not crash. I uninstalled 8.2.5 and then reinstalled 8.2.5 as Client Only and now it is working.

Thank You,

Pauly
Support
2017-03-18T12:24:54Z
Please export server settings from File->Export and send to support@visualcron.com
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
AHTECH
2017-03-24T20:31:12Z
Originally Posted by: Support 

Did you test using Client AND Server version 8.2.5?




The desktops were all updated from 8.2.4 to 8.2.5 using the installer with client only option.
We have tried this on 3 separate Windows 7 64bit pc's.
All load the client, opens the main window and flashes away quickly, so does the process.
There is no issue when using the client on the same computer the server is installed on. This issue only occurs on client only installations and possibly only those upgraded from 8.2.4. I can verify this next week.


hetco user
2017-03-25T16:53:59Z
Henrik, as you know I'm seeing the same problem - now even from one VM to another on the same physical machine. I think this is related to some sort of strange timeout issue, as in addition to the client crashing when connecting from London to NY, I can replicate this when connecting to a local (on the same LAN) server that is overloaded.

Also, I've noticed that 8.2.4's installer requires .NET 3.5, and 8.2.5 now requires a higher version of .NET. You really should put these things in your change log. Right now your change logs mention only features you've added, and bug fixes that you've created -- you say little about what else you've changed.

Increasingly I find myself having to backup all settings, roll all our machines forward, and when something breaks, having to roll everything back.
Support
2017-03-27T08:13:38Z
Originally Posted by: hetco user 

Henrik, as you know I'm seeing the same problem - now even from one VM to another on the same physical machine. I think this is related to some sort of strange timeout issue, as in addition to the client crashing when connecting from London to NY, I can replicate this when connecting to a local (on the same LAN) server that is overloaded.

Also, I've noticed that 8.2.4's installer requires .NET 3.5, and 8.2.5 now requires a higher version of .NET. You really should put these things in your change log. Right now your change logs mention only features you've added, and bug fixes that you've created -- you say little about what else you've changed.

Increasingly I find myself having to backup all settings, roll all our machines forward, and when something breaks, having to roll everything back.



8.2.5 still requires .NET 4 as before. 8.2.6 however requires 4.5.2 and will be marked in the change log.

Can you please try to run the VCCommand.exe to see if you get any error? You probably have to add --password and change the server name from "rambo". Let us know how it goes.

objlhnohnhjhhiob.png
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hetco user
2017-03-27T15:39:24Z
Quote:

8.2.5 still requires .NET 4 as before. 8.2.6 however requires 4.5.2 and will be marked in the change log.



Ah ok, it's just that the 8.2.4 installer requires .NET 2 to be installed -- I noticed this when testing VC 8.2.4 on a Windows 10 LTSB N VM.
Support
2017-03-28T08:15:56Z
Is it possible for you to test the VCCommand.exe as supplied before?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2017-04-03T07:39:23Z
The problem has been resolved now. It was related to different time zones on client and server and a calculation went wrong. Please test this build:

http://www.visualcron.co....aspx?g=posts&t=7172 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top