tray icon keeps disappearing

[Shaky]

Can you put it into high verbosity and just let it run that way until it croaks, then get me a log dump? Maybe that will get us some useful info. It's got to be something obscure.

Yeah sure, I'll monitor the memory usage and I just put it into High verbosity for logging as well.  Running the startremapp command didn't bring on any obvious errors but will keep an eye on it and check periodically.

[Dean Roddey]

I'm assuming that machine doesn't ever got to sleep, right? It sounded like the tray was running on the MS, so I'm guessing that the machine going to sleep and coming back (and the tray not dealing well with that) is not a possible issue?

[Shaky]

I'm assuming that machine doesn't ever got to sleep, right? It sounded like the tray was running on the MS, so I'm guessing that the machine going to sleep and coming back (and the tray not dealing well with that) is not a possible issue?

Correct, It's always fully on with power saving stuff off. Client machine is also always on.  Both are virtual machines which I don't think should matter much, but could add a layer of complexity of course...   

Let's see if we can get something in the logs to show a direction to head in I guess. Not sure we can do much else at the moment but wait and watch what's going on and look for a pattern to hopefully emerge.

[Shaky]

It crashed sometime in the last day or two, didn't realise until now. Is there a way to get a log from a day or two back in CQC? I just went into the Log Monitor and did a snap to file. There's nothing in there old enough to be useful...unfortunately my B&K went offline as well so spammed the logs. Unrelated i'm pretty sure.

Memory usage looks fine. It's almost the same usage as Sunday afternoon was.

[Dean Roddey]

So it's still there but not responsive? You can do a full dump by:

1. Open the CQC Command Prompt
2. Do the command:
CIDLogAdmin FullDump /OutFile=Logs.txt
3. That will dump the whole log file to Logs.Txt
4. Too big to post so zip it and e-mail it to me

[Shaky]

Yeah, the icon is still in the tray on the MS but the StartRemoteApp commands from the client on another machine  falls on deaf ears.  When you hover over the tray icon, it then disappears.  I can simply start it again from the start menu and off it goes again.

I must have cleared the logs from the viewer window... Will have to wait it out again.

For my own future reference, the log from the steps above gets created in :C:\Users\CQCMaster\AppData\Local\VirtualStore

[Dean Roddey]

That's just because that's the current directory and the command as I indicated it doesn't give a path, so it just goes wherever the command prompt got opened by the system. You can change the current directory or indicate a path in the output file parameter to put it somewhere else.

[Bugman]

Yeah, the icon is still in the tray on the MS but the StartRemoteApp commands from the client on another machine  falls on deaf ears.  When you hover over the tray icon, it then disappears.  I can simply start it again from the start menu and off it goes again.

I've had this exact behavior for quite some time with previous and current releases, but coming out of sleep mode ion win 10.

[Dean Roddey]

I thought was happy with sleep/wakeup. I'll check that again. That's something I can test myself, though it's very annoying and not fully representative of the real sleep/wakeup cycle. You can't debug a program when the machine is going to sleep, so you can only fake it and it's not really the same.

[Bugman]

I thought was happy with sleep/wakeup. I'll check that again. That's something I can test myself, though it's very annoying and not fully representative of the real sleep/wakeup cycle. You can't debug a program when the machine is going to sleep, so you can only fake it and it's not really the same.

Good luck...It's an intermittent condition. Will run fine for weeks and then fail. Rinse, repeat. On a client in my case.