SQLSTATE[42S22]

[adukes40]

@Tom-Elliott Lol. OK, updating again.

[adukes40]

@Tom-Elliott Alright, my issues seems to be checking out now. All looks good so far. Thanks Tom!

[Tom Elliott]

Update again, I found another issue with imaging that it couldn’t find the right field.

This is now fixed, and I think imaging is more important than GUI. Hopefully all will be well.

[adukes40]

@Tom-Elliott I was getting ready to say that there was an error Attempting to checkin during deployment. Updating now.

[adukes40]

@Tom-Elliott OK, looks like imaging is running now. And the other parts still look good.

[Tom Elliott]

Safe to say this one is solved now?

[Roger Saffle]

im seeing some cert errors in my clients after doing all these updates. I went into our all group and hit the cert update button. Is that all I need to do? Doing latest update now.

[Tom Elliott]

@Roger-Saffle You mean invalid security token?

[Roger Saffle]

@Tom-Elliott yes

[Roger Saffle]

@Tom-Elliott the reboot problem is fixed, yes

[adukes40]

@Tom-Elliott Just set an image and came back to it in sleep mode. Checked machine and the snapins did not run. I found this in the log:

---

--------------------------------Authentication--------------------------------

6/21/2016 8:56 AM Client-Info Version: 0.9.12
6/21/2016 8:56 AM Middleware::Communication URL: http://10.103.72.49/fog/management/other/ssl/srvpublic.crt
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not get security token
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not find file ‘C:\Windows\system32\token.dat’.
6/21/2016 8:56 AM Data::RSA FOG Server CA cert found
6/21/2016 8:56 AM Data::RSA ERROR: Certificate validation failed
6/21/2016 8:56 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not authenticate
6/21/2016 8:56 AM Middleware::Authentication ERROR: Certificate is not from FOG CA
6/21/2016 8:56 AM Service Sleeping for 120 seconds

[Tom Elliott]

@adukes40 reset encryption data.

[Roger Saffle]

@adukes40 Yep that the exact error I was talking about just now. I did a reset on all. Did not seem to make a diff. I went into our all group and hit the big button. Is that what you are asking us to do?

[Tom Elliott]

@Roger-Saffle time not valid is a bit concerning. That isn’t anything I can help server side. Check you clients times to make sure they’re within the time of the certificate period.

[Roger Saffle]

@Tom-Elliott
Im sorry I did not see that on his error. Mine does not have a time error. Just the below.

--------------------------------Authentication--------------------------------

6/21/2016 12:43 PM Client-Info Version: 0.9.10
6/21/2016 12:43 PM Middleware::Communication URL: http://10.95.95.100/fog/management/other/ssl/srvpublic.crt
6/21/2016 12:43 PM Data::RSA FOG Server CA cert found
6/21/2016 12:43 PM Data::RSA ERROR: Certificate validation failed
6/21/2016 12:43 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
6/21/2016 12:43 PM Middleware::Authentication ERROR: Could not authenticate
6/21/2016 12:43 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
6/21/2016 12:43 PM Service Sleeping for 120 seconds

[Tom Elliott]

@Roger-Saffle I think a new thread would be good. This is now leading in an entirely different direction as what the problem was with this thread.

[adukes40]

@Tom-Elliott I am starting to lean towards FOG not liking my hosts import. It sees some hosts, not all and the same machine that the log was from, I removed from FOG and performed a full inventory, and imaged again. All is going through now. I guess we will just perform full registers on all hosts (thats what summer help is for)

[Tom Elliott]

@adukes40 importing works but I’m not sure where the tie down is. In most cases the pending hosts field is likely the culprit though one of my changes was to try to address that.

[adukes40]

@Tom-Elliott its no big deal. once this summer is over, adding new hosts gets more rare. It was just this being our first roll out, there will be a lot of machies to touch. All good though, rather have FOG do what it needs correctly instead of me tearing it up.