This just started today after I restarted my media box. Running this on a domain user (not admin) account in Win 11.
Any ideas what could be going on?
I found these threads from Ember on hitting this and it was caused by a process leaking heap space.
https://github.com/emberjs/ember.js/issues/16503
https://blog.emberjs.com/the-emberjs-times-issue-44/
@Russ figured it out. Had a GPO that set the execution policy for the local machine. I had the computer added by name in the GPO. Looked at the GPO, and since I had to remove and re-add the "new" computer with the same name to the domain, it was showing the old entry in the GPO. Added the "new" computer name and it applied the correct execution policy to the local machine.
I didn't notice at first as I was using VS Code which just allowed the script to run.
However, I did fix it to make sure that even if the execution policy is set to restricted, it will still run. I used this command in TriggerCMD to get it to work.
powershell -executionpolicy bypass -file "C:\Users\MYUSER\Documents\TriggerCMDScripts\StartWork.ps1"
Thanks a ton for pointing me in the right direction. I appreciate all your help as always. Keep on being awesome.
This is the command Im using which has been working for years until I reformatted my machine:
powershell "C:\Users\MYUSER\Documents\TriggerCMDScripts\StartWork.ps1"
I checked the debug.log and I dont see any timestamps in there and when I click on the scripts, its not logging anything. Its like the button is doing nothing. I deleted the debug.log file and when it recreated, it didnt log anything other than the app starting and me opening the GUI editor.
Running the newest agent 1.0.46.
Hey @Russ! Long time!
Reformatted my HD, reinstalled Windows 10, then installed triggercmd and reconnected it as the same machine. I copied over the .triggercmd folder and all the scripts to the new environment. Everything comes up in the GUI properly. When I try to kick off a PowerShell command, it doesnt run. Nothing happens at all. No error. When I run the script outside triggercmd, it works without issue. The only thing in the script is a couple of Start-Process and Stop-Process commands.
When I look at the history of the command, it shows error 1.
I'm a full admin. Not sure why it's failing me when when it worked perfectly until now.
Anywhere that I can check logs to see what may be going on? Any ideas on what could be happening?
This just started today after I restarted my media box. Running this on a domain user (not admin) account in Win 11.
Any ideas what could be going on?
I found these threads from Ember on hitting this and it was caused by a process leaking heap space.
https://github.com/emberjs/ember.js/issues/16503
https://blog.emberjs.com/the-emberjs-times-issue-44/
@Russ Wil do! I haven't seen the issue with the UI since the latest Win 11 update. May have been an issue with an earlier build.
@Russ If you need any testing done, let me know. I have a couple VMs setup with Win11 and a bare bones PC that I just picked up with it on there that I can use. Happy to help.
Keep up the awesome work bud!
Hey there!
Did some testing on Windows 11 and there are a few issues.
When I try to run the agent "as administrator" from the Start menu, I get a JS error in the main process. "TypeError: Path must be a string"
Starts fine as the logged in local user. Starts fine when logged in as a user with admin permissions.
There are some weird glitches with the GUI editor. Sometimes the window will freeze, sometime it thinks the mouse is 1 command below where it is. Seems like the mapping is off. Have to quit and restart to fix it. It doesn't like it when you switch to a different window and come back to it.
I've looked into this one before. TriggerCMD aside, I don't even think there is a way to do it from the command line.
So it looks like it is kinda working. The issue now is that when I run the batch file manually as an admin, it works fine. If I run it using a foreground command, it only runs the first command and then sits there. Not sure why it wont progress to open all the programs. Is it running the commands as an admin?
"C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE"
start %localappdata%\Microsoft\Teams\Update.exe --processStart "Teams.exe"
"C:\Users\kadamson\AppData\Local\GoToMeeting\19228\g2mstart.exe"
"C:\Program Files (x86)\Auto Mouse Mover\AutoMouseMover.exe" :silent
That is the entire script. Stored in my local user documents folder.
@Russ Installer worked to reinstall the agent but the agent still fails to run the commands. I believe I ran the installer by right-clicking -> Run as Admin. I usually do that when installing any program as a CYA anyways.
The post above was on what I am seeing in the developer console in the GUI when I attempt to run my StartWork,bat script. All the script does is opens Outlook and Teams. Doesn't matter if I run it from the GUI, through Alexa, or from the website, it does not run on the local machine.
The other post was me hitting the same thing as the other user when trying to troubleshoot the commands not working issue.
This all started happening after updating Win10 to 20H2.