Azuredatastudio: 1.14 version does not run under LocalSystem

[genifycom]

• Azure Data Studio Version:

Steps to Reproduce:

1. Version 1.13.1 runs fine under Local System using
   Administrative Command Prompt:
   Run psexec64 -i -s cmd.exe
   In the new "nt authority\system" command promt:
   Run "C:\Program Files\Azure Data Studio\azuredatastudio.exe"

The application starts and runs as normal.

After upgrade to 1.14, when trying this same scenario, the application starts and you can see it in the taskbar, but the UI will not activate.

Tried this on multiple machines now and same result. We have had to back down all 1.14 back to 1.13.1 in order to use Azure Data Studio

[adsbot[bot]]

Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Bump extensions gallery for 1.14 release (#8707)
  

[alanrenmsft]

@genifycom I am not able to reproduce the issue. do you see any error in the command window or in this folder: C:\Windows\System32\config\systemprofile\AppData\Roaming\azuredatastudio\logs?

[adsbot[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity in the last 7 days. If you have more info to help resolve the issue, leave a comment

[genifycom]

So I ran version 1.13.1 under Local System and that ran fine (run from the Command Prompt as "C:\Program Files\Azure Data Studio\azuredatastudio.exe"). Then I upgraded to 1.14.1
I ran the same command.
The command line says
update#setState idle
update#setState checking for updates
Then I get a Dialog saying "The window is no longer responding" Reopen, Keep Waiting, Close

Mouse on the Azure Data Studio Icon shows [Administrator] (unresponsive)

It is definitely a permissions issue. Running from the Task Bar via the icon opens immediately.
So the test is run Administrative Command Prompt. Run psexec64 -i -s cmd.exe
In the new CMD prompt, run "C:\Program Files\Azure Data Studio\azuredatastudio.exe"

I see that Azure Data Studio does eventually open. It is taking several minutes.

Please advise if you can reproduce.

[genifycom]

BTW, I see the log directories. Which file should I be looking at for you (there are several directories and files in there)?

[alanrenmsft]

@genifycom still no repro from our team. and you are saying it eventually worked after several minutes? to help understanding the issue, do you mind zipping up log files and send it to me ([email protected])? also do you see anything error in the Windows event viewer?

[genifycom]

logs.zip

[alanrenmsft]

@abist , Hi Aditya, I will be on vacation, could you please take a look at this one?

[adsbot[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity in the last 7 days. If you have more info to help resolve the issue, leave a comment

[genifycom]

What else do I need to send? I can record video of the behavior or additional logs.

[genifycom]

Here are the timing. After requesting "C:\Program Files\Azure Data Studio\azuredatastudio.exe" in an "nt authority\system" command prompt. I do not touch anything.

Here are the messages shown in the CMD window.
[main 2020-01-23T15:04:20.331Z] update#setState idle
[main 2020-01-23T15:04:50.333Z] update#setState checking for updates
[main 2020-01-23T15:04:50.635Z] update#setState idle

Notice that 30 seconds pass from the first idle to the "checking for updates" happens.
The window opens around 2 minutes after issuing the start program command.

[genifycom]

There are no errors shown in the Event log

[abist]

@genifycom Unfortunately I couldn't repro this issue either. Could you try running the application with the flag --disable-gpu --disable-extensions i.e. "C:\Program Files\Azure Data Studio\azuredatastudio.exe" --disable-gpu --disable-extensions and see if it works? If it doesn't, please run "C:\Program Files\Azure Data Studio\azuredatastudio.exe" --disable-gpu --disable-extensions --verbose and paste the logs here.

[genifycom]

Thank you for that. --disable-gpu allows immediate opening. I suspect LogMeIn is interfering somehow. Have to use LogMeIn since these 30 machines are not on a Corporate network and are standalone.

So now I have a workaround.