| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Queue Manager stays up only in interactive session |
« View previous topic :: View next topic » |
| Author |
Message
|
| MQChela |
 Posted: Thu Feb 16, 2012 6:54 am Post subject: |
 |
|
Novice
Joined: 07 Feb 2006
Posts: 20
|
| Quote: |
Sure... I more was thinking of stopping the taskbar icon, stop the service, and if amqmsrvn.exe is still running then kill it. If the process token of amqmsrvn is not administrative, adding MUSR_MQADMIN to be an administrator is ineffective until that process restarts.
|
Will try that tonight. We did bounce "IBM MQSeries" service after adding MUSR_MQADMIN to local admin group. Perhaps rebooting the server is clean way but will have to wait until Saturday afternoon.
| Quote: |
The FDC was explicitly saying MQ tried to open the file under that userid and did not have access to the file. What makes you think it does have access to that file? On the failing machine you need to ensure that local mqm has full control over the folder, and ensure it was reapplied to all subdirs and contents. Explore through to the file, and see what the effective permissions of musr_mqadmin would be.
|
I did check effective permissions on that file and they came out to be full control and everything in grey (inherited).
| Quote: |
Putting musr_mqadmin in administrators group really isnt needed for normal mq operation but if you are trying to do a form of DR onto other boxes rather than use MSCS which sorts it all out for you, then by making it administrative you are probablyt benefitting from the fact admins have full control by default. The alternative is to add the mqm group in manually on the failing node for this to work.
|
Do you mean drop existing mqm group and recreate manually? |
|
| Back to top |
|
 |
| JasonE |
| Posted: Thu Feb 16, 2012 7:03 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Quote: |
| I did check effective permissions on that file and they came out to be full control and everything in grey (inherited). |
It may well simply be that amqmsrvn was left running when you added musr_mqadmin to the admin group, and hence hasnt yet got the right permissions.
| Quote: |
| Do you mean drop existing mqm group and recreate manually? |
No, just go to permissions, add mqm group with full control and apply to all sub items/folders. The main issue is on the working server, the mqm group will show up as already being in there, but when on the DR machine, the mqm hasnt been added automatically (and MQ doesnt always inherit)
If it still fails, use process monitor and watch for access denieds. Also try to confirm that if it still fails, its still the same issue - ie same fdc's for the same file. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
