Central User Manager Initialization Failed With Error
Contents |
AMQ9557 COULD CAUSE CONFUSION . Subscribe to this APAR By subscribing, you receive periodic emails alerting you to the status of the APAR, along with security accounts manager initialization failed because of the following error directory service a link to the fix after it becomes available. You can track this security accounts manager initialization failed because of the following error 0xc00002e1 item individually or track all items by product. Notify me when this APAR changes. Notify me when an APAR security accounts manager initialization failed server 2003 for this component changes. APAR status Closed as program error. Error description If a Websphere MQ queue manager is configured to check userid and password with these settings: - ALTER QMGR CONNAUTH(LOCAL.ISPW) -
Security Accounts Manager Initialization Failed Windows 7
DEF AUTHINFO(LOCAL.ISPW) AUTHTYPE(IDPWOS) CHCKCLNT(OPTIONAL) ADOPTCTX(YES) and the following is used - USER_OWNER : user ID used to start the client application (or owner of the application) - USER_MQCSP : user ID passed in MQCSP structure for authorization check. The password is also provided in MQCSP structure. In these scenarios the error message AMQ9557 may cause confusion: Scenario 1: USER_MQCSP has no authority to access the queue amq9557: queue manager user id initialization failed manager. The client application fails to connect and following error messages are generated in queue manager error log: AMQ8077: Entity 'USER_MQCSP' has insufficient authority to access object 'QM1'. EXPLANATION: The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: connect AMQ9557: Queue Manager User ID initialization failed for 'USER_OWNER'. EXPLANATION: The call to initialize the User ID 'USER_OWNER' failed with CompCode 2 and Reason 2035. Scenario 2: USER_MQCSP has authority to connect and open objects on QM1. But the password is incorrect. The client application fails to connect and following error messages are generated in queue manager error log: AMQ5534: User ID 'USER_MQCSP' authentication failed EXPLANATION: The user ID and password supplied by 'amqsputc' could not be authenticated. AMQ5542: The failed authentication check was caused by the queue manager CONNAUTH CHCKCLNT(OPTIONAL) configuration. EXPLANATION: The user ID 'USER_MQCSP' and its password were checked because the queue manager connection authority (CONNAUTH) configuration refers to an authentication information (AUTHINFO) object named 'LOCAL.ISPW' with CHCKCLNT(OPTIONAL). This message accompanies a previous error to clarify the reason for the user ID AMQ9557: Queue Manager User ID initialization failed for 'USER_OWNER'. EXPLANATION: The call
user ID and password, 2035 MQRC_NOT_AUTHORIZED Technote (troubleshooting) Problem(Abstract) As an MQ administrator you create a new queue manager in WebSphere MQ the queue manager is configured to require a user id and password, but none was supplied. version 8.0. You can access the queue manager by using WebSphere MQ
Amq9776: Channel Was Blocked By Userid
Explorer or MQ client applications in bindings mode. You are aware of the default behavior for the channel authentication
Amq5542
records in which an MQ administrator cannot remotely access the queue manager. To gain access an administrator can either set the queue manager attribute CHLAUTH to DISABLED, or add the http://www.ibm.com/support/docview.wss?uid=swg1IT08408 appropriate records to allow remote access. This behavior is documented in the following technote: http://www.ibm.com/support/docview.wss?uid=swg21577137 WMQ 7.1 / 7.5 queue manager RC 2035 MQRC_NOT_AUTHORIZED or AMQ4036 when using client connection as an MQ Administrator You try to remotely access the queue manager as an MQ administrator and you get the return code 2035 MQRC_NOT_AUTHORIZED. You expected that the issue with the http://www.ibm.com/support/docview.wss?uid=swg21680930 channel authentication records had been addressed. Symptom To find out more details, view the error log for the queue manager. There are 3 errors: 6/6/2014 06:33:10 - Process(7512.22) User(rivera) Program(amqzlaa0.exe) Host(HOST_A) Installation(Installation3) VRMF(8.0.0.0) QMgr(QM_ANG8) AMQ5540: Application 'Sphere MQ\bin64\amqsputc.exe' did not supply a user ID and password EXPLANATION:The queue manager is configured to require a user ID and password, but none was supplied. ACTION: Ensure that the application provides a valid user ID and password, or change the queue manager configuration to OPTIONAL to allow applications to connect which have not supplied a user ID and password. ----- 6/6/2014 06:33:10 - Process(7512.22) User(rivera) Program(amqzlaa0.exe) Host(HOST_A) Installation(Installation3) VRMF(8.0.0.0) QMgr(QM_ANG8) AMQ5541: The failed authentication check was caused by the queue manager CONNAUTH CHCKCLNT(REQDADM) configuration. EXPLANATION: The user ID 'rivera' and its password were checked because the user ID is privileged and the queue manager connection authority (CONNAUTH) configuration refers to an authentication information (AUTHINFO) object named 'SYSTEM.DEFAULT.AUTHINFO.IDPWOS' with CHCKCLNT(REQDADM). This message accompanies a previous error to clarify the reason for the user ID and password check. ACTION: Refer to the previous error for more in
reason for this error there. Common reasons for this error are: Incorrect file/directory permissions: manager initialization failed Below 644. In order files to be read by the webserver, their permissions have to be equal or above 644. You can update file permissions with a FTP client or through cPanel's File Manager. Restrictive Apache directives inside .htaccess file. There are two Apache directives which can cause this error - 'Deny from' and 'Options -Indexes'.