Re: Services properties lost

[Tony.Allison]

Enrico,   There are known issues with CSD06 which pertain to the issues you are having.  You can browse this site in the archives and see all of the known issues.   My suggestion would be to go to CSD07 or CSD08 and you will see these issues go away.   Sincerely, Tony Allison Technical Architect Target Technology Services Enterprise Tools / Middleware 33 South 6th Street 11th Floor / Cube 11240 Minneapolis, MN Direct (612) 304-3740 Cell Phone (612) 518-2625 E-Mail: [EMAIL PROTECTED]   From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Enrico Strydom Sent: Monday, November 01, 2004 7:58 AM To: [EMAIL PROTECTED] Subject: Services properties lost Hi all,   I am using Websphere MQ 5.3 CSD06 on Win 2000 SP4. (I have not tried CSD07)   I have a problem whereby the properties for some of the services for MQ gets lost. If the sequence of installation/setup is the following: 1) Install MQ server 2) add admin id to MQM group 3) create queue manager 4) runmqsc with script to add objects 5) create trigger monitor service 6) apply CSD06 then all seems fine . . . If I change the sequence to: 1) Install MQ server 2) apply CSD06 3) add admin id to MQM group 4) create queue manager 5) runmqsc with script to add objects 6) create trigger monitor service When I restart the machine en look at the services MMC, the listerner is not running. When I look at the properties of the listener the port number is empty. When I update the port number and start the service then all is well until the next reboot (port number missing again). By installing in the sequence first mentioned,  I got around that specific problem.   I now sit with the problem whereby the Trigger monitor on some machines is showing the same symptoms (loosing the init queue property). This last problem I have not been able to recreate - I am going on information received from a client (deep in Africa)   I am just about convinced that the problem is not with the MMC snap-in - I stop MQSeries, add the required registry entries (with an edited .reg file), restart MQ  and all is well (until the next reboot). The registry keys that is missing (trigger monitor) are the following: "Hide"=dword:00000001 "InitQueue"="OPMON.TRIGGER.INITQUEUE" and for the listener the missing entries are: "Port"=dword:00000586 "Hide"=dword:00000001   This is what the entries look like on a working machine [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Services\XXXXX!QMAN\Listener] "Startup"=dword:00000001 "ServiceType"=dword:00000003 "RecAction"=dword:00000001 "RecDelay"=dword:00000001 "RecAttempts"=dword:00000003 "Protocol"=dword:00000002 "Port"=dword:00000586 "Hide"=dword:00000001   [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Services\XXXXX!QMAN\Trigger Monitor] "Startup"=dword:00000001 "ServiceType"=dword:00000005 "RecAction"=dword:00000001 "RecDelay"=dword:00000001 "RecAttempts"=dword:00000003 "Hide"=dword:00000001 "InitQueue"="OPMON.TRIGGER.INITQUEUE"     Any help greatly appreciated Enrico