| Author |
Message
|
| mnance |
 Posted: Mon Feb 21, 2005 10:33 am Post subject: QMgr goes down unexpectedly |
 |
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
I have a Qmgr running on a Windows Server 2003 Domain Controller. I have setup and configured the Qmgr 3 times now and after setup everything works fine. Within an hour the Qmgr has failed and shutdown as well as deleted my Listener and Trigger Monitor out the the MQ Services.msc I have the following errors in the logs directory. Can anyone explain to me what might be going on here?
2/21/2005 10:01:11
AMQ7227: WebSphere MQ encountered the following network error: The trust
relationship between the primary domain and the trusted domain failed.
EXPLANATION:
MQ failed to successfully complete a network operation due to the specified
error.
ACTION:
Ensure that your network is functioning correctly.
----- amqxsecn.c : 3380 -------------------------------------------------------
02/21/05 07:46:24
AMQ7227: WebSphere MQ encountered the following network error: The RPC server
is too busy to complete this operation.
EXPLANATION:
MQ failed to successfully complete a network operation due to the specified
error.
ACTION:
Ensure that your network is functioning correctly.
----- amqxsecn.c : 3380 -------------------------------------------------------
02/21/05 07:46:35
AMQ6119: An internal WebSphere MQ error has occurred (WinNT error 1723 from
NetLocalGroupGetInfo.)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 628 --------------------------------------------------------
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Feb 21, 2005 3:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is your version and CSD?
 |
|
| Back to top |
|
|
| mnance |
| Posted: Tue Feb 22, 2005 5:02 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
WebSphere 5.3 CSD07
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 22, 2005 5:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What is the security configuration you are using? What domain is the machine hosting your MQServer in? What domain is the MQ Service user in? What groups belong to the mqm group? How many domains are you trying to authenticate users against? What is the trust relationship between those?
You should probably discuss this with your Windows Domain Administrator.
Also, MQ doesn't support nested groups.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mnance |
| Posted: Tue Feb 22, 2005 5:42 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
Currently, there is no security configuration set up on the Qmgr or the queues. The MQ server and the user account are all in the same domain. I am only concerned with one domain. I am not using nested groups. The domain account resides in the domain MQM group.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| dhenry |
| Posted: Thu Feb 16, 2006 11:43 am Post subject: |
|
|
Newbie
Joined: 13 May 2002
Posts: 2
Location: Philadelphia, PA, USA
|
I'm experiencing exactly the same issue. The box is a Windows 2003 server, SP1 and nothing fancy about the configuration except the box is in a process control network. Everything is configured to run locally so that shouldn't be an issue. If the QM is running, I cannot view the queues - I receive a permissions errror. I've got a PMR open with IBM, however level three support hasn't seen this either.
So far, the indicators are pointing to DCOM/security/domain configuration. Lastly - SP1 adds "remote" features for "remote" users, which is also being investigated.
I will let you know what we determine. |
|
| Back to top |
|
|
| dhenry |
| Posted: Thu May 04, 2006 7:53 am Post subject: Possible Solution to Post SP1's Access Violation |
|
|
Newbie
Joined: 13 May 2002
Posts: 2
Location: Philadelphia, PA, USA
|
If you're still experiencing this issue, it may be what I experienced. What we found was an Access Violation in one of the MQ processes (amqzlaa0.exe). The result of this, is the inability to open the MMC console and view/edit the queues. This only occurs when using the app through Terminal Services. This turned out to be a regression bug in (tsappcmp.dll) in Windows 2003 SP1. A recently released hotfix (KB916667) adresses this issue. In the meanwhile, a workaround would be to bypass TS and logon either directly to the box, or logon via the console.
Note - Microsoft has yet to post this to the general public, so I'd check their website daily if you're interested. |
|
| Back to top |
|
|
|
|
