30. KBGEN0001 - ANS2622S An invalid ID or password was submitted.
| Summary | This article will guide you through resolving the error message "ANS2622S An invalid ID or password was submitted" when you try to run TSM |
| Symptom | When trying to run TSM, the error message "ANS2622S An invalid ID or password was submitted" is returned. |
| Cause 1 | Possible Cause - TSM on your machine is configured with the wrong nodename. |
| Resolution 1 | Check your TSM nodename via the
TSM backup client information page.
Then start the TSM Backup client program and answer Yes to the
error message that displays. At the TSM main window, choose the Edit
menu and [Preferences] option. The General tab should display. Change the entry
in the Nodename field to the Nodename registered - typically of the form Username-freetext-Department/college.
Click OK and restart the TSM Backup Client program. After doing this, Windows users should proceed to follow the instructions in our page on
updating the TSM scheduler in Windows to ensure that their scheduler is correctly
configured. |
| Cause 2 | Possible Cause - TSM on your machine is configured to connect to the wrong HFS TSM server. |
| Resolution 2 | Check which server you should be contacting via
the TSM backup client information page and note
the value in the Server column for the TSM
nodename of your machine. This value will correspond to the last two characters of one of the Server Names in the table below.
To check if you are connecting to the correct OUCS TSM server, note the DNS Name and Port
from the table above, then start the TSM backup client program and answer
Yes to the error message that displays. At the TSM main window, choose the Edit
menu and [Client Preferences] option. Select the Communication tab. Ensure that the
value in the Server Address field corresponds to the DNS name and the
value in the Server Port field corresponds to the Port from the table above. If they do not,
amend them to their correct values, click OK and restart the TSM Backup Client program. After doing this, Windows users should proceed to follow the instructions in our page on
updating the TSM scheduler in Windows to ensure that their scheduler is correctly
configured.
|
| Status | |
| More Information | |
| Applies To | TSM |
Up: Contents Previous: 29. KBNTW0001 - Scheduled backups fail due to failure to connect to the NDS Next: 31. KBGEN0002 - "ANS1357S Session rejected: Downlevel client code version"