APAR status
Closed as program error.
Error description
Upon creating the active instance of a queue manager it fails to start, the following error is produced: AMQ6245: Error executing system call 'CreateFile' on file '\\server\mqdata\qmgrs\QM1\amqprobe.amq' error '1337'. AMQ7001: The location specified for the queue manager is not valid. The Microsoft error correlates to the following: ERROR_INVALID_SID 1337 (0x539) The security ID structure is invalid. The strmqm command was able to read a file from the directory '\\server\mqdata\qmgrs\QM1\qm.ini'; However, it failed when it did a CreateFile '\\server\mqdata\qmgrs\QM1\amqprobe.amq'. You have the security rights needed to perform this operation; furthermore, an MQ trace of the issue may yield similar results to: . Directory(\\server\mqdata\qmgrs\QM1) Permissions(5) Flags(67) - Filename(\\server\mqdata\qmgrs\QM1\amqprobe.amq) Permissions(5) Flags(67) - xcsCreateFile 00000000 12:34:56.789101 1121.3 : File: '\\server\mqdata\qmgrs\QM1\amqprobe.amq', access: -1073741824, sharing: 4, permissions: 5, disposition: 2, attributes: 67108992, ffstOnError: FALSE - xcsCreateFile (rc=lpiRC_FILE_TREE_CREATION_ERROR) 00001201 12:14:15.440289 1121.3 : CreateFile failed: 1337
Local fix
<html>None. </html>
Problem summary
**************************************************************** USERS AFFECTED: Users creating multi-instance queue managers on MQ V8 on Windows platform. The problem is seen with some NAS storage configurations (which restricts local users in the access control list (ACL) set for the files and directories) when used as the shared storage for storing the queue manager data and logs. Platforms affected: Windows **************************************************************** PROBLEM DESCRIPTION: If queue manager is created with -ar option then the local mqm group is not granted access on the queue manager data files. However, in this case the ACL set for the queue manager process handle still incorrectly included the permission for the local mqm group and hence the queue manager processes were unable to access the queue manager data files. For the same reason the commands such as addmqinf , dltmqm also failed.
Problem conclusion
The problem has been addressed by removing the local mqm group permissions set on the queue manager process handle. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.5 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT10185
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-07-20
Closed date
2016-03-17
Last modified date
2016-03-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ BASE MULTIP
Fixed component ID
5724H7251
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
18 March 2016