Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASG Crashes after you add a second session
#1
Hello, 
i have the latest "Free" versions, trying to test before i buy.. I have installed the "free" license. 
using only one session is fine, the second i try to go to a second console, it crashes.. ( or double click to access ) another system?   v 12.0.6504.1
What is wrong here? Why does it crash each time.. 
I have imported from AD around 20 to 30 systems no issue, just when i try to connect to more than one.. 
this is a BIG issue for me. i need to have more than once system open and one time,, maybe like 6 to 10 systems open???
Thank you, 
Jeff W.
Reply
#2
Hi,

do you use x86 or x64 version? Which connection protocol do you use? Is there any error log or just an application crash?

Normally it should be no problem to open 10 connections at the same time - so I just wondering what causes these crashes on the second connection?!?
Regards/Gruss
Oliver
Reply
#3
First,, how do i check which version. i would think it would match the OS version so x64.. i am using RDP to connect to my wks / servers.. all windows devices. i just turned on the log files, found those. so next time it crashes i'll include that. but yes as soon as i open two wks.. it crashes evertime???
Reply
#4
You can see in TaskManager if your process runs in 32 or 64bit mode…

I never heard that it always cashes with the second connection - and there are thousands of people who are working with this tool

Crash without any error? App crash, only eror message within app? A screenshot could be helpful also...
Regards/Gruss
Oliver
Reply
#5
(09-01-2020, 04:48 PM)DevOma Wrote: You can see in TaskManager if your process runs in 32 or 64bit mode…

I never heard that it always cashes with the second connection - and there are thousands of people who are working with this tool

Crash without any error? App crash, only eror message within app? A screenshot could be helpful also...
I'm using the 32 bit Version and have the same problem. I'm running Version 12.0.6504.1 and it started when I upgraded from Win 10 Insider Build 19041 to 19536 and its still happening on build 19541.

This is what I see in the eventviewer:

Faulting application name: ASGRD.exe, version: 12.0.6504.1, time stamp: 0x5daf87f6
Faulting module name: mstscax.dll, version: 10.0.19541.1000, time stamp: 0xe5608cfd
Exception code: 0xc0000409
Fault offset: 0x0017505d
Faulting process id: 0x38bc
Faulting application start time: 0x01d5c7877a3a9897
Faulting application path: C:\Program Files (x86)\ASG-Remote Desktop 2019\ASGRD.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: 8bdcb1d3-c84c-4d29-aaaf-2b48735280d2
Faulting package full name:
Faulting package-relative application ID:
Reply
#6
Ok, that should be a problem of the insider preview build - on my workstation the last insider builds couldn't even install correctly, always reverting to last version - so I wait for a new install on my machine - but this seems not the first timne that in a preview version there are components that are not working correctly
Regards/Gruss
Oliver
Reply
#7
(10-01-2020, 10:05 AM)DevOma Wrote: Ok, that should be a problem of the insider preview build - on my workstation the last insider builds couldn't even install correctly, always reverting to last version - so I wait for a new install on my machine - but this seems not the first timne that in a preview version there are components that are not working correctly

With Insider Build 19551 everything is working as expected.
Reply




Users browsing this thread: 1 Guest(s)