| Author |
Message
|
| DaveABowden |
 Posted: Thu Aug 12, 2004 2:25 am Post subject: Listener fails after Windows XP reboot with process error 10 |
 |
|
Newbie
Joined: 12 Aug 2004
Posts: 2
|
There appears to be a problem with some WMQ installations on Windows XP. The symptom is that some of the listeners fail to start when Windows is rebooted. The warning in the Windows event log is:
| Quote: |
Error code 0 starting {queue manager}/Listener WebSphere MQ service.
The service was unable to start {queue manager}/Listener. The error message reported was as follows:
The process has terminated with return code 10. |
On closer inspection it appears that the Listener has forgotten its TCP/IP protocol information. This can be entered manually via the MQ Service Explorer, but this would need to be done each time Windows is rebooted. Instead it is possible to modify the registry to insert the missing information for the errant queue manager.
It is advisable to backup the Windows Registry before making any changes.
using regedit, edit the following registry key:
1. HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Service\{queue manager}\Listener
2. If you only have five registry items then three are missing.
3. Add a new DWORD item with a name of Protocol and a value of 0x2. Note, registry entries are added in little endian order, e.g. a DWORD consists of four half words so the hex value 0x2 is entered as 02 00 00 00.
4. Add a new DWORD item with a name of Hide and a value of 0x1.
5. Add a new DWORD item with a name of Port and a value of your queue managers TCP port. For example if your queue mangers port is 1414, in hex this is 0x586. |
|
| Back to top |
|
 |
| offshore |
| Posted: Thu Aug 12, 2004 2:39 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Dave,
What CSD is MQ at? I was thinking around CSD03 or CSD04 there was a fix for a QMGR losing its listener information due to it not writing/saving to the Windows registry correctly.
Offshore |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Aug 12, 2004 8:12 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
CSD06 had that problem
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| suri |
| Posted: Thu Aug 12, 2004 10:04 am Post subject: |
|
|
Apprentice
Joined: 16 May 2004
Posts: 39
Location: NewYork
|
|
| Back to top |
|
|
| DaveABowden |
| Posted: Fri Aug 13, 2004 11:11 pm Post subject: |
|
|
Newbie
Joined: 12 Aug 2004
Posts: 2
|
Normally I just load the base MQ 5.3, but one of my team recently installed CSD 3 then CSD 6 and started experiencing this problem. I then repeated the same install and got the same problem he experienced. The inference is that the problem occurred somewhere on one of these CSDs. If I get time I will go through the install again and try CSD 7.
The problem is that the failure to correctly configure the listener is intimating, i.e. some are created correctly and some have the missing registry items. |
|
| Back to top |
|
|
| EddieA |
| Posted: Sat Aug 14, 2004 10:12 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
It's CSD 6. And it only affects QMs that are created at this level. Either apply the hiper-fix, or CSD 7.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
