| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuration Manager error on issuing mqsistart |
« View previous topic :: View next topic » |
| Author |
Message
|
| mehedi |
 Posted: Tue May 06, 2003 4:52 am Post subject: Configuration Manager error on issuing mqsistart |
 |
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
HI All,
Created a configuration manager and on issuing mqsistart the following error messages(see below) are received in the event viewer logs
I looked in the registry and the value for the MRM database exists.
In the database the MRM tables exist too.
Message (1)
( ConfigMgr ) The Configuration Manager is not available for use.
A problem has been encountered while trying to start the Configuration Manager. The problem is not expected to be transient.
Stop the Configuration Manager using the mqsistop command. Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem before attempting to start the Configuration Manager again. If the problem persists contact your IBM support center.
Message (2)
(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 WebSphere MQ Integrator Administration Guide for guidance.
If the problem persists, contact your IBM support center.
-----------------------
Other information --
WIN NT
WMQI 2.1
db2level
DB21085I Instance "DB2" uses DB2 code release "SQL07020" with level identifier
"03010105" and informational tokens "DB2 v7.1.0.41", "n010426" and "WR21254".
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| Back to top |
|
 |
| mehedi |
| Posted: Tue May 06, 2003 5:06 am Post subject: Environment Info - correction - Win 2000 advanced server |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
Windows 2000 Advanced Server
WMQI 2.1
db2level
DB21085I Instance "DB2" uses DB2 code release "SQL07020" with level identifier
"03010105" and informational tokens "DB2 v7.1.0.41", "n010426" and "WR21254".
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue May 06, 2003 5:15 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
When creating the configmgr, make sure the user is part of the administrators group.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| mehedi |
| Posted: Tue May 06, 2003 9:37 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
| Thanks eddie that solved my problem |
|
| 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
|
|
|
|
