What was the error?
Message Number: 1105
Message Severity: Error (Corrective action is required to continue)
Message Text: ARS1105E Userid or password is invalid
arsload: Unable to log load information
ARS1609W - Specifying passwords on the command line is not secure due to the text being visible.
What were you doing?
Attempting to load data into IBM Content Manager OnDemand with arsload or starting arsload in Daemon Mode.
The load fails, or arsload refuses to start in Daemon mode. 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 CMOD System Log, the LoadID may not be stored elsewhere.
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. # arsload Daemon Load fails, especially after an upgrade to CMOD v10.5 arsload -u CMOD_Load_User -p /opt/IBM/ondemand/V10.5/config/ars.stash -v -c /arstmp -d /arsacif/acif1 ARS1105E Userid or password is invalid
Check the OnDemand stash file
If you've just created a new CMOD stash file with the arsstash command:
- Check the command use used to create the stash file. For arsload, you should use the
- Check the ownership and permissions of the file. For security, the stash file's permissions are restrictive.
$ ls -l /opt/IBM/ondemand/V10.5/config/ars.stash -rw------- 1 archive sysadm1 11409 Jun 27 08:40 /opt/IBM/ondemand/V10.5/config/ars.stash
- Ensure the user trying to execute the arsload command is the same as the owner of the file.
Check your password
- Double check your password by using it to log in with the CMOD Thick Client.
- If you're not able to use the password to log in, have your Content Manager OnDemand Admin reset the password for you.
- If the password has been reset recently, log in with the Thick Client and choose a new password.
- If you've reset the OnDemand password, re-create the stash file with the new password.
- Did you change the case-sensitivity of UserID or passwords in the IBM CMOD Admin Client? You'll likely need to re-create the stash file, and ensure you use the correct case for both the UserID and Password.
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
Check the GSKit Install
If this is a new or recently upgraded CMOD installation, check that the IBM Global Security Kit is installed properly. Content Manager OnDemand uses the GSKit for cryptographic functions, including password hashing for authentication. A problem with the GSKit installation can cause command line logins to fail. Run the
gsk8capicmd_64 from the command line. If you're presented with a screen full of errors (prominently featuring messages about missing libraries) then you'll need to update your LIBPATH or LD_LIBRARY_PATH environment variables to put the GSKit libraries (in /usr/lib on AIX) at the start of the environment variable.
You can check the contents of the environment variable with the
$ echo $LIBPATH /home/archive/sqllib/gskit:/usr/lib:/lib
$ echo $LD_LIBRARY_PATH /home/archive/sqllib/gskit:/usr/lib:/lib
In this case, the DB2 library for the IBM Global Security Kit comes before the operating system libraries. This can cause GSKit to fail, because it's finding older and incompatible libraries BEFORE the ones that match the newer version that you installed. You can alter your login profile to prefix the operating system libraries:
Then log out, and log back in again to get the update environment variables loaded, and try the
gsk8capicmd_64 command again.