do you have file Windows file ACL in place. defining QL would involve 
creating file system object. does the service id has required access ?
 

        Alexander Gerasimenko 
                                        (a.k.a. Sasha) 
                                        AMI Interface Factory Manager 
                                        AMI Arhitecture 
                                        Application Messaging & 
Integration Team, ISW , *120, x.6629 
                                        Information Services 
International, (part of Mars Inc.) 
                                        DDI: +44 (0) 118 9446629 
                                        mobile: +44 (0) 7966920715 
                                        Mars Conference ID: 674567 
                                        mailto: 
[EMAIL PROTECTED] 
                                        web:   www.mars.com 
 
 
 
 





"Heggie, Peter" <[EMAIL PROTECTED]>
Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
10/01/2007 13:45
Please respond to MQSeries List



To:
MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
cc:




Subject:
Re: Not authorized on Win2003 after applying CSD13 



Thank you - That is correct, the CSD upgrade does not prompt or allow an 
ID to be supplied. The original install did, and I put in the MQ service 
domain ID at at that time. The MQ service runs under that ID with no 
problem. I did try adding that ID into the mqm group and deleting it and 
re-adding it to the administrators group, but there is no change. 
 
As a member of the local administrator group, I can stop and start the MQ 
service, and I can stop and start a queue manager. I can get into runmqsc 
with the specified queue manager name. But when I run a command, like 
define qlocal(TEST.TEST), I get an AMQ8101 - error 893. The FDC file shows 
1/10/2007  08:27:49
AMQ6119: An internal WebSphere MQ error has occurred (Access Violation at 
address 9894B22A when writing) . I am logged on as a local administrator, 
so I am confused about getting an Access Violation).

From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf 
Of [EMAIL PROTECTED]
Sent: Wednesday, January 10, 2007 4:03 AM
To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: Not authorized on Win2003 after applying CSD13


Hello Peter, 
did you use Domain ID as services ID before ?  I did not see that option 
during CSD upgrade. 
WHat about local mqm group membership , is your id part of it ?

        Alexander Gerasimenko 
                                        (a.k.a. Sasha) 
                                        AMI Interface Factory Manager 
                                        AMI Arhitecture 
                                        Application Messaging & 
Integration Team, ISW , *120, x.6629 
                                        Information Services 
International, (part of Mars Inc.) 
                                        DDI: +44 (0) 118 9446629 
                                        mobile: +44 (0) 7966920715 
                                        Mars Conference ID: 674567 
                                        mailto: 
[EMAIL PROTECTED] 
                                        web:   www.mars.com 





"Heggie, Peter" <[EMAIL PROTECTED]> 
Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT> 
09/01/2007 22:25 
Please respond to MQSeries List 



To: 
MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT 
cc: 





Subject: 
Not authorized on Win2003 after applying CSD13 




I am reluctant to ask for help on an 'older' release, and hopefully will
jump to v6 soon, but first - I just installed CSD13 on a Windows 2003
server, using a domain ID as the service's' userid, and now I am unable
to connect to the queue manager. I tried again by completely
uninstalling MQ from the server, rebooting the server, deleting all
files and folders in the c:\Program Files\IBM\WebsphereMQ directory,
re-installing MQ v5.3 (csd01) and then applying CSD03 over the top
(there were files in use - had to reboot that also). Still have the
error.

I had full functionality before the CSD install. Now I cannot connect
via MQ Explorer, and I can't use runmqsc to issue commands to the queue
manager.

I get an AMQ8135 Not authorized on the command line, and in the FDC
file, I see this:

| PIDS              :- 5724B4100
|
| LVLS              :- 530.13  CSD13
|
| Product Long Name :- WebSphere MQ for Windows
|
| Vendor            :- IBM
|
| Probe Id          :- XC130031
|
| Application Name  :- MQM
|
| Component         :- xehExceptionHandler
|
| Build Date        :- Dec 20 2006
|
| CMVC level        :- p530-13-L061220
|
| Build Type        :- IKAP - (Production)
|
| UserID            :- MQsrvc
|
| Process Name      :- C:\Program Files\IBM\WebSphere
MQ\bin\amqzlaa0.exe     |
| Process           :- 00004260
|
| Thread            :- 00000007
|
| QueueManager      :- MQLW001
|
| Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
|
| Minor Errorcode   :- OK
|
| Probe Type        :- MSGAMQ6119
|
| Probe Severity    :- 2
|
| Probe Description :- AMQ6119: An internal WebSphere MQ error has
occurred   |
|   (Access Violation at address 00000000 when reading)
|
| FDCSequenceNumber :- 0
|
| Comment1          :- Access Violation at address 00000000 when reading
|
|
|
|
|
+-----------------------------------------------------------------------
------+


zfuLocateSid rc=zrcF_NOT_FOUND

I can see that the service is running as the special domain ID. Perhaps
some security setting has been changed on my server without my knowledge
and this account cannot verify my login ID's credentials. But my login
ID is part of the local administrators group as well as the local mqm
group.

So I am puzzled. Could this be a problem with CSD13 ? Thanks in advance
for any help.

Peter Heggie


**** For your information: the Rhode Island Operations of New England Gas 
Company have been acquired by National Grid and are now doing business 
under that name.  ****


This e-mail and any files transmitted with it, are confidential to 
National Grid and are intended solely for the use of the individual or 
entity to whom they are addressed.  If you have received this e-mail in 
error, please reply to this message and let the sender know.



To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html




List Archive - Manage Your List Settings - Unsubscribe 
Instructions for managing your mailing list subscription are provided in 
the Listserv General Users Guide available at http://www.lsoft.com 

Attachment: jpgzjukSZTkSx.jpg
Description: JPEG image

Attachment: jpgGdoGE9fGxa.jpg
Description: JPEG image

Reply via email to