On Windows™, the message AWSDEQ024E is received
When attempting to log in to conman on a Windows™ operating system, the following error
is received:
|
Cause and solution:
This problem can have a variety of causes related to users and
permissions. On the server, perform the following checks:
- <˂TWS_user>> password
- Make sure that the password that you supplied for the <˂TWS_user>> user is correct, that the account is not locked out, and that the password has not expired.
- Tokensrv service
- Ensure
that the Tivoli® Token Service
(tokensrv) is started by the IBM Workload Scheduler administrative
user (not the local system account). This must be verified in the
properties of that service in the Services panel; see IBM® Workload Scheduler: Administration
Guide for details of how to access that panel and view the
details of the user that "owns" the service.
If the password to this user has changed on the workstation, check also that the password has been changed in the entry on the Services panel.
- File ownerships
- Check that the following ownerships are correct:
- All .exe and .dll files in the <TWA_home>\TWS\bin directory are owned by the <˂TWS_user>>
- All .cmd files are owned by "Administrator"
If necessary, alter the ownership of these files as follows:- Stop any active IBM Workload Scheduler processes.
- Change to the <TWA_home>\TWS directory.
- Issue the following commands:
setown -u <TWS_user> .\bin\*.exe setown -u <TWS_user> .\bin\*.dll c:\win32app\maestro> setown -u administrator .\bin\*.cmd - Issue a StartUp command on the affected server.
- On the IBM Workload Scheduler master domain manager, launch conman.
- Once conman is started, issue the following command sequence: link @!@;noask
- Keep issuing the sc command to ensure that all the servers relink. A server is considered linked if the State shows "LTI JW"
- Advanced user rights
- Make sure
that the <˂TWS_user>> has
the correct advanced user rights, as documented in the IBM® Workload
Scheduler: Planning and Installation Guide. These are as follows:
- Act as part of the operating system
- Adjust memory quotas for a process
- Log on as a batch job
- Log on as a service
- Log on locally
- Replace a process level token
- Impersonate a client after authentication right