| Author |
Message
|
| smyers |
 Posted: Thu Jul 18, 2002 1:34 pm Post subject: Unable to set up default configuration (AMQ4203) |
 |
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Hello everyone, I am trying to install MQ5.2 on Windows 2000. It seems to install properly, but when I go to set up the default Queue Manager(through "first steps") I get the error:
Unable to set up default configuration (AMQ4203)
It then gives more detail by stating the following:
Unable to create the default configuration cluster receiver channel - error code 4032.
Next, I go into MQ Explorer and try to create a Queue Manager. It lets me create one in there, yet when I click on the "advanced" tab and click on "channels", I see the following error:
Unexpected MQSeries Error (2136) (AMQ4802)
I then click on channels and select "new" Sender Channel and I see the following error:
Default object not found. Cannot create a new object because the default object for the object type could not be found. (AMQ4000).
I get this same error for several of the folders in the advanced tab.
If anyone has ANY suggestions I would appreciate it. I have checked into my permissions (tried everything with them) and tried to find some help on the ibm site, but the suggested remedy to this problem seems to be to contact their support. Please don't make me call support and listen to Wayne Newton (although he does deserve credit for that hair). It just won't create the necessary system objects!!! HELP!
Thanks for your time... |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Jul 19, 2002 7:47 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I saw a similar problem on another bulletin board with the following response:
I see that customers have seen this, and have generally found it to be fixed after adding permissions for the local mqm group to a file named ccsid.tbl, which is in the directory <installdir>\conv\table. How this file came to be installed without these permissions, I don't know.
If you got any FDC files with the error, I'd suggest posting the top of them here. They can sometimes point to the actual problem.
Ron |
|
| Back to top |
|
|
| smyers |
| Posted: Fri Jul 19, 2002 8:42 am Post subject: cannot create default configuration |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Hi Ron,
Thanks for your reply!
I checked that ccsid file and it already had the proper permissions for the mqm group. I then went and looked at the error logs again and noticed that in the error file called amqerr01.log I see the following message:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 668.
This corresponds to a message about a failing process from the generated fdc file I have copied below:
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Thu July 18 15:42:42 MDT 2002 |
| Host Name :- M51358 (NT Version 5.0 Build 2195: Service Pack 2) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- MS317000 |
| Application Name :- MQM |
| Component :- mutReportMQError |
| Build Date :- Mar 27 2002 |
| CMVC level :- p520-CSD04G |
| Build Type :- IKAP - (Production) |
| UserID :- t805303 |
| Process Name :- C:\WINNT\System32\MMC.EXE |
| Process :- 00000668 |
| Thread :- 00000632 |
| Major Errorcode :- xecF_E_UNEXPECTED_SWITCH |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6120 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6120: An internal MQSeries error has occurred. |
| Arith1 :- 2136 858 |
| |
+-----------------------------------------------------------------------------+
So, something is happening with the mmc console? I have tried creating the qm from the command line using crtmqm, but still keep getting this error:
MQSeries queue manager created.
Creating or replacing default objects for sm.
Default objects statistics : 29 created. 0 replaced. 1 failed.
For details of the failures that occurred, please check AMQERR01.LOG.
Completing setup.
Setup completed.
Any ideas at all? I am stumped here....
Thanks
Shawn |
|
| Back to top |
|
|
| karthiks |
| Posted: Fri Nov 29, 2002 5:04 am Post subject: Unable to set up default configuration (AMQ4203) |
|
|
Newbie
Joined: 19 Nov 2002
Posts: 3
|
Hello everybody,
I am trying to install WebphereMQ5.3 on Windows 2000. It seems to install properly, but when I go to set up the default Queue Manager (through "first steps") I get the error: function Unable to set up default configuration (AMQ4203)(MQDAIInitialise failed) .
I saw a similar problem on another bulletin board with the following response:
I see that customers have seen this, and have generally found it to be fixed after adding permissions for the local mqm group to a file named ccsid.tbl, which is in the directory <installdir>\conv\table.
I checked that ccsid file and it already had the proper permissions for the mqm group. I then went and looked at the error logs again and noticed that in the error file called FDC files with the error message:
Web Sphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time : - Fri November 29 12:54:12 India Standard Time 2002 |
| Host Name :- JAMIT (NT Version 4.0 Build 1381: Service Pack 6) |
| PIDS :- 5724B4101 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MS000003 |
| Application Name :- MQM |
| Component :- msntCompData::Initialize |
| Build Date :- Jun 17 2002 |
| CMVC level :- p000-L020617 |
| Build Type :- IKAP - (Production) |
| UserID :- db2admin |
| Process Name :- C:\WINNT.0\System32\mmc.exe |
| Process :- 00000521 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| () |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2148007941 80080005 |
| |
+--------------------------------------------
So what is the good solution? Any good idea?
Thanks & Regards,
Karthik |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Fri Nov 29, 2002 8:07 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
I don't know about a good solution, but check that the MUSR_MQADMIN userid is a member of the Administrators group, and the password has not got an incorrect or expired password.
Are your symptoms exactly the same as described previously? |
|
| Back to top |
|
|
| clindsey |
| Posted: Fri Nov 29, 2002 8:26 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Also, the id that you are logged in with (db2admin) must be either a local admin group or in the mqm qroup. To be sure, add it to both.
If you had to reset the password for MUSR_MQADMIN, you must register the new password to the service. Run dcomcnfg and double click on the MQ Service. Select the
identity tab and enter the new password.
You may even need a reboot before it works. Strange things happen sometimes with caching of security in NT/2000.
Charlie |
|
| Back to top |
|
|
| karthiks |
| Posted: Tue Dec 03, 2002 11:35 pm Post subject: |
|
|
Newbie
Joined: 19 Nov 2002
Posts: 3
|
Hi, Charlie
Thanks for your reply!
My problem was solved. I added logonID (db2admin) to local admin group or in the mqm group after that it's worked
Tanks
Karthik |
|
| Back to top |
|
|
|
|
