VAS Errors of [auth_vas4:error] in K1000 Server's Error Logs. (4289405)

All Users and Administrators are not able to login to the K1000 Server adminui or webui pages. 

The K1000 Server is pingable and after some initial checks, all the services are running and all databases are as per normal without any corruption. 

Apache service is also running but unable to provide any web pages for webui, adminui or systemui. 

The errors from K1000 Error Logs indicates the following: 

[Tue May 17 22:03:12.966152 2016 ] [auth_vas4:error]  [pid 29888: tid 36698968288]  [client 192.168.67.68:64371] authenticate_gss_user: no VAS context, check for errors logged at startup

This is caused by the SSO module which was not being disabled when the K1000 Server's IP Address or Hostname have been changed and rebooted.

When the K1000 Server comes back from the reboot process with a new Hostname and IP Address, the SSO module will trigger such errors and K1000 unable to display the web pages properly. 

If the K1000 Server is an appliance and changes to the Hostname or IP Address have been made, login via the K1000 Console with konfig credentials and revert back the Hostname or IP Address to the former configurations and settings.

When the K1000 is back online, you should be able to login to the webui. Now, disable the SSO first then only make changes to the IP Address or Hostname if required.

However there are other considerations that might need to be look into before doing any changes to the initial setups because all the KACE Agents are currently using the K1000 Hostname and IP Address. 

Here are some best practices if there are requirements to change the Hostname or IP Address of the K1000 Server: 

• How to change K1000 IP address KB 181478

  How to Resolve Agent Check in Problems when the K1000 IP Address is Changed on the Network KB 111183