Error launching 11.1.4.0 BETA from the command line

FYI got your error log. We are looking into it.

Regards,

Wow, the issue has been resolved. It was a very strange one to solve but we found it. The next beta will have the fix.

Thank you for reporting the issue.

Best regards,

Just wanted to follow up - updated to 11.1.6.0 and the issue is resolved for me. Thanks for resolving it so quickly - good work!!

Good morning. I wanted to follow up on an issue that I've been having (since the update to RDM mentioned in this thread).
Basically, in the mornings, my system launches RDM (command line) via a PowerShell script at login time. The PS script runs (via the Windows startup group) so I don’t have to launch a bunch of programs every morning (and I can launch the script manually, if needed). Prior to the RDM update from this thread, the script would run and at the end of it, the script window would close and the programs it launched would remain open (up and running). Since the RDM update (which resolved a RDM command-line issue), RDM launches (as expected), connects to the SQL data source and establishes the desired RDP session. However, the PS script window remains open and shows the following:





If I CTRL-C to exit the PS window, RDM closes (no matter what state RDM is in, RDP session established, sitting idle, etc.). If I leave the PS window open and exit RDM, the PS script window closes. If I launch RDM (within a data source or command line) via the startup PS script, this behavior doesn’t occur (the PS window closes and RDM remaining up and running). I’ve found that launching the PS script manually, the issue doesn’t occur.
If I manually run the following (from an admin PS window), I get the same results (but have to press ENTER to clear the PS window (but it doesn’t force RDM to close):
If (-Not (Get-Process RemoteDesktopManager* -ErrorAction SilentlyContinue))
{
"RDM (64-bit) not running"
$argList = " /DataSource: (removed) /Session: (removed)"
Start-Process "C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe" -argumentlist $argList -WindowStyle maximized
}
I’m guessing something changed to resolve the command-line issue that was originally mentioned in this thread. Might any of those changes have caused this behavior to occur? Is this something that can be easily resolved, it is possibly a PS issue and not an RDM issue or is it something that is just going to happen because of the changes made?
BTW – I’ll forward the entire script to you (if you want), just send me a private message for me to respond to.

Thanks