| Author |
Message
|
| mqfan |
 Posted: Thu Apr 24, 2008 2:51 am Post subject: Error in Default Config: Exits while trying to create CM |
 |
|
Novice
Joined: 12 Feb 2007
Posts: 11
|
Hi All,
I have installed MB 6.0.0.3 and toolkit 6.0.2 on Windows XP Professional with SP2. WMQ 6.0.2.3.
I have run the default configuration wizard and the samples were working fine. Then I had to uninstall  the whole package including the database (DB2 Run-time Client) and after I reinstalled it I couldnt run the default config. The error is as shown below. I havent changed the use name and password (its a local user in Administrators, mqm and mqbrkrs group).
I have searched for a solution but in vein. I have uninstalled MB and toolkit with out deleting the CM and broker configurations  .
Then I tried
mqsideleteconfigmgr <CN name> -n.
The command returns successfully. As you can see the verification checks by the config wizard are passed but when it comes to the CM creation it throws an error and stops the whole thing. i am able to create CMs with other names and could deploy a message flow. But I am curious to know why the config wizard cant create the CM "WBRK6_DEFAULT_CONFIGURATION_MANAGER"
| Quote: |
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:45 IST 2008]
Checking for the Default Configuration
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
BIP8071I: Successful command completion.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:46 IST 2008]
Checking for the Default Configuration
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
BIP8071I: Successful command completion.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:52 IST 2008]
Verifying that the default queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] does not already exist.
The above task succeeded
Collected output from task >
Stdout: []
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:54 IST 2008]
Verifying that the default broker [WBRK6_DEFAULT_BROKER] does not already exist.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
BIP8013E: Component does not exist.
A component may only be used if it has first been created.
No user action required.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:57 IST 2008]
Verifying that the default broker database [DEFBKDB6] does not already exist.
The above task succeeded
Collected output from task >
Stdout: [C:\Program Files\IBM\MessageBrokersToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>db2 start database manager
DB20000I The START DATABASE MANAGER command completed successfully.
C:\Program Files\IBM\MessageBrokersToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>echo off
C:\Program Files\IBM\MessageBrokersToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>db2 terminate
DB20000I The TERMINATE command completed successfully.
C:\Program Files\IBM\MessageBrokersToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>echo off
C:\Program Files\IBM\MessageBrokersToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>db2 list database directory
SQL1057W The system database directory is empty. SQLSTATE=01606
C:\Program Files\IBM\MessageBrokersToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>echo off]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:58 IST 2008]
Verifying that the default Configuration Manager [WBRK6_DEFAULT_CONFIGURATION_MANAGER] does not already exist.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
BIP8013E: Component does not exist.
A component may only be used if it has first been created.
No user action required.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:39:58 IST 2008]
Verifying that the local domain connection file does not already exist.
The above task succeeded
Collected output from task >
Stdout: []
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:40:09 IST 2008]
Creating the database [DEFBKDB6] for the default broker.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
C:\Program Files\IBM\MessageBrokersToolkit\6.0>CALL mqsicreatedb DEFBKDB6 -i user -a **********
BIP9824I: Creating the DatabaseInstanceMgr Service Component.
BIP9832I: Starting the DatabaseInstanceMgr Service Component.
BIP9828I: Connecting to the Cloudscape Network Server on port 1527.
BIP9809I: Creating Derby Database 'DEFBKDB6', this may take a while.
BIP9829I: Cataloging the Derby Database 'DEFBKDB6'.
BIP9818I: IBM Cloudscape/Apache Derby was used to create the 'DEFBKDB6' database.
BIP8071I: Successful command completion.
C:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:40:11 IST 2008]
Creating the Configuration Manager. [WBRK6_DEFAULT_CONFIGURATION_MANAGER]
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the Configuration Manager.
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
C:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsicreateconfigmgr -i user -a ********** -q WBRK6_DEFAULT_QUEUE_MANAGER WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8078E: A problem was encountered while attempting to create/delete the Configuration Manager.
The operation was not completed successfully.
Check messages in the system log for related errors and retry the operation. If the problem still occurs, contact your IBM support center.
C:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: [] null
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:40:16 IST 2008]
Deleting the Configuration Manager.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
C:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsideleteconfigmgr -q -n -w WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8071I: Successful command completion.
C:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Thu Apr 24 12:40:24 IST 2008]
Deleting the database [DEFBKDB6] for the default broker.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.3
C:\Program Files\IBM\MQSI\6.0
C:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsideletedb DEFBKDB6
BIP9827I: Removing the ODBC Data Source name 'DEFBKDB6'.
BIP9831I: Uncataloging the Cloudscape Network Server.
BIP9833I: Stopping the DatabaseInstanceMgr Service Component.
BIP9826I: Removing the DatabaseInstanceMgr Service Component.
BIP9837I: Shutting down the Derby Database 'DEFBKDB6'.
BIP9830I: Deleting the Derby Database 'DEFBKDB6'.
BIP8071I: Successful command completion.
C:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: []
|
The system error log shows
| Quote: |
( utility ) The Configuration Manager's repository is not available for use.
The Configuration Manager was not able to gain exclusive access to its internal repository. Either another process already has exclusive access to the repository (for example, if another instance of the Configuration Manager is running), or the user ID under which the Configuration Manager was started does not have the required authority to access the repository.
Ensure that the Configuration Manager is not already running, and that no other process is running that may have acquired exclusive access to the repository. Also, ensure that the Configuration Manager's user ID has the required authority to access the database; the user at least needs to be a member of the mqm and mqbrkrs groups, and on Windows the user also needs to be in the Administrators group. |
Could anyone  .
Thanks & Regards,
MQFan
_________________
Ability is what you're capable of doing.
Motivation determines what you do.
But attitude determines how well you do it.
Last edited by mqfan on Thu Apr 24, 2008 2:59 am; edited 1 time in total |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Thu Apr 24, 2008 2:59 am Post subject: Re: Error in Default Config: Exits while trying to create CM |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| mqfan wrote: |
The system error log shows
| Quote: |
( utility ) The Configuration Manager's repository is not available for use.
The Configuration Manager was not able to gain exclusive access to its internal repository. Either another process already has exclusive access to the repository (for example, if another instance of the Configuration Manager is running), or the user ID under which the Configuration Manager was started does not have the required authority to access the repository.
Ensure that the Configuration Manager is not already running, and that no other process is running that may have acquired exclusive access to the repository. Also, ensure that the Configuration Manager's user ID has the required authority to access the database; the user at least needs to be a member of the mqm and mqbrkrs groups, and on Windows the user also needs to be in the Administrators group. |
|
Verify the user id and password...
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Apr 24, 2008 3:03 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Could be a few things.
You may have some debris left over from a previous Config Manager. Firstly, make sure that C:\Documents and Settings\All Users\Application Data\IBM\MQSI\components\WBRK6_DEFAULT_CONFIGURATION_MANAGER is empty before you start running the wizard.
Regards
-Matt |
|
| Back to top |
|
|
| mqfan |
| Posted: Thu Apr 24, 2008 3:05 am Post subject: |
|
|
Novice
Joined: 12 Feb 2007
Posts: 11
|
Thank you for the reply...but if you have read it ...
| Quote: |
I havent changed the use name and password (its a local user in Administrators, mqm and mqbrkrs group).
|
.
I feel there are some CM components left behind during the uninstallation. If it is so where all do I have to check to find it out?
Thanks.
_________________
Ability is what you're capable of doing.
Motivation determines what you do.
But attitude determines how well you do it. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 24, 2008 3:08 am Post subject: Re: Error in Default Config: Exits while trying to create CM |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gaya3 wrote: |
Verify the user id and password...
|
Poster's already said he's using the same user id & password, and can create other named CMs with them. Do read the posts before replying.
I'm assuming Windoze here, and I would guess there's a registry key or similar indicating to the wizard that it's already created that CM & it exists. Might be worth trying to create it with the command line to see what happens....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Thu Apr 24, 2008 6:32 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear MQFan,
This happened for me once. Following are the list of action I took and it got succeeded. Just make a try
delete the default broker and CM if it exists using the commands
since my broker DB didnt contain any important info I dropped the DB.
Then I deleted the QM used by Broker and CM.
Then rerun the wizard. It was successful for me. But not sure for urs 
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| mqfan |
| Posted: Thu Apr 24, 2008 10:01 pm Post subject: Problem Solved :) |
|
|
Novice
Joined: 12 Feb 2007
Posts: 11
|
Hi All,
I have cleared "C:\Documents and Settings\All Users\Application Data\IBM\MQSI\components\WBRK6_DEFAULT_CONFIGURATION_MANAGER" contents and the rerun the Wizard...it worked  . thanks a lot Matt.
Vitor thank you for pointing out
| Quote: |
| Do read the posts before replying. |
. And again I have tried the command line and cleaning up the registry but it didnt work.
sri_csee1983...I have tried that as well but that didnt work too.
Thank you guys . This forum ROCKS 
Regards...
_________________
Ability is what you're capable of doing.
Motivation determines what you do.
But attitude determines how well you do it. |
|
| Back to top |
|
|
|
|
