Change of Domain password stops MQ on client working

We have several developers using Websphere MQ on there PC's. We are running a Windows 2003 Network and have a group set up "domain mqm" of which these developers are members. When they first install all works fine. However the moment they have to change there doman password they get the following error message

"Could not Initialize Websphere MQ service objects. 0x8000401A. The server process could not be started because the configured identity is incorrect. Check the username and password. (AMQ4100).

On their local machines; that are running either XP Pro (SP2) as well as/or W2K (SP4) the services are set to start with Local User credentials. All users have local admin rights with their Domain credentials.

I have tried to remove them from the domain group and rejoin them but still no avail, the only solution is to uninstall the application and re install. I have searched through the IBM support forums but can not find a solution

Any ideas
smartstream-stpAsked:
Who is Participating?
 
rama_krishna580Commented:
Hi,

Problem seems like:
You install WebSphere® MQ (WMQ) v5.3 on Windows® XP SP1. You create a queue manager, some queues, and a channel. After reboot, when you try to open the MQServices or MQExplorer you receive "AMQ4100 Could not initialize WebSphere MQ Services objects 0x8000401A. The server process could not be started because the configured identity is incorrect. Check the username and password".  
 
Cause  :
During install, there is a panel asking whether the domain controllers(DC's) are Windows 2000 or not. A more 'accurate' statement is whether the DC's are a new active directory (AD) domain or not (that is, a Windows NT4 domain or a Windows NT4 to AD migrated domain).

You answered yes to this question and so you were asked for a userid. In this case you entered your own userid. The wizard confirms the supplied userid has enough authentication to start the dcom object and since it does it deletes the musr_mqadmin account as it is no longer required.
The problem with putting your own userid would be that when you sign off, all your processes will be terminated. Similarly strmqm, runmqsc, and runmqlsr are all a problem in this Windows setup because they get terminated on signoff.
 
Solution:
By running amqmsrvn -regserver, WMQ redefines the musr_mqadmin account and configures the dcom object to use it. In a new active directory domain, this would have failed, but because this was migrated, it all works and solves this problem.
As a reference, all the WMQ processes should run under the dcom id except amqmtbrn (which runs under the signed on userid), and amqsvc (which normally runs under SYSTEM).
 
R.K
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.