Posts: 40,483
Threads: 491
Joined: Aug 2002
I guess the data logger is looking at the timeout field as a sort of 'this driver is available' thing. Somewhere, in my recent enumeration work, I switch the name and text parts, and one was Timeouts and the other was TimeOuts. The first is what the original name was, but now it's using the latter, and the logger driver not finding, which probably makes it think the driver isn't available, and so it just fails the other fields without even trying them.
So I will fix that for the next round.
Dean Roddey
Explorans limites defectum
Posts: 599
Threads: 31
Joined: May 2009
Tray monitor crashed again.  I sent you the log although I don't know if I see anything useful in there or not.  My Shoutcast/squeeze software player is complaining a lot so clogged the logs a bit.  I do think though that the tray was OK yesterday and failed tonight (or that's when I noticed).  The logs do seem to go back that far so maybe there will be something there.  Verbosity should have been on high too for the tray mon.
We use shoutcast a lot at xmas so reluctant to take it out of the picture at the moment.  If needed I will after Christmas so we can tackle this properly and may remove the cameras too as they complain a bit.  Let me know if you see anything though.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Yeh, that audio driver is logging a lot of goop. You can try a full log dump which may go back far enough.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
OK, once more... Give 5.3.921 a try. I found another issue that would be a good candidate.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
It's been a while, has it been happy all this time?
Dean Roddey
Explorans limites defectum
Posts: 599
Threads: 31
Joined: May 2009
Yeah sorry, I had to reboot the server a couple times for windows updates and the like over the last little bit so it didn't have a chance to run long enough to get a good test. Unfortunately it died sometime on the 26th or 27th. The fieltag was offline spewing garbage so messed the logs up. Will be able to watch a little closer now again that Christmas is over.
Posts: 599
Threads: 31
Joined: May 2009
Hi Dean, I had this happen tonight at some point. Logging was set to verbose so if anything is logged it should be there. I emailed the logs as they are large - full dump.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Nary a thing related to the Tray Monitor. So, whatever is doing it is not logging anything apparently. It looked like the MS machine was restarted somewhere in there, but I'm assuming that couldn't be the explanation for all the other times this has happened, so it's probably not related.
Dean Roddey
Explorans limites defectum
Posts: 599
Threads: 31
Joined: May 2009
(05-31-2019, 10:22 PM)Dean Roddey Wrote: Nary a thing related to the Tray Monitor. So, whatever is doing it is not logging anything apparently. It looked like the MS machine was restarted somewhere in there, but I'm assuming that couldn't be the explanation for all the other times this has happened, so it's probably not related.
Yeah I don't think the restart would be it.  That reboot I assume was probably a day or two back unless MS Update service forced a reboot I wasn't aware of. It's the icon on the MS that is disappearing.  In theory, a reboot would have reloaded the tray app anyhow so when I found it locked up it would have been running for a bit in a steady state I would think.
Posts: 599
Threads: 31
Joined: May 2009
Dean, I think I've solved this one. Does or did the CQC installer create a scheduled task called " Start CQC Tray Monitor" ? I was going to create a task to restart the service every day and stumbled on this task. Really not sure if I created way back or if CQC does/did.
In the settings tab I changed a couple items. Unfortunately I don't recall exactly which ones. I think I unchecked If the task fails restart and Stop the task if runs longer than 3 days.
It's been a couple weeks and the tray icon has not gone away.
