search

tig / mcec

Robust remote control of Windows PCs over the network.
https://tig.github.io/mcec/
MIT License
80 stars 13 forks source link

The .commands file is getting corrupted #24

Open jonathanrissler opened 2 years ago

jonathanrissler commented 2 years ago

Describe the bug

We use only the "shutdown"-command in MCE Controller. After a period of time, MCE Controller won't load the commands correctly, so "shutdown" is no longer enabled and therefore the PC won't shut down.

To Reproduce

We haven't found a way yet to reproduce the error, but think it may be related to power failure.

Expected behavior

We expected MCE Controller to shut the PC down, as it always had done. We use the tool on 50 PCs, and have the problem only on 5 devices. The error started occuring after 2 months.

Screenshots

MCE_Controller_Fehlermeldung

Version Information

MCE Controller v2.2.7.67 - OS: Microsoft Windows NT 10.0.17763.0 on x64 - .NET: 4.0.30319.42000

Snippets from the log

Paste Logs here.
[MCEControl_6206-PC-01.log](https://github.com/tig/mcec/files/7863260/MCEControl_6206-PC-01.log)

Desktop (please complete the following information): Microsoft Windows 10 Pro
Version 10.0.17763 Build 17763

Additional context Add any other context about the problem here.

tig commented 2 years ago

Hello.

The log screenshot you shared does not match the contents of the .log file you linked to. In the .log file I don't see this error happening. To help me debug this, can you get me a .log file that shows the operations before and after the shutdown where the .commands file was lost/corrupted?

tig commented 2 years ago

Also, is there something about your network connection which is preventing MCE Controller from checking for new versions?

2022-01-11 13:31:26,267 DEBUG - Checking for new release...
2022-01-11 13:31:26,269 DEBUG - (https://github.com/tig/mcec/releases) Fehler beim Senden der Anforderung.
2022-01-11 13:31:26,275 INFO  - You are are running a MORE recent version than can be found at tig.github.io/mcec (0.0)

I don't think this could be related, but I'd like to ensure I don't have a bug in the update code. Thanks.

jonathanrissler commented 2 years ago

Hello,

that's right, sorry. I made the screenshot in November, on a different device than the one I took the .log-file from. And also right, the-log-file doesn't show the error. It starts in January, I don't know why that is.

There are no more operations to see before the error occurs. Everytime it happens (all in all 15 times by now) it's right after the start, where it says in the log "Error parsing .commands XML. Das Stammelement ist nicht vorhanden. (The trunk element does not exist.)"

Regarding your other question: Our PCs do not have internet connection and are supposed not to have. We downloaded the most recent version.

Thanks for your quick reply!

tig commented 2 years ago

Can you please share a full .log file from one of the PCs where the error has occured?

tig commented 2 years ago

Also, in the screenshot it appears you edited the .commands file and saved it manually. Is that correct?

tig commented 2 years ago

One more request:

Next time this happens, please check to see if C:\Users\kiosk\AppData\Roaming\Kindel Systems\MCE Controller\MCEControl.commands exists.

If it does, please send me a copy.

If it does not, please let me know.

jonathanrissler commented 2 years ago

Yes, I will send you a .log file of one of the error-PCs. Unfortunately, I can only access them on Tuesdays, since they are part of a running installation.

No, I didn't save the .commands file manually.

Yes, next time I will check if the .commands file exists, it really seems like it either doesn't exist and is newly created or it is corrupt and therefore "lost" the one defined command.

tig commented 2 years ago

I've been travelling so have not been able to check in on this. I'm now in a more stable location and have time today. If you can get met the logs and other info, I should be able to focus on helping fix this! Let me kow.

jonathanrissler commented 2 years ago

Hi, no problem! MCEControl.log

I'm sorry, but again, there is nohing to see in the logs - they seem to "restart" after the error occurs, and so now when I checked, they didn't pass back until the time of the error (last November). You can see it only on the screenshot I put in the first description. If you need anything more, please let me know. Thanks.

jonathanrissler commented 2 years ago

Hi! So now I've managed to catch two PCs in the act of the error. I collected all logs and error messages. Hope this helps!

MCE_error_1_6006 MCE_error_2_6006

jonathanrissler commented 2 years ago

MCEControl_6126.log MCEControl_6006.log

I copied the complete MCE-folder, if you also need the .commands and -settings files. I can't paste them here but can send you a link or mail. Let me know. Thank You!

tig commented 2 years ago

MCEControl_6126.log MCEControl_6006.log

I copied the complete MCE-folder, if you also need the .commands and -settings files. I can't paste them here but can send you a link or mail. Let me know. Thank You!

These two log files appear to be from Sept 2021. Did you capture any log files from around Feb 01 when the screen shots above were taken?

jonathanrissler commented 2 years ago

You're right, I didn't check on this, because I captured them just on Tuesday, when I took the screenshots. I checked on the other log files from PCs withour the error, and they all date back to August/September 2021, although I captured them just this year. Seems like the log isn't written over the entire period?

tig commented 2 years ago

This is really concerning. I can't understand how recent logs are not being written.

Can you please exit and restart MCE controller on one of the machines that is working ok and then send me

1) the latest .log file 2) a screen shot of the directory the .log, .settings, and .commands files are in

tig commented 2 years ago

In addition to doing the above, please:

1) Update all your machines to the new release: v2.2.8 (https://github.com/tig/mcec/releases/tag/v2.2.8.63) 2) In Settings, change the logging threshold to "ALL"

image

This new release has better logging and I tweaked some things that MIGHT fix this problem.

However, without full logs, I can't know for certain why the .commands file is getting written as empty.

jonathanrissler commented 2 years ago

OK, I can do that tomorrow.

jonathanrissler commented 2 years ago

MCEControl.log

The log file from one of the working machines - it just dates back to January 17.

directory

And the screenshot from the directory. It starts with C:\Users\kiosk

jonathanrissler commented 2 years ago

I updated MCE Controller on some of the machines an tested several times. Using another strategy, I wrote a batch file that always copies the correct .commands file to the right directory when the PC boots. Both seems to work, but if it will for a long period of time, we can only observe. I will keep you informed, thanks for the Update!

tig commented 2 years ago

MCEControl.log

The log file from one of the working machines - it just dates back to January 17.

directory

And the screenshot from the directory. It starts with C:\Users\kiosk

Thanks. FWIW, the MCEControl.log.n files are previous logs. At 100k file size, the logger starts a new file, saving the previous as MCEControl.log.n.

Please send me ALL files in that directory. Thanks.

jonathanrissler commented 2 years ago

Ok. As usual, I can give you these files next Tuesday.