ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » MQ Services failed on Win2000

Post new topic  Reply to topic
 MQ Services failed on Win2000 « View previous topic :: View next topic » 
Author Message
MVO
PostPosted: Mon Nov 05, 2001 8:00 am    Post subject: Reply with quote

Centurion

Joined: 09 Sep 2001
Posts: 131

Hi folks, I'm running MQ series 5.2 on Win 2000. When starting MQ services, I don't have any queue managers displayed. When I selected to close the application, I received this error: MMC.EXE The exception unknown software exception (0xc0000001e) occured in the application at location 0x0008b590. Please help.
Thanks
Back to top
View user's profile Send private message
kolban
PostPosted: Mon Nov 05, 2001 8:16 am    Post subject: Reply with quote

Grand Master

Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA

I would call this one into IBM defect support. When MQ based code "traps", it is obviously not a usage based problem and hence must be product code. Since so many of us have been running MQ 5.2 without incident, I can only imagine it is something peculiar to your environment. IBM defect support have tools and techniques to advise you to capture traces and other diagnostic information to help resolve the problem.
Back to top
View user's profile Send private message
bower5932
PostPosted: Tue Nov 06, 2001 10:39 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I'll attach some notes that I got from support on fixing mmc related problems. I'm not sure if your problem is covered or not....

For 1067s Try this first:
The error occurs because in order for the DCOM object AMQMSRVN.exe to run, the user who launches it must have certain rights
set.

By default, when MQSeries is installed, the MQSeries service process (AMQSVC.exe) and the DCOM object that it launches
(AMQMSRVN.exe) are set up to run under the MUSR_MQADMIN id - and that ID has all of the correct rights set.

Sometimes it is necessary to change the user under which AMQMSRVN runs, this is achieved using the application DCOMCNFG.exe -
and it can be used to clarify which userid (or identity) this process is actually set up to run under. If you run DCOMCNFG.exe and look at
the 'IBM MQSeries Services' DCOM object's Properties, the Identity tab shows who it is configured to run as.

If the identity under which AMQMSRVN is executed does not have the User Right 'Log on as a batch job' in User manager / User Rights
/ Advanced User rights then the 1067 error and event 10004 result.

This is all very intriguing because, according to MSDN, Log on as a batch job means 'Nothing and is not used in Windows NT 4.0!' ...
go figure!

On Windows 2000 the way to set up user rights is with Local Security Settings panel available from Administrative tools. Open up the
User Rights Assignments tree, from which you can select 'Log on as a batch job' and add a user.



____________________________________________________________________________________________



Failure of mmc to start

Various things can cause mmc to fail to start:

1.DCOM related problems with AMQMSRVN - NT event log for any DCOM related messages. Please check both System and
Application logs.
2.Incorrect or expired password on MUSR_MQADMIN - Check that MUSR_MQADMIN has a valid password. This can be done
through User Manager. To set the password, set it to a known value under the user manager, then use dcomcnfg, properties of
MQSeries, Identity page to change the password we have it registered against.
3.Incorrect permissions on registry entries - Check that MUSR_MQADMIN has access to the registry keys under
HKEY_LOCAL_MACHINESoftwareIBMMQSeries. This can be done through REGEDT32.exe
4.Incorrect directory permissions for MUSR_MQADMIN - Check that MUSR_MQADMIN has directory permissions to the MQ
drive and directories including WINNT and SYSTEM32.
5.c:Program Filesetc, a file c:Program (no extension) which is produced by example by installing Host On Demand (Also, products
called "Miracle"?), Tivoli Storage Manager. This one can also be identified by a AMQ4108 failure during install at around 92% or
93% with the last line of amqilogn.txt indicating amqsvc has just been issued. Additionally this problem can cause errors indicating "%1
is not a valid Windows NT application", eg. EventId 7000 from the Service Control Manager, and DCOM event id 10001 (Unable to
start DCOM server).
6.If it is still failing, try running amqmsrvn -regserver
7.Another useful command is 'regsvr32 amqmspsn.dll' (reregister the proxy) - This frequently solves trap related issues
8.It it still fails after the above 2 commands, change the password in the user manager, and use dcomcnfg to change the identity that
MQSeries runs under to have this new password. This can also be done with 'amqmsrvn -regserver -user MUSR_MQADMIN
-password newpwd', but this is not 100% reliable.


If it is a permissions related problem then a message box can appear saying "Unable to switch to directory c:wintsystem32". To resolve it,
grant permissions to Everyone on System32 directory or even better on the whole drive.

This can also be caused if the policies are set unusually, eg. such that the password for MUSR_MQADMIN expires after a certain number
of logins/a certain period of time/it's allowed to log in only at certain times etc. If this sounds likely then the customer should review their
policy settings for MUSR_MQADMIN and make changes such that the password does not expire. If the customer needs to change the
password for MUSR_MQADMIN, they should make sure that MQ is not running (including the service) and then;

1.change the password via user manager, and
2.run AMQMSRVN -user MUSR_MQADMIN -password XXXXXX

alternatively, step 2 can be performed using dcomcnfg. If it is still failing, do the same command as (2) but add -regserver to it.

Checking MUSR_MQADMIN has logon as a service/batch job rights on W2K

Open Start,Programs,Administrative Tools,Local Security Settings. Open up local policies then User Rights Assignments, double click 'Log
on a a service', and ensure MUSR_MQADMIN is in the list (Or add it if it isnt) (and 'Log on as a batch job').

Cant expand queue managers

One possibilty is that SYSTEM.ADMIN.COMMAND.QUEUE has been changed to have default persistance as YES, which breaks mmc.

Comments
General MMC checkup

Check the following - Report on any which are different. Note 'mqm' may be 'machinemqm'.

DComCnfg check

1.Default Properties tag, Default Authentication Level is Connect
Default Impersonation Level is Impersonate
2.Applications Tag, IBM MqSeries Services, Properties
Location - Run application on this computer
3.Security Tag
Use custom access permissions, edit, mqm - Allow access
Use custom launch permissions, edit, mqm - Allow Launch
4.Identity tag
This user, MUSR_MQADMIN (+password...)

Registry check

1.HKEY_CLASSES_ROOTAppIDamqmsrvn.EXEApplID = {x}
HKEY_CLASSES_ROOTAppID{x} - Ensure contact admin set to MUSR_MQADMIN
(Default) is IBM MQSeries Services
2.Find HKEY_CLASSES_ROOTMQServiceManager.MQServiceManager, key CurVer
Look at HKEY_CLASSES_ROOT, find key CLSID={y}
Find HKEY_CLASSES_ROOTCLSID{y} - find key AppId={z}
Check {x} == {z}
3.Now check HKEY_LOCAL_MACHINESOFTWAREClassesCLSID{y}LocalServer32
- Should be D:mqmbinamqmsrvn.exe (or similar)


HKLMSOFTWAREMicrosoftOLE
They were returned access denied.

Notes, on my machine,
{4576E163-FA1A-11D1-ABB8-0004ACF79B59} = x
{55B99860-F95E-11D1-ABB6-0004ACF79B59} = y
{4576E163-FA1A-11D1-ABB8-0004ACF79B59} = z
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
MVO
PostPosted: Tue Nov 06, 2001 11:29 am    Post subject: Reply with quote

Centurion

Joined: 09 Sep 2001
Posts: 131

Hi, thanks for your help. I did the followings and the problem no longer occurs:
1) ran amqmsrvn -regserver
2) ran regsvr32 amqmspsn.dll
3) ran regedt32 to allow MUSR_MQADMIN access to IBM/MQSeries/services.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » MQ Services failed on Win2000
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.