Secure Release Here: Users cannot log on at terminals

Users are unable to log on at terminals to release their print jobs.

Possible causes of this problem are:

• The employee may have simply entered the wrong logon details at the terminal. You may need to check their account in the authentication system to make sure that the employee’s details are what they think they are.

• The employee’s details may not be present in the authentication system (whether that’s the Blueprint database or an external system). Check that their account is present.

• If the authentication system is offline or unavailable for some other reason, the terminal will not be able to authenticate employees. Make sure that whatever authentication system you are using is online and able to be contacted.

• The terminal itself may be misconfigured in a way that prevents it from authenticating users. Check the configuration details at the terminal to ensure that it is set to communicate with the right Blueprint server. Check that all of its properties are configured correctly in Blueprint Administrator.

• If the terminal is configured correctly, there may be a problem with the script it uses to authenticate users. Test the script in Blueprint Administrator to make sure that it returns the correct data.

• Network problems may mean that the terminal is not able to contact its server to authenticate users. Make sure the relevant Collector is able to be contacted on the network.