MQSeries.net :: View topic - Problem stopping broker service from Cluster Administrator

ivan8008

Hi All,

I have installed and configured Microsoft Cluster with WMQ(v6.02), DB2 (8.2), Broker(v6.02), and Config. Manager.
The MQS, broker and the configuration manager services are set to work with a Domain user account, which is a member of the local Adminisrators, mqm and mqbrkrs groups. The db2 instance service on which the broker database is hosted works with the same domain user account....
The MQS, db2 instance, broker and the configuration manager are configured as a cluster resources...

For a certain period everithing worked well, but recently I faced several problems:

1. When trying to stop the broker service from the Cluster Administrator it fails and the service remains in stopping state.
2. the broker database started to work very slowly. Any configuration requests from the Toolkit timed out. I found the following error in the db2 log:
-----------------------------------------------------------------------
2007-03-23-18.09.20.109000+120 I10726H463 LEVEL: Error
PID : 416 TID : 3340 PROC : db2syscs.exe
INSTANCE: WMQII NODE : 000
APPHDL : 0-7 APPID: *LOCAL.WMQII.070323160546
FUNCTION: DB2 UDB, oper system services, sqlo_get_userpw, probe:208
MESSAGE : retry NetUserGetLocalGroups failed, retry count:
DATA #1 : Hexdump, 4 bytes
0x019D570C : 3C00 0000
-----------------------------------------------------------------------
I thought that it is a matter of authorization and changed the db2 instance user to local administrator and now it works normally. But I think that being a cluster resource the instance user shoud be a domain one.

Nothing seems to be changed in the AD security policies but I think that the problem is in the domain account.

Any ideas?

Do you think that problem 1 comes from any auth. verifications with the domain controller?
_________________
Ivan Tumbev
MQ Series Administrator & Broker Developer
ICQ 344974669
ivan_tumbev@yahoo.com