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.
Restarting worked for me as well. Installed successfully and the service launched automatically.
Reinstalled as admin. Service is confirmed running. I clicked the option to install the background agent but I don't see node.js in the installed app list like I see it on all my other machines.
After seeing this in Event Viewer -> Application should there be an additional entry stating that it started successfully?
Starting C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent\app-1.0.25\resources\app\src\service.js
This is what I'm seeing when I try to run a command in the GUI from the developer tools:
C:\triggercmdDev\github\TRIGGERcmd-Agent\process\js\fake_d10b99db.js:197 Running c:\scripts\StartWork.bat
C:\triggercmdDev\github\TRIGGERcmd-Agent\process\js\fake_d10b99db.js:62 Neither add nor edit box visible, so updating file
15C:\triggercmdDev\github\TRIGGERcmd-Agent\process\js\fake_d10b99db.js:197 Running c:\scripts\StartWork.bat
Failed to parse SourceMap: file:///C:/Users/kadamson/AppData/Local/TRIGGERcmdAgent/app-1.0.25/resources/app/app/css/bootstrap.css.map * this one only shows up once.
Still not running the command. Not sure what could be happening. Is there anything that I can grab for you?
@Russ I got the same error after uninstalling and then attempting to reinstall this morning. I'll restart and give it another go. I took a look at the log but I can't copypasta it on there due to length.
Let me paste a couple entries that caught my eye in terms of the failed install:
2020-04-24 09:14:11> Program: Starting Squirrel Updater: --install .
2020-04-24 09:14:11> Program: Starting install, writing to C:\Users\kadamson\AppData\Local\SquirrelTemp
2020-04-24 09:14:11> Program: About to install to: C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent
2020-04-24 09:14:11> Program: Install path C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent already exists, burning it to the ground
2020-04-24 09:14:12> Utility: DeleteDirectory: could not delete - C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent\app-1.0.22\resources\app\src: System.IO.IOException: The process cannot access the file 'C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent\app-1.0.22\resources\app\src' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean throwOnTopLevelDirectoryNotFound, WIN32_FIND_DATA& data)
at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
at Squirrel.Utility.<DeleteDirectory>d__19.MoveNext()
2020-04-24 09:14:13> Utility: DeleteDirectory: could not delete - C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent\app-1.0.22\resources\app: System.IO.IOException: The directory is not empty.
2021-03-05 09:04:01> Program: Starting install, writing to C:\Users\kadamson\AppData\Local\SquirrelTemp
2021-03-05 09:04:01> Program: About to install to: C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent
2021-03-05 09:04:01> Program: Install path C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent already exists, burning it to the ground
2021-03-05 09:04:01> IEnableLogger: Failed to remove existing directory on full install, is the app still running???: System.UnauthorizedAccessException: Access to the path 'C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent\app-1.0.25\resources\app\src\node.exe' is denied.
Win10 64. 20H2. Running as a full admin and also use "Run as admin". AV is Windows Defender.
One question I did have. What is going on with the Discord, Teams, Whatsapp stuff that I'm seeing in the log? What are you doing in these folders?
3912> 2020-03-12 16:59:13> Program: About to install to: C:\Users\kadamson\AppData\Local\Discord why is it installing in the Discord AppData folder?
@Russ If you need anyone to test or reproduce the issue, I'm happy to help. I can provide logs or anything else you need.
Edition Windows 10 Enterprise
Version 20H2
Installed on 2020-10-04
OS build 19042.844
Experience Windows Feature Experience Pack 120.2212.551.0
Do you also test on the newest builds of server 2016 and 2019? Currently working fine on 2019 - 1809 but now I'm terrified to update.
Seems 20H2 broke shit.
Now I can't even get commands to work by clicking on the play button in the UI. Reinstalled as well.
The background service installer doesn't seem to make an entry for Node.js anymore from what I see in Programs and Features so it may not even be installing it anymore.
Hey there @Russ!
Not sure if I'm missing something but I can't seem to find a list of the agent versions and their release dates. Will I get a prompt from the current agent that there is an update available? Do you post anything when you release a new agent at all? Are there any release notes when a new version is released?
@Russ Will do! Nice dig on troubleshooting the issue.
@Russ stopped working again. I think you may need to open a ticket with Amazon and see why their skill stops working randomly.
@Russ Finally got around to giving it a shot. Disabled the skill but when I went to re-enable the skill through amazon.ca, I click Enable -> Allow and I get this error message after it fails:
We were unable to link TRIGGERcmd Smart Home at this time.
Any idea what the issue could be?
EDIT:
I just tried it again and it seems to have worked. Will keep you posted.
EDIT2:
Fix worked. After getting it enabled the voice commands seem to be working again. I'll remember this for troubleshooting in the future since it seems to be non-destructive. Thanks!
Was working fine until the 21st and then all commands from Alexa stopped working to all 3 of my connected devices. History shows the last command run by Alexa Smart Home that was recorded was on the 21st. Has been working fine for months and I haven't changed anything in my environment.
Commands triggered from the GUI work
Commands triggered through the website work.
Only Alexa seems to be the issue.
Any ideas?