| Author |
Message
|
| RNStanich |
 Posted: Thu Mar 06, 2003 3:16 pm Post subject: NetUserGetInfo() |
 |
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
We are using WMQI V2.1 CSD2 and on occassion receive the following error:
( ConfigMgr ) Error in call NetUserGetInfo() to the NT security domain with return code 1726.
A component of WebSphere MQ Integrator 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.
Has anyone else seen this?
_________________
Regards, Bob |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Mar 06, 2003 6:50 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
We get this error all the time!
This problems comes when the Configuration manager service fails to contact the backup domain.
The solution is to either restart the Configuration Manager service or to define WMQI Groups on the local server.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| RNStanich |
| Posted: Fri Mar 07, 2003 4:37 am Post subject: |
|
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Thank you Kirani, for your quick response.
I'm not sure what you mean by "define WMQI groups on the local server". Also, why do you suppose the Configmgr fails to contact the BDC? Are we talking defect?
_________________
Regards, Bob |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Mar 07, 2003 8:11 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
If you use -d option when creating configuration manager, you have to define mq* groups on domain server. To get around this problem, the support guys are asking us to define these groups only on the local WMQI box. This is a defect in the product, I'd recommend that you open a PMR with IBM for this.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| KSkelton |
| Posted: Thu Mar 27, 2003 10:23 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
Has a PMR been opened for this yet?
We are receiving this exact error when the Primary Domain Controller is rebooted. The Configuration Manager crashes when a developer tries to connect with the Control Center. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Mar 27, 2003 8:10 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Yes, we did raise a PMR for this problem, but I hate to say this, we did not receive satisfied reply from support guys. We have filled out a form to request a change in the product to fix this problem, I don't know how these requests are handled by IBM.
If you want I can email you the PMR number for your reference.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| KSkelton |
| Posted: Fri Mar 28, 2003 12:43 pm Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
Kiran,
Here is the info from IBMLink. Considering this problem is nearly two years old now, I think we know this will not be fixed:
--------------------------------------------------------------------------
APAR Identifier ...... IC29717 Last Changed..01/07/18
MQSI 2.01 AUTHENTICATION SEEMS TO RELY ENTIRELY ON
PRIMARY DOMAIN CONTROLLER
Symptom ...... IN INCORROUT Status ........... CLOSED SUG
Severity ................... 1 Date Closed ......... 01/07/18
Component .......... 5639F6100 Duplicate of ........
Reported Release ......... 201 Fixed Release ............
Component Name MQSERIES INTEGR Special Notice
Current Target Date .. Flags
SCP ................... NT
Platform ............ WIN/NT
Status Detail: Not Available
PE PTF List:
PTF List:
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
When Primary Domain controler goes down in NT network you get
security errors.
( Configuration Manager ) Error in call NetUserGetInfo() to
the NT security domain with return code 53.
A component of MQSeries Integrator is attempting to call the NT
security domain. The security subsystem returned an error code.
This happens when MQSI is running on Backup domain Controller
LOCAL FIX:
Work around is by promoting BDC where MQSI and ConfigMgr is
running to PDC. After this is done the system need to be
restarted.
PROBLEM SUMMARY:
PROBLEM CONCLUSION:
TEMPORARY FIX:
COMMENTS:
This is requirement R2043, MQSI V2: Authenticate NT user ids on
BDC as well as PDC (especially when PDC has failed)
MQSeries Integrator always uses the primary domain controller to
authenticate ie MQSI will always fail authentication (and locks
up) if the primary domain controller fails and ignores backup
domain controllers even if the backup domain controller is local
and the primary domain controller remote. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 28, 2003 1:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Actually, given that this is an issue with the Configuration Manager, and the Configuration Manager has been completely reworked in the Eclipse version of the WMQI tooling, it may have already been addressed.
We just can't use it with anything that's released or available yet. |
|
| Back to top |
|
|
|
|
