Hi Glen, Yes that should work for a testing / developer PC.
An 'IBM WMQ person' emailed me and said this was a known issue. They said that there is a workaround: 'put the musr_mqadmin account into the administrators group.' They also said that an upgrade may delete and recreate the musr_mqadmin account, hence, you may need to repeat the process. I have not tried it as I'm back on WMQ v5.3. Since, I am on contract at a client site, I cannot spend any more time on it. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz On Wed, 19 Sep 2007 08:46:11 -0600, Glen Larson <[EMAIL PROTECTED]> wrote: > Roger, > > I see you really don't care about security and are using these qmgrs for > testing. So there is a way to avoid the security checks. While I do not > recommend this for general use, it sounds like you just need these qmgrs > for testing. > > After creating the qmgr, make sure it is stopped, then edit the registry > and remove the Authorization Service key associated with the qmgr. > > HKEY_LOCAL_MACHINE -> SOFTWARE -> IBM -> MQSeries -> Current Version -> > Configuration -> QueueManager -> qmgr-name -> Service -> > AuthorizationService > > Then restart the qmgr. > > > > Glen Larson > Lead System Engineer > Middleware Support > Progressive Insurance > 719-660-4717 cell > 719-432-3102 work > and 762-3102 network > > > > Roger Lacroix <[EMAIL PROTECTED]> > Sent by: MQSeries List <[email protected]> > 09/18/2007 11:58 AM > Please respond to > MQSeries List <[email protected]> > > > To > [email protected] > cc > > Subject > Re: WMQ v6 and Windows local install problems > > > > > > > All, > > Well, after going through the 20-questions at the client site, and them > wondering if / how this would affect DEV/QA/ PROD, the answer back was no > to adding my local musr_mqadmin to domain controller (AD). > > So, the simplest thing was to uninstall WMQ v6.0.2.2, delete the MQ UserId > and groups and reboot. I logged in as the local Administrator, installed > WMQ v5.3, reboot, applied CSD13 and reboot. > > I then logged in under my domain account, added it to the mqm group and > started MQ Explorer. I created 2 queue managers, added test queues and > test channels and now I am back where I was last Thursday morning. > > I need a functioning queue manager (any recent version) to do development > and testing work while at a client site. I don't need the latest and > greatest. And yes, I know it will not be supported by IBM in 12 days but > who cares, a working queue manager is better than a non-working queue > manager. > > I don't know what IBM has changed, or what was updated, but WMQ v6 most > certainly acts differently when logging in locally with a domain account > vs how WMQ v5.3 worked. > > > Regards, > Roger Lacroix > Capitalware Inc, > > > At 06:07 PM 9/13/2007, you wrote: > All, > > Well, today's been a bad MQ day. It started off with such promise then > went straight into the gutter. > > Help... Please help. > > This morning I decided to upgrade MQ on a PC at a client site from WMQ > v5.3 CSD13 to WMQ v6. Since I had 3 queue managers that I wanted to keep, > I thought the simplest and easiest thing to do is to uninstall WMQ v5.3 > then install WMQ v6. Of course, since I have install WMQ v6 at least 20 > times, it never even occurred to me to take a backup first (and of course, > Murphy bite me right the @ss). > > So I did the following: > - Uninstalling WMQ v5.3 > - rebooted > - Installed WMQ v6 and selected local account (not domain) > - reboot > - Started MQ Explorer > - Created a test queue manager and as it is trying to define a listener, I > get 2035 (not authorized). > - I checked via runmqsc and sure enough 2035. > - Stopped and deleted the test queue manager. > - I stop the MQ Services > - I check that my account is in the mqm group and it is (it is in the > Admin group too). > - I start 'Prepare WebSphere MQ Wizard' and it complains about MQ not > having authority to 'query information about your user account'. It wants > a domain account for MQ. I go 'say what'. > > Figuring I messed something up in the install, I decide to uninstall > everything and start again. I did and it makes absolutely no difference. > > The event viewer has a bunch of the following messages: > > "Access was denied when attempting to retrieve group membership > information for user '[EMAIL PROTECTED]'. > WebSphere MQ, running with the authority of user > '[EMAIL PROTECTED]', was unable to retrieve group membership > information for the specified user. > Ensure Active Directory access permissions allow user > '[EMAIL PROTECTED]' to read group memberships for user > '[EMAIL PROTECTED]'. To retrieve group membership information for a > domain user, MQ must run with the authority of a domain user." > > So, I figured I must have a old setting that is conflicting with WMQ v6. > So, uninstall WMQ v6, delete everything under {WMQ_Install_Dir}, go delete > the 'mqm' group and 'MUSR_MQADMIN' service account. I even made sure the > registry was clean. > > Next I shut the PC off, unplug the network cable, started it up again and > logged in as 'Administrator'. > > I did the following: > - Installed WMQ v6 and selected local account (not domain) > - reboot > - Started MQ Explorer > - Created a test queue manager and it worked perfectly > - Stopped and deleted the test queue manager > > Turned off the PC, plugged in the network cable, started it and logged in > with my domain account. I immediately added my domain account to the > local mqm group. > > I did the following: > - Started MQ Explorer > - Created a test queue manager and as it is trying to define a listener, I > get 2035 (not authorized). > > Ahhhhhhhhhhhhh and screamed at the moon. > > Logged off as domain user and logged in as 'Administrator' and everything > works. > > I even applied v6.0.2.2 (logged in as Administrator) and I still get the > problem when I log in with my domain account. > > Interesting item: > > - Under local 'Administrator' account if I start 'Prepare WebSphere MQ > Wizard' it says local setup (No network) > > - Under my domain UserId account if I start 'Prepare WebSphere MQ Wizard' > and it complains about MQ not having authority to 'query information about > your user account'. It wants a domain account for MQ. > > > Why is MQ insisting on checking my domain UserId against the domain when I > installed / configured MQ as a local setup. It never did this under WMQ > v5.3. > > How can I force it to only look locally? (My domain account is in the > local mqm group.) > > I've wasted a whole day on this when it should have been 30 minutes. And > now I don't even have a working MQ environment on my PC (under domain > UserId that is). > > Help! Anyone please. > > > Regards, > Roger Lacroix > Capitalware Inc. > http://www.capitalware.biz > > 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 > > 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 > > 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
