KBOX Invalid Credentials error


I've inherited a Kace setup from my predecessor and after some housekeeping I've got one simple error left that drives me nuts:
The K1000 log is basically a long list of the following error:

[2018-02-14 11:37:16 +0100] KBOX [info] Errno 49 Invalid credentials.

It happens approximately 20 times every 2 minutes. 
There's no other information available to me, so I am at a loss how to fix it. 

Is there a way to find out what credentials are causing the error? 

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
After checking the AD-logs I found an old open-manage server that wasn't being used anymore, after shutting it down the error disappeared.
Posted by: DaveMT 3 years ago
4th Degree Black Belt

Top Answer

I ran into this also.  some things I would suggest to check:
Settings>Credentials (This is likely not the cause, but good to make sure they are current)
Home>Label Management>LDAP Labels  (This is what was causing our issue.  we had credentials used to authenticate back to our Active Directory and they were incorrect.  If you know the password to the account used (or just reset it if not) and re-enter the password in all LDAP labels.  Give it a day and it hopefully will clean up your event log.

One step that could help, is if can check your AD Logs to see what account is attempting to authenticate and failing.  That will help you identify which credentials need to be updated.

  • Wow, thank you! I was looking all over including credentials and LDAP authentication. I did not think to check LDAP Labels. - swalker804 1 year ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ