| Author |
Message
|
| aboggis |
 Posted: Fri Jan 19, 2007 2:21 pm Post subject: Configuring WMQ6 via Microsoft Remote Desktop connection. |
 |
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I have WMQ 6.0.2 installed on a Windows Server 2003 machine. Installation was successful and service runs.
I followed the guides for configuring user ids, etc.
Now, when I connect as a user via Remote Desktop, I can create (crtmqm) and configure (runmqsc) queue managers. However, when I log off as a user (even if I was logged on as Administrator), as you might expect, all my user processes are terminated, so any queue manager that I created "ends unexpectedly". Even if I restart the service, the new queue manager(s) that I set to auto-start do not.
So, my question is, what's the trick to using Remote Desktop? |
|
| Back to top |
|
 |
| pathipati |
| Posted: Sat Jan 20, 2007 5:41 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| How did you set your queue manager to default QM?Did you see any thing different if you directly control your machine instead of remote desktop? |
|
| Back to top |
|
|
| aboggis |
| Posted: Sat Jan 20, 2007 5:58 pm Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I didn't set the created queue manager to default. I did set it to auto-start (and it's listener).
I don't (at the moment) have the ability to log on to the machine locally (it's 50 miles away). I'm going to try things through a telnet client on monday to see if it makes a difference. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jan 21, 2007 6:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Try starting the queue manager from MQ Explorer, rather than the command line.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| aboggis |
| Posted: Sun Jan 21, 2007 10:47 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
Makes no difference. I can only control the queue manager (either via command line or via Explorer) whilst my remote desktop session is active. I can connect (and manage) to the running queue manager remotely or locally when it's running.
However, disconnecting from the remote desktop, ends all active processes that I stared during that session.
Even if I create the queue manager, set it to autostart with MQ, stop the queue manager then restart the MQ service, the queue manager I just created doesn't start - this is because Terminal Services, does not pass through all registry changes made in a session to the system registry.
Now I know people out there must use remote desktop/terminal services to remotely manage MQ on Windows. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Jan 22, 2007 1:21 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
aboggis,
This is very interesting to me. Did you do the original installation via Remote Desktop (I'm assuming yes, due to the geography you mentioned).
Your statement:
| Quote: |
| I can connect (and manage) to the running queue manager remotely or locally when it's running. |
Do you mean that you can connect from your local desktop via Eclipse to the 50-miles-away queue manager?
Can you use Eclipse on your local desktop to create a queue manager on the faraway machine? And does is auto-start properly?
I actually have not tried this yet, but I think you have inspired me to do so soon.
Shirley |
|
| Back to top |
|
|
| MQALearner |
| Posted: Mon Jan 22, 2007 1:38 pm Post subject: |
|
|
Newbie
Joined: 10 Jun 2006
Posts: 9
|
Hi
if its windows 2003 and MQ Ver 6.0.2
have you tried to use this "amqmdain AUTO QMGR" |
|
| Back to top |
|
|
| aboggis |
| Posted: Mon Jan 22, 2007 4:24 pm Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
Yes. Tried that.
| Quote: |
C:\Program Files\Support Tools>strmqm TEST
WebSphere MQ queue manager 'TEST' starting.
5 log records accessed on queue manager 'TEST' during the log replay phase.
Log replay for queue manager 'TEST' complete.
Transaction manager state recovered for queue manager 'TEST'.
WebSphere MQ queue manager 'TEST' started.
C:\Program Files\Support Tools>amqmdain auto TEST
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Initialization of resource 'amqmsrvn' failed, rc=0x8000401a
The server process could not be started because the configured identity is incorrect. Check the username and password. |
Any clues? |
|
| Back to top |
|
|
| mapa |
| Posted: Tue Jan 23, 2007 6:19 am Post subject: Related: Remote desktop console option |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
|
| Back to top |
|
|
| rtsujimoto |
| Posted: Tue Jan 23, 2007 8:20 am Post subject: |
|
|
Centurion
Joined: 16 Jun 2004
Posts: 119
Location: Lake Success, NY
|
| I have V6.0.1.1 on Windows 2003 and I used Remote Desktop for defining and managing purposes. But, I login using a local userid. Did you try that? |
|
| Back to top |
|
|
| MQALearner |
| Posted: Tue Jan 23, 2007 9:10 am Post subject: |
|
|
Newbie
Joined: 10 Jun 2006
Posts: 9
|
[img]C:\Program Files\Support Tools>amqmdain auto TEST
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Initialization of resource 'amqmsrvn' failed, rc=0x8000401a
The server process could not be started because the configured identity is incorrect. Check the username and password.[/img]
I got the same error at one time. but i don’t recall exactly what i did. but its related to your domain account. check with the startup services(IBM MQ SERVICES) and DCOMCNFG and also in Task manager
make sure all the services are running with one account and that account should be the part of mqm and domain account(if needed)
reply with your result will be appreciated |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Jan 23, 2007 11:08 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
|
| Back to top |
|
|
| aboggis |
| Posted: Tue Jan 23, 2007 11:37 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
Yes. I had. And it didn't seem to resolve our issue.
However, I repeated the "Prepare MQ Wizard", and we created an explicit MQ user ID, "MQuser", in the domain and just gave it the necessary (documented) permissions. It doesn't have any interactive login rights or anything like that.
After doing that the issue remained. However, restarting the machine (not just restarting the MQ service) seemed to provide some measure of fix. There's still some quirks, but it's better... |
|
| Back to top |
|
|
|
|
