DESCRIPTION:
- Customer completed the Production of two new lines. Customer attempted to refresh the queues within the MTS Configuration section of Prognosis PULSE. This worked as expected during testing within the TEST environment, however it failed when placed into production. They received the below error message after clicking "Refresh Queues"
\<NAME>: User logon failed. CAUSE: Unable to logon user at the target system.
ANALYSIS:
The “User logon failed” error is caused by the fact that you want to run the command on a remote node and it requires a login ID and password in order to logon to the machine and run the command. But this login details are not provided, hence it triggered the message.
So depending on which node you are trying to run the command on, you need to enter the ID and password for that node. This indicates that the user credentials used to logon to the GUI are not valid on the monitoring node running the database.
For example when you run a command:
• You may supply alternate credentials by clicking the ‘advanced’ button at the database start prompt. (the dialog box you click through after clicking the ‘start’ link)
• Click on it then tick Remote Logon, then you can enter the ID and password for that remote machine.
RESOLUTION:
You need to enter the ID and password for that node. This indicates that the user credentials used to logon to the GUI are not valid on the monitoring node running the database.
For example when you run a command:
• You may supply alternate credentials by clicking the ‘advanced’ button at the database start prompt. (the dialog box you click through after clicking the ‘start’ link)
• Click on it then tick Remote Logon, then you can enter the ID and password for that remote machine.
It was confirmed by customer that the remote credentials were empty
If my answer helped you today, please give my post a like and be sure to mark the 'Accept Solution' button to help others find the answer!
Cheers
Andy Gjertsen
