Last night Joe and I found a potential issue with the client in regards to the fog client having “bad” data and we patched it. With any luck, bad cycle data should no longer happen and this should be automatically fixed if it was a problem due to the bad cycle data.

@Tom-Elliott Confirmed resolved. Thanks Tom!

@Tom-Elliott Thanks Tom. I’ll use that if the alert returns with the blank host report. It’s not come back since I did “approve all” a few hours ago.

I updated last week and tried the import again, it’s working.

@Wayne-Workman forgot to write here but this should be good now.

This issue should be fixed now. It was because I was parsing through direct elements (Ensuring integer’s were indeed integers, strings were indeed strings, etc…) But 0 is parsed out as a null/empty/false entry which on update wouldn’t show up. Since changing them back to strings all appears to be working properly.

Thanks for reporting.

I’ve gone ahead and solved the thread, thanks for the heads up.

@Tom-Elliott I guess. The graph appears to be exactly correct at the moment.

Confirmed fixed in 8241

@Tom-Elliott Thanks Tom, I’ll try to update again.

This should now be fixed.

@Tom-Elliott yessir

Every host is changing their hostname first and then joining AD 🙂 awesome job, thanks man! Feel free to mark this as solved.

@Raymond-Bell yes but for some users there is also a GPO adding another shared printer, so I don’t want for them that only one printer appears.
But with last test it seems ok.

Just what you indicated.

mysql
use fog
DELETE FROM multicastSessions WHERE 1;
DELETE FROM multicastSessionsAssoc WHERE 1;
DELETE FROM tasks WHERE taskTypeID = 8;
quit

That’s all

This was cleared up by a hard refresh.

@Joe-Schmitt thank you sir

@Raymond-Bell I’m going to solve this then. The issue was likely from a far older revision of fog where 0 id’s were very much prevelant. This should no longer be the case, with any luck.

@Tom-Elliott same thing. BTW, no need to update both threads. Ill pop over to the other thread since its more on topic

https://forums.fogproject.org/topic/7848/sqlstate-42s22/1

@Tom-Elliott So far so good, given I also remade the image with a new definition to try to escape the problem too.