| Author |
Message
|
| agosain |
 Posted: Tue May 25, 2004 5:29 am Post subject: WebsphereMQ instalaltion problem DCOM error |
 |
|
Newbie
Joined: 22 Nov 2002
Posts: 5
Location: Phoenix US
|
Hi there
I am trying to install the MQ 5.3 on windows 2000 preff. OS
Thought the installation goes of successfully but when i start the MQ service I am getting the following error.
"The server {55B99860-F95E-11D1-ABB6-0004ACF79B59} did not register with DCOM within the required timeout. "
Has anybody faced this problem. pl help
thankx |
|
| Back to top |
|
 |
| JasonE |
| Posted: Tue May 25, 2004 5:40 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
1. Check the event viewer, system log, for com/dcom messages
2. Are you running under the default userid or did you supply your own domain id?
Try after each step of the following:
| Quote: |
1. Open command prompt, cd to mqm\bin dir, amqmsrvn -regserver
2. Same prompt, regsvr32 amqmspsn.dll
3. Change the password to musr_mqadmin, set in dcomcnfg under the mqseries
dcom object, identity page, ensure the userid is musr_mqadmin and type
the new password. Note: If the MQ userid is not musr_mqadmin, do the
same for whatever (domain?) userid is being used.
4. If installed into x:\program files\.... see if there is a file called
x:\program (no extension) and rename it
5. Ensure SYSTEM.ADMIN.COMMAND.QUEUE is set to DEFPSIST(NO)
6. Ensure MUSR_MQADMIN is not disabled and password is not set to expire
7. Check that MUSR_MQADMIN has directory permissions to the MQ drive and directories
including WINNT and SYSTEM32
8. Ensure MUSR_MQADMIN has logon as a service and logon as a batch job rights
9. Ensure the computer does not have the browser service disabled as MQ Install
seems to require it for some reason.
10. Do the dcomcnfg check below, specifically ensuring Default Authentication
Level is Connect
11. Check that MUSR_MQADMIN has access to the registry keys under
HKEY_LOCAL_MACHINE\Software\IBM\MQSeries. This can be done through
REGEDT32.exe
|
[/quote] |
|
| Back to top |
|
|
| agosain |
| Posted: Thu May 27, 2004 8:39 pm Post subject: |
|
|
Newbie
Joined: 22 Nov 2002
Posts: 5
Location: Phoenix US
|
Hi Jason,
Thanks for your comments it really helped me to solve the problem. I have done the steps as given by you . Now I am able to start the mqseries service. but when i open the mq explorer. i get the following error.
"could not initialize websphere mq objects . access is denied (AMQ4100)"
I have added the MUSR_MQADMIN in the administrator group and given full access to the local drives.
I am doing all this using the network user id which is part of the administrator group. I have also added this userid to the mqm group and tried but still i am getting the same error.
I have also done the reinstallation of mqseries but the problem persist.
any help is greatly appreciated...
thanks in advance guys
avi |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri May 28, 2004 1:37 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Sorry, no help but a list of questions 
1. Are you certain the dcom default authentication level is connect
2. When the error occurs are any COM or DCOM errors listed in the event viewer, system portion
3. When the error occurs, does any MQ message get logged in the <mqm>\errors or <mqm>\qmgr\<qmgrname>\errors amqerr01.log files?
4. Is this machine in a domain, if so is it an active directory domain?
Note musr_mqadmin does not have to be a member of the local administrators group.
Also...
| Quote: |
DComCnfg check
Default Properties tag, Default Authentication Level is Connect
Default Impersonation Level is Impersonate
Applications Tag, IBM MqSeries Services, Properties
Location - Run application on this computer
Security Tag
Use custom access permissions, edit, mqm - Allow access
Use custom launch permissions, edit, mqm - Allow Launch
|
|
|
| Back to top |
|
|
| agosain |
| Posted: Sun May 30, 2004 8:26 pm Post subject: |
|
|
Newbie
Joined: 22 Nov 2002
Posts: 5
Location: Phoenix US
|
thanks jason
i have done the changes as given by you in dcomcnfg.
and it worked some of the settings were not as per your reco.
thanks again |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Jun 01, 2004 2:13 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Out of interest, do you remember which one(s)? (Just so I can update some notes I have) |
|
| Back to top |
|
|
| agosain |
| Posted: Tue Jun 01, 2004 3:52 am Post subject: |
|
|
Newbie
Joined: 22 Nov 2002
Posts: 5
Location: Phoenix US
|
Hi Jason,
I have done one change given below: It worked Thanks again
Default Properties tag,
Default Impersonation Level is Impersonate
The error was: I was not able to open the queue manager on the webspheremq explorer. I was able to create the queue manager using the websphere message broker but not able to open it from the webspheremq explorer. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Jun 01, 2004 4:34 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Thats great! Thanks - I've updated the checklist with the dcomcnfg check, as I end up quoting the checklist quite often
I've also made a note internally of the symptoms vs your solution, in case others hit it. |
|
| Back to top |
|
|
| pbravic |
| Posted: Fri Sep 17, 2004 12:56 am Post subject: |
|
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
hi Jason and agosain
Thanks the inputs below solved the similar issue. To understand better can you pls let me know
i) what is the relation between DCOM identified by MUSR_MQADMIN
ii) The MQ explorer was working fine last week and suddenly I got this DCOM error - solved using the steps above. Do you find any reason for change in behaviour of the system |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Sep 17, 2004 2:35 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
i) I'd love to know. It normally seems associated with a reboot, but I have no idea what happens to convert a working dcom installation to a failing one (other than other products changing some defaults perhaps?)
ii) I dont understand the question. MQ uses dcom to convert the service (runs as SYSTEM) into a background process running as MUSR_MQADMIN, and for the guis to talk to this process. |
|
| Back to top |
|
|
|
|
