Difference between revisions of "ARS1105E"
m (Tweaked error text.) |
m (Minor formatting changes to IBM CMOD password article.) |
||
| Line 26: | Line 26: | ||
arsload: Unable to log load information | arsload: Unable to log load information | ||
arsload: Processing has stopped. The remaining files will NOT be processed. | arsload: Processing has stopped. The remaining files will NOT be processed. | ||
== Troubleshooting == | == Troubleshooting == | ||
Revision as of 12:10, 14 July 2017
What was the error?
Message Number: N/A
Message Severity: Error (Corrective action is required to continue)
Message Text: Userid or password is invalid
Related Errors
arsload: Unable to log load information
What were you doing?
Attempting to load data into Content Manager OnDemand with arsload.
What happened?
The load fails. If you receive a LoadId, then consider running the arsadmin unload command to remove it immediately. If the message was unable to be logged in the System Log, the LoadID may not be stored elsewhere.
Example
arsload: Processing file >testfile< Userid or password is invalid arsload: Processing failed for file >testfile< Userid or password is invalid arsload: Unable to log load information arsload: Processing has stopped. The remaining files will NOT be processed.
Troubleshooting
Check your password
- Double check your password by using it to log in with the CMOD Thick Client.
- If you've recently reset the password on the account, log in with the Thick Client to choose a new password.
- Check arsload.cfg or your stash file to verify the password is correct.
- Did you change the case-sensitivity of UserID or passwords in the client?
Case sensitive passwords
By default, OnDemand uses case-insensitive passwords. Because of the way secure password storage is implemented in CMOD, when passwords are case-insensitive, all passwords are converted to uppercase. Enabling 'case sensitive passwords' after users have already entered their password (possibly with lowercase letters) means that they won't be able to log in unless they enter their password in all uppercase letters. This applies to the contents of the arsload.cfg file as well.
Verify your ars.ini configuration file
Ensure that the HOST parameter in the ars.ini configuration file is a fully-qualified domain name like cmod.yourcompany.com rather than just cmod. Using a short name or alias can manifest itself in strange errors like this.
[@SRV@_ARCHIVE] HOST=ondemand.example.com PROTOCOL=2 PORT=1445 SRVR_INSTANCE=ARCHIVE SRVR_INSTANCE_OWNER=archive SRVR_OD_CFG=/usr/lpp/ars/config/ars.cfg SRVR_DB_CFG=/usr/lpp/ars/config/ars.dbfs SRVR_SM_CFG=/usr/lpp/ars/config/ars.cache