| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| connection to configmgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| helping_hand |
 Posted: Fri Sep 02, 2005 6:38 am Post subject: connection to configmgr |
 |
|
Novice
Joined: 28 Jul 2005
Posts: 14
|
Hi,
i got this error in system services Event viewer
plz help me in sovling this error
Event Type: Error
Event Source: BIPv500
Description:
( ConfigMgr ) Error in call NetUserGetLocalGroups() to the NT security domain with return code 2221.
A component of WebSphere Business Integration Message Brokers is attempting to call the NT security domain. The security subsystem returned an error code.
Check NT security subsystem documentation for the reported error. Restart the relevant service component (UserNameServer, or Configuration Manager). Ensure that a Domain Controller, either Primary or Backup, is available. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Sep 02, 2005 6:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You'll need to restart the configmgr.
Did any of your domain controllers go away, or become unreachable, temporarily, from the network?
If this happens more than once a month, you should open a PMR.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Sep 02, 2005 6:47 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
Found by google, maybe this helps. at least it tells you that 2221 is "user not found".
| Quote: |
SYMPTOMS
When an application running on Windows NT 3.51 makes a call to NetUserGetLocalGroups and passes <domainname>\<username> as the username parameter, where <domainname> is a trusted domain, the following error is returned:
NERR_UserNotFound (2221)
CAUSE
In this API call, username does not allow username to be in the form <domainname>\<username>.
RESOLUTION
This problem has been corrected in the latest Service Pack for Windows NT version 3.51.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
_________________
Regards, Butcher |
|
| Back to top |
|
|
| helping_hand |
| Posted: Tue Sep 06, 2005 12:55 pm Post subject: |
|
|
Novice
Joined: 28 Jul 2005
Posts: 14
|
Thanks everyone helping me.
Its working now
I got logged in with db2admin and created the broker and configmgr again
and now its working fine
thanks and regards |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
