| Author |
Message
|
| Nathan |
 Posted: Fri Nov 21, 2003 10:40 am Post subject: 2059 after upgrade to 5.3.5 |
 |
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
I hope someone can answer my question.
I just upgraded MQ 5.2.1 to 5.3.5 (on W2K Server). Now, an asp script that one of the developers gets a 2059 message. I can connect to the QMgr via MQExplorer, runmqsc, IH03 and QPasa.
Is there a programming difference between 5.2 and 5.3 for connecting to a QMgr? |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Nov 21, 2003 11:40 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| After the upgrade, did you start the listener. See if the listener is running (if it is connecting in client mode) |
|
| Back to top |
|
|
| Nathan |
| Posted: Mon Nov 24, 2003 4:31 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
Yes, the Listener is running.
The asp script is not connecting in client mode. I have an exact setup running on another machine, still with 5.2.1. |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Nov 24, 2003 12:28 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Are you getting any FDC's? You might see the OpenProcess fdc...
You also state it is working at 5.2.x? Was anything special done on that setup (eg. disable mts layer?) |
|
| Back to top |
|
|
| Nathan |
| Posted: Tue Nov 25, 2003 4:56 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
The 5.2.1 system is a vanilla install. It was here before I got here  I can't see any setup differences between the installs, other than what 5.3 does differently 
Here is an excerpt from the FDC that is created.
| Quote: |
| Component :- xstAddConnectedThread
...
Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqxssvn.exe
...
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
| Minor Errorcode :- OK
| Probe Type :- MSGAMQ6119
| Probe Severity :- 2
| Probe Description :- AMQ6119: An internal Webshpere MQ error has occurred
(Failed to open handle on process 1984 - (5))
| FDCSequenceNumber :- 11
| Arith1 :- 536895769 20006119
| Arith2 :- 5 5
| Comment1 :- Failed to open handle on process 1984 - (5)
| Comment2 :- Access is denied.
...
----} xcsFFST rc=OK
--} xstAddConnectedThread rc=xecF_E_UNEXPECTED_SYSTEM_RC
-} xstStorageRequest rc=xecF_E_UNEXPECTED_SYSTEM_RC
-{ xstStorageRequest
... |
Thanks for helping me out. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Nov 25, 2003 5:22 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Give the userid MQ is running under the "Debug Programs" user right on the server this is occuring on. (As configured under the identity tab, in dcomcnfg for MQSeries).
Bring up the Local Security Policy tool, click on 'Security Settings
->Local Policies->User Right Assignments', click on 'Debug Programs'
(See Q101366 for the list and their 'Display names'). Double click "Debug Programs", then Add your MQ userid into the list. |
|
| Back to top |
|
|
| Nathan |
| Posted: Tue Nov 25, 2003 5:41 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
| dcomcnfg has the correct user id listed. I added that ID to the Debug Program security Policy. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Nov 25, 2003 5:50 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
... and did it work?  |
|
| Back to top |
|
|
| Nathan |
| Posted: Tue Nov 25, 2003 5:54 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
Nope  I restarted the QMgr too, just hoping... Same error and FDC message. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Nov 25, 2003 6:06 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
You need to end any mmc snapins (Explorer, services) then restart the whole service, not just the qmgr. Try rebooting, it always cleans things out.
To be more specific, you need to restart amqmsrvn as this process token is the one the others inherit from. This only ends when all dcom processes using it end, and that includes all the MMC snapins (explorer, services) and the MQ service (including the taskbar and all qmgrs). |
|
| Back to top |
|
|
| Nathan |
| Posted: Tue Nov 25, 2003 6:23 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
I am sorry, I didn't tell you right. I restarted the service (QMgr of course goes with it). That didn't work.
But, I rebooted the system and BING! Worked like a charm 
You da man! Thanks very much for the assistance.
Could you explain why I had to do that? I will need to explain it to my Boss. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Nov 25, 2003 8:32 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
The problem is that MQ needs to open a process handle to do shared memory / IPC, and the process we are opening is a higher priviledge level than we are authorized to do (OpenProcess fails with r/c 5 (access_denied)).
Since we require this functionality you need to explicitly authorize the userid, which means give it the ability to open other processes regardless of security, and this is classified as "debug programs". |
|
| Back to top |
|
|
| Nathan |
| Posted: Tue Nov 25, 2003 8:38 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
| Thank you for the explanation and help. |
|
| Back to top |
|
|
| Nathan |
| Posted: Fri Nov 28, 2003 8:28 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
Here we go again. Different system.
I installed 5.3, the CSD and made the change to the local policy (just as I did with the last system like you helped me with).
I get the same access denied. The process it says that it can't open is DLLHOST.EXE
Now, I am confused. |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Nov 28, 2003 8:39 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Same FDC and exception? Whats the userid in the FDC, the probe and the callstack?
What o/s as well? |
|
| Back to top |
|
|
|
|
