| Author |
Message
|
| anthony.barnes |
 Posted: Tue Dec 20, 2005 7:15 pm Post subject: 5.3.7 install on XP 2003 is messing with my head |
 |
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
I'm about ready to loose it with this one...
After the successful install of 5.3.7 on a windows 2003 server SP1 I am having some issue creating and connecting to a queue manager.
I have been told that this windows server is a standalone server in its own workgroup and not part of any domain. I have validated that the Computer Name tab under My Computer properties does show it in a workgroup. With this information I am under the impression that I do NOT need to worry about a domain level account. With that being said...
If I use the MQ Explorer tool to create a queue manger with the name 'EAIESP1' I am unable to connect to it (via MQ Exp). When I try I get an error dialog stating "Unknown Error". If I create a qmgr with the exact same settings but name it 'EAIES' then all is good. I can connect, create objects, etc.
To further confuse the issue if I create everything from the command line (using crtmqm and runmqsc) with the qmgr name of 'EAIESP1' I can continue to access the qmgr from the command line but MQExp still throws that error. However upon restarts of the MQ Servie I loose the Channel Int and Listener settings. Have to delete and recreate those.
I have also been able to create and connect to qmgrs with names like 'TESTTEST7' without any issues.
Anyone have a clue at what might be going on here?
I'm happy to provide any additional troubleshooting data. I would just REALLY like to know what is happening here. I keep looking for the Candid Camera guy... |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 20, 2005 7:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Um.
First, upgrade to CSD 11.
Second, check for errors in the Application Log that correspond with your errors in MQExplorer.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 20, 2005 8:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Loosing the listener settings smacks more of CSD06 behavior than CSD07.
Did you reboot the PC after the install ?
Like Jeff said, if it isn't for production compatibility you should upgrade to the latest CSD or even to WMQ version 6 refresh pack 1.
 |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Tue Dec 20, 2005 8:35 pm Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
| jefflowrey wrote: |
Um.
First, upgrade to CSD 11.
Second, check for errors in the Application Log that correspond with your errors in MQExplorer. |
OK. Fair enough. I have completed the upgrade. mqver now reporting 530.11
Using MQExp I create a qmgr named 'EAIESP1' with the default settings.
It completed but when I click on it with in MQExp I get a hung and unresponsive MQExp. If I close the MQExp window I get the error dialog to send to MS. When I try to bring MQExp up again... I get nothing. The MMC wont come up. Running dspmq shows my new qmgr running. Kind of the same thing when I try with runmqsc. Its hung... I have to ctrl-c to exit.
Reboot seems to help some. Now MQExp comes up. Connection attempts to EAIESP1 return with "Access not authorized. You are not authorized to perform this operation. (AMQ4036). Trying the same qmgr from runmqsc returns with "AMQ8135: Not authorized". I am using a local account that is a member of the local admin and mqm groups. I used this same account to install and set up this qmgr. This server is not part of a domain.
I continue to not have any issue connecting to my shorter named qmgr 'EAIES'.
The qmgr error log's latest entry is show below. It was a minute or two before my connection attempt. There does not appear to be an error thrown into this log for that attempt.
----- amqzfubn.c : 3587 -------------------------------------------------------
12/21/2005 05:26:42
AMQ7227: WebSphere MQ encountered the following network error: The stub received bad data.
EXPLANATION:
MQ failed to successfully complete a network operation due to the specified error.
ACTION:
Ensure that your network is functioning correctly.
----- amqzfubn.c : 3587 ------------------------------------------------------- |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 20, 2005 8:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Not authorized is a bizarre one.
You could try and rerun the initialization wizard. This makes sure that the service account has the right password etc...
Remember that WMQ does not like embeded group resolutions ...
Hope this helps some.
|
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Tue Dec 20, 2005 9:15 pm Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
| fjb_saper wrote: |
Not authorized is a bizarre one.
You could try and rerun the initialization wizard. This makes sure that the service account has the right password etc...
Remember that WMQ does not like embeded group resolutions ...
Hope this helps some.
|
Thanks for the follow up fjb. The groups are nice and straight forward; administrators and mqm.
As far as rerun of the init wizard... you mean reinstall from my CDs or the Prepair MQ Wizard? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 20, 2005 9:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Just the prepair MQ Wizard.
Make sure your userid is part of the groups (mqm, admin) and not a group your userid is member of being part of those groups.
Enjoy |
|
| Back to top |
|
|
|
|
