| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem starting the configuration manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| dutchman |
 Posted: Tue Feb 12, 2002 4:14 am Post subject: |
 |
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Chaps - I did a spingclean of my desktop pc,
and reinstalled MQ 5.2 (CSD2), DB2 V7.1 (GA) and MQSI V202 (CSD2).
Went through the usual steps to create the configmgr, and started it.
It gave the following error :
( ConfigMgr ) Missing or blank message repository database name.
The message repository database name supplied to the Configuration Manager
is either blank or missing. This is a mandatory property of the
Configuration Manager. The most likely cause of this is manual editing of
the Windows NT registry entries created by the mqsicreateconfigmgr command.
Delete the Configuration Manager using the mqsideleteconfigmgr command,
without specifying the -n or -m options. Then recreate the Configuration
Manager using the mqsicreateconfigmgr command, specifying the correct
database name on the -m option. See the MQSeries Integrator Administration
Guide for guidance. If the problem persists, contact your IBM support
center.
I've checked the command that created the configmgr, and it's fine.
Also, the registry looks fine as well.
All databases registered to ODBC.
Any ideas? |
|
| Back to top |
|
 |
| dutchman |
| Posted: Tue Feb 12, 2002 6:21 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Fixed it. In the past I used userid db2admin as that was also the one that gets set up during the db2 install.
I decided to set up a new userid, and added it to groups mqm and all the MQSI groups. That was obviously not enough.
Comparing it with db2admin, it has group Administrators.
Added this group to my new 'service userid' and now it's working.
Strange that the service userid needs to have those rights.
BTW A similar thing happens when you try to start the broker.
Instead of the above error, you get an MQ code 2058, because it is
trying to connect to a queue manager whose name is the same as
the broker - and mine wasn't. |
|
| 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
|
|
|
|
