| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Conflict between Config Mgr and Tivoli Storage Mgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| twegmann |
 Posted: Fri Oct 05, 2001 1:01 pm Post subject: |
 |
|
Novice
Joined: 09 Aug 2001
Posts: 23
Location: New Jersey
|
We are experiencing a problem with MQsi 2.0.1. We've applied patch CSD03 in an attempt to correct a 'java core dump' problem on the broker.
When we try to start the Config Mgr, he fails because MQ services have stopped. IBM support team is indicating they think that Tivilo Storage Manager running on the same box is hosing MQ services.
Has anyone else experienced this problem ?? |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Oct 12, 2001 7:12 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
After seeing your comment about IBM support, I did some searching on our internal databases. I found a hit that looks like the problem that you are seeing. It dealt with problems because MQSeries and MQSI had been installed in a subdirectory that contained a blank. Here is the resolution:
There is a workaround that should resolve the problem - in the
registry, if you change any reference to 'amqmsrvn.exe' so that instead
of 'C:Program Files'they use 'C:Progra-1'. The places to change are:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMQSeriesServices
where the path is specified for AMQSVC.exe and then something under
the HKEY_CLASSES_ROOTCLSIDLocalServer32 where the
path to AMQMSRVN.exe is specified.
For MQSI v2.x, the Configuration Manager, the Brokers and the
UserNameServer may all be started as a service. The workaround will be
similar to the one recommended by Ian for MQSeries, edit the registry
changing the path to 'bipservice.exe' to use 'C:Progra-1' instead of
'C:Program Files'. The places to change are:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMQSeriesBroker*
i.e. MQseriesBrokerConfigMgr, MQSeriesBrokerUserNameServer (if used),
and similarly for any Brokers that run locally on the box.
I haven't seen the above problem myself. There is also a note that this is a work-around because of the Tivoli. Hope this helps.
|
|
| Back to top |
|
|
| twegmann |
| Posted: Mon Oct 15, 2001 7:08 am Post subject: |
|
|
Novice
Joined: 09 Aug 2001
Posts: 23
Location: New Jersey
|
Thanks for taking time to help.
The IBM support team also recommended these registry changes as the workaround. We implemented them on Sunday and all seems to be well. |
|
| 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
|
|
|
|
