Author |
Message
|
kvranjan10 |
Posted: Wed Aug 19, 2009 2:43 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
Hi Exerk
Thanks for your support. I tried giving quotes still not working..
Actually this is very urgent.
Hi Aggarwal,
Sorry for saying this if we give
Start Command : runmqtrm -m TESTQM -q initq -- service itself not starting.... |
|
Back to top |
|
 |
exerk |
Posted: Wed Aug 19, 2009 2:50 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
So is there anything in the logs? Any FDC's? Anything in EventVwr? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
aditya.aggarwal |
Posted: Wed Aug 19, 2009 2:54 am Post subject: |
|
|
 Master
Joined: 13 Jan 2009 Posts: 252
|
in my case it is working.
bounce your queue manager and start it. i believe that OLD TM process is still stuck with your queue manager.
also after restarting the queue manager check if SERVICE is running or not!
Best Regards,
Aditya |
|
Back to top |
|
 |
kvranjan10 |
Posted: Wed Aug 19, 2009 3:05 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.4 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XC381001 |
| Application Name :- MQM |
| Component :- xcsDisplayMessageForSubpool |
| SCCS Info :- lib/cs/amqxeida.c, 1.52.1.23 |
| Line Number :- 3448 |
| Build Date :- May 12 2008 |
| CMVC level :- p600-204-080509 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\Program Files\IBM\WebSphere MQ\bin\amqzmur0.exe |
| Addressing mode :- 32-bit |
| Process :- 00005524 |
| Thread :- 00000002 |
| ConnId(1) IPCC :- 10 |
| ConnId(2) QM :- 10 |
| Major Errorcode :- zrcX_TASK_STARTED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ5037 |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: MQM could not display the text for error |
| 20535. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1 1 |
| Arith2 :- 5524 1594 |
| Comment1 :- ERROR-LOG
---------------------------------------
This is the only FDc created today and in the qmgr errors i found this
8/19/2009 06:37:08 - Process(7564.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
AMQ5019: Unable to access program 'D:\Program Files\IBM\WebSphere
MQ\bin\runmqtrm -m TESTQM -q initq'.
EXPLANATION:
A request was made to execute the program D:\Program Files\IBM\WebSphere
MQ\bin\runmqtrm -m TESTQM -q initq, however the operation was unsuccessful
because the program could not be found in the specified location.
ACTION:
Check the definition of the service specifies the correct and full path to the
program to run. If the path is correct then verify that the program exists in
the specified location and that WebSphere MQ userid has permission to access
it.
May be bcoz it is unable to find the location? |
|
Back to top |
|
 |
kvranjan10 |
Posted: Wed Aug 19, 2009 3:11 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
Hi Exerk,
I tried copying the runmqtrm.exe to some other location and tried but still not working..
Could you please tell me how to check whether the MUSR_MQADMIN has access to that particular folder? |
|
Back to top |
|
 |
exerk |
Posted: Wed Aug 19, 2009 3:14 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
No, it's because it is reading runmqtrm -m TESTQM -q initq as being the program name.
The Restartable Process Manager coughed the FDC. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
exerk |
Posted: Wed Aug 19, 2009 3:15 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Do as suggested and bounce the queue manager, then start from scratch if that doesn't cure it. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
kvranjan10 |
Posted: Wed Aug 19, 2009 3:45 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
I restarted and recreated everything and tested. But still not working.
In Start command if i am giving complete command like
runmqtrm -m TESTQM -Q initq the service is not starting... |
|
Back to top |
|
 |
kvranjan10 |
Posted: Wed Aug 19, 2009 3:47 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
Am i missing out any properties or the way iam trying is correct? |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Aug 19, 2009 3:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
put the *arguments* to the STARTCMD in the STARTARGs parameter. |
|
Back to top |
|
 |
exerk |
Posted: Wed Aug 19, 2009 3:54 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
mqjeff wrote: |
put the *arguments* to the STARTCMD in the STARTARGs parameter. |
kvranjan10 did originally, but someone 'helpfully' suggested putting the whole lot in the Start Command: field  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
kvranjan10 |
Posted: Wed Aug 19, 2009 4:10 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
i kept the arguments in
-m TESTQM -q initq in startargs
and the command runmqtrm in start command
But still not working...This thing i tried from the morning. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Aug 19, 2009 4:57 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20767 Location: LI,NY
|
Maybe it's not liking the path. Have you tried with the short version of the path?
What I mean with short version is instead of Program Files using Progra~1 ... or the equivalent on your system (dir /x). And this for each segment of the path.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
kvranjan10 |
Posted: Wed Aug 19, 2009 5:06 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2008 Posts: 29
|
I tried this one also...but no clue... |
|
Back to top |
|
 |
gunter |
Posted: Wed Aug 19, 2009 5:26 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004 Posts: 307 Location: Germany, Frankfurt
|
kvranjan10 wrote: |
If i am running manually through command prompt its working fine... |
If the trigger monitor is running with a user not logged in, the process and processes started by it are not connected with the interactive session and hence they cannot open a window.
Redirect the output in test.bat (p.e. echo ... > path\datei.log) to a file. Make sure the user is able to write. _________________ Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
Back to top |
|
 |
|