| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQ freeze startup on Win2003 server |
« View previous topic :: View next topic » |
| Author |
Message
|
| glumotte |
 Posted: Thu Jun 22, 2006 1:48 am Post subject: WMQ freeze startup on Win2003 server |
 |
|
Newbie
Joined: 22 Jun 2006
Posts: 3
Location: France
|
Hello all
I have a strange problem on some of our servers. At the reboot of the server the MQSeries service stays in 'starting' status and is unavailable
Only amqsvc.exe and amqmsrvn.exe are launched.
I've also non eventvwr errors, no fdc ...so it's very hard to resolve...
After server reboot and after the kill of amq* process, I can start normally the IBM MQSeries service without any problem.
It's very located on the server boot
It seems to be linked with the service start order (I put a dependence between mq and the last sevice to start and I have no pb...)
Do you know if there is sommething special to check, or anybody already had this kind of pb ?
The servers are in windows 2003 servers, with SP1. MQSeries is the 5.3 version with CSD11
MQ is running with a special domain account (with have all NT acl and and is good about special rights (replace tokenlevel, etc...))
Than you very much for your help ! 
Damien |
|
| Back to top |
|
 |
| BBM |
| Posted: Wed Jun 28, 2006 4:30 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Hi,
Windows funnies are normally due o permissions with MQ I have found.
Can you try altering MQ to run under a "God" account?
You need to change the identity section under dcomcnfg.exe or run the Prepare MQ Wizard again.
BBM |
|
| Back to top |
|
|
| glumotte |
| Posted: Thu Jun 29, 2006 12:05 am Post subject: |
|
|
Newbie
Joined: 22 Jun 2006
Posts: 3
Location: France
|
Hello
Thank you BBM for your post
We found the "solution"
After many phone calls with IBM Support, we found an APAR about time-out startup at the boot of server (IC47978)
IBM suggest to apply a dependancies between RpcSs services and MQSeries Service.
This will be corrected in CSD13, but at the moment it's needed to do it manually (regedit...)
But, in our case, it was not enough and we will have to create dependancies with the latest service to start. And it was OK
(we used loadorder from sysinternals to have this information) |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
