CumulusMX as a service, Win10 stopped.
Posted: Sat 05 Sep 2020 12:59 pm
I'm running CMX 3093 on Win10, as a service.
CMS seems to have stopped again this morning for now apparent reason that i can see.
The laptop is still up and running and doesn't sleep, and the other apps are still happily ticking over.
Looking at the windows event log there are two entries for CMX this morning:
first:
- System
- Provider
[ Name] CumulusService
- EventID 0
[ Qualifiers] 0
Level 4
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2020-09-05T06:31:01.285021900Z
EventRecordID 7795
Channel Application
Computer MB7UCW
Security
- EventData
Service stopped successfully.
Second:
- System
- Provider
[ Name] CumulusService
- EventID 0
[ Qualifiers] 0
Level 4
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2020-09-05T06:31:01.285021900Z
EventRecordID 7796
Channel Application
Computer MB7UCW
Security
- EventData
PowerEvent handled successfully by the service.
There's nothing standing out in the windows logs why this has happened, it's pretty much an isolated entry for CMX at this time.
This also happened with previous release after a few days of use.
Anyone got any thoughts on this one?
CMS seems to have stopped again this morning for now apparent reason that i can see.
The laptop is still up and running and doesn't sleep, and the other apps are still happily ticking over.
Looking at the windows event log there are two entries for CMX this morning:
first:
- System
- Provider
[ Name] CumulusService
- EventID 0
[ Qualifiers] 0
Level 4
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2020-09-05T06:31:01.285021900Z
EventRecordID 7795
Channel Application
Computer MB7UCW
Security
- EventData
Service stopped successfully.
Second:
- System
- Provider
[ Name] CumulusService
- EventID 0
[ Qualifiers] 0
Level 4
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2020-09-05T06:31:01.285021900Z
EventRecordID 7796
Channel Application
Computer MB7UCW
Security
- EventData
PowerEvent handled successfully by the service.
There's nothing standing out in the windows logs why this has happened, it's pretty much an isolated entry for CMX at this time.
This also happened with previous release after a few days of use.
Anyone got any thoughts on this one?