| Author |
Message
|
| FFSparky |
 Posted: Tue Jun 14, 2005 1:20 pm Post subject: Support pack MA7K - Win/NT Client Trigger Service |
 |
|
Novice
Joined: 23 Dec 2003
Posts: 16
Location: Des Moines, Iowa
|
Has anyone out in MQ world had problems with the Support pack MA7k -
Client Trigger Service?
I’m getting random issues where the service will try and trigger an
application but fails: “128 trying to start process.” A period of time
later I turn triggering off then back on to resend the trigger message and
it works.
The only information I can find is in the event viewer as I have looked
everywere else I can think of:
First the trigger service attempts to start the application:
Event Type: Information
Event Source: MQSeries Client Trigger Service
Event Category: None
Event ID: 259
Date: 5/20/2005
Time: 1:52:31 AM
User: N/A
Computer: JHWSPR13
Description:
Starting: c:\SysApps\mqclient\bin\mqftpr.exe
>>C:\SysApps\MQClient\mqftpr.log
"TM
C 2MQFTP.JHWSPR13
MQFTP.CLIENT
c:\SysApps\mqclient\bin\mqftpr.exe
>>C:\SysApps\MQClient\mqftpr.log
DQP0000 "
.
Data:
0000: 63 3a 5c 53 79 73 41 70 c:\SysAp
0008: 70 73 5c 6d 71 63 6c 69 ps\mqcli
0010: 65 6e 74 5c 62 69 6e 5c ent\bin\
0018: 6d 71 66 74 70 72 2e 65 mqftpr.e
0020: 78 65 20 3e 3e 43 3a 5c xe >>C:\
0028: 53 79 73 41 70 70 73 5c SysApps\
0030: 4d 51 43 6c 69 65 6e 74 MQClient
0038: 5c 6d 71 66 74 70 72 2e \mqftpr.
0040: 6c 6f 67 20 20 20 20 20 log
0048: 20 20 20 20 20 20 20 20
0050: 20 20 20 20 20 20 20 20
0058: 20 20 20 20 20 20 20 20
0060: 20 20 20 20 20 20 20 20
0068: 20 20 20 20 20 20 20 20
0070: 20 20 20 20 20 20 20 20
0078: 20 20 20 20 20 20 20 20
0080: 20 20 20 20 20 20 20 20
0088: 20 20 20 20 20 20 20 20
0090: 20 20 20 20 20 20 20 20
0098: 20 20 20 20 20 20 20 20
00a0: 20 20 20 20 20 20 20 20
00a8: 20 20 20 20 20 20 20 20
00b0: 20 20 20 20 20 20 20 20
00b8: 20 20 20 20 20 20 20 20
00c0: 20 20 20 20 20 20 20 20
00c8: 20 20 20 20 20 20 20 20
00d0: 20 20 20 20 20 20 20 20
00d8: 20 20 20 20 20 20 20 20
00e0: 20 20 20 20 20 20 20 20
00e8: 20 20 20 20 20 20 20 20
00f0: 20 20 20 20 20 20 20 20
00f8: 20 20 20 20 20 20 20 20
0100: 20 22 54 4d 43 20 20 20 "TMC
0108: 20 32 4d 51 46 54 50 2e 2MQFTP.
0110: 4a 48 57 53 50 52 31 33 JHWSPR13
0118: 20 20 20 20 20 20 20 20
0120: 20 20 20 20 20 20 20 20
0128: 20 20 20 20 20 20 20 20
0130: 20 20 20 20 20 20 20 20
0138: 20 20 4d 51 46 54 50 2e MQFTP.
0140: 43 4c 49 45 4e 54 20 20 CLIENT
0148: 20 20 20 20 20 20 20 20
0150: 20 20 20 20 20 20 20 20
0158: 20 20 20 20 20 20 20 20
0160: 20 20 20 20 20 20 20 20
0168: 20 20 20 20 20 20 20 20
0170: 20 20 20 20 20 20 20 20
0178: 20 20 20 20 20 20 20 20
0180: 20 20 20 20 20 20 20 20
0188: 20 20 20 20 20 20 20 20
0190: 20 20 20 20 20 20 20 20
0198: 20 20 20 20 20 20 20 20
01a0: 20 20 20 20 20 20 20 20
01a8: 20 20 20 20 20 20 63 3a c:
01b0: 5c 53 79 73 41 70 70 73 \SysApps
01b8: 5c 6d 71 63 6c 69 65 6e \mqclien
01c0: 74 5c 62 69 6e 5c 6d 71 t\bin\mq
01c8: 66 74 70 72 2e 65 78 65 ftpr.exe
01d0: 20 3e 3e 43 3a 5c 53 79 >>C:\Sy
01d8: 73 41 70 70 73 5c 4d 51 sApps\MQ
01e0: 43 6c 69 65 6e 74 5c 6d Client\m
01e8: 71 66 74 70 72 2e 6c 6f qftpr.lo
01f0: 67 20 20 20 20 20 20 20 g
01f8: 20 20 20 20 20 20 20 20
0200: 20 20 20 20 20 20 20 20
0208: 20 20 20 20 20 20 20 20
0210: 20 20 20 20 20 20 20 20
0218: 20 20 20 20 20 20 20 20
0220: 20 20 20 20 20 20 20 20
0228: 20 20 20 20 20 20 20 20
0230: 20 20 20 20 20 20 20 20
0238: 20 20 20 20 20 20 20 20
0240: 20 20 20 20 20 20 20 20
0248: 20 20 20 20 20 20 20 20
0250: 20 20 20 20 20 20 20 20
0258: 20 20 20 20 20 20 20 20
0260: 20 20 20 20 20 20 20 20
0268: 20 20 20 20 20 20 20 20
0270: 20 20 20 20 20 20 20 20
0278: 20 20 20 20 20 20 20 20
0280: 20 20 20 20 20 20 20 20
0288: 20 20 20 20 20 20 20 20
0290: 20 20 20 20 20 20 20 20
0298: 20 20 20 20 20 20 20 20
02a0: 20 20 20 20 20 20 20 20
02a8: 20 20 20 20 20 20 20 20
02b0: 20 20 20 20 20 20 20 20
02b8: 20 20 20 20 20 20 20 20
02c0: 20 20 20 20 20 20 20 20
02c8: 20 20 20 20 20 20 20 20
02d0: 20 20 20 20 20 20 20 20
02d8: 20 20 20 20 20 20 20 20
02e0: 20 20 20 20 20 20 20 20
02e8: 20 20 20 20 20 20 20 20
02f0: 20 20 20 20 20 20 20 20
02f8: 20 20 20 20 20 20 20 20
0300: 20 20 20 20 20 20 20 20
0308: 20 20 20 20 20 20 20 20
0310: 20 20 20 20 20 20 20 20
0318: 20 20 20 20 20 20 20 20
0320: 20 20 20 20 20 20 20 20
0328: 20 20 20 20 20 20 20 20
0330: 20 20 20 20 20 20 20 20
0338: 20 20 20 20 20 20 20 20
0340: 20 20 20 20 20 20 20 20
0348: 20 20 20 20 20 20 20 20
0350: 20 20 20 20 20 20 20 20
0358: 20 20 20 20 20 20 20 20
0360: 20 20 20 20 20 20 20 20
0368: 20 20 20 20 20 20 20 20
0370: 20 20 20 20 20 20 20 20
0378: 20 20 20 20 20 20 20 20
0380: 20 20 20 20 20 20 20 20
0388: 20 20 20 20 20 20 20 20
0390: 20 20 20 20 20 20 20 20
0398: 20 20 20 20 20 20 20 20
03a0: 20 20 20 20 20 20 20 20
03a8: 20 20 20 20 20 20 44 51 DQ
03b0: 50 30 30 30 30 20 20 20 P0000
03b8: 20 20 20 20 20 20 20 20
03c0: 20 20 20 20 20 20 20 20
03c8: 20 20 20 20 20 20 20 20
03d0: 20 20 20 20 20 20 20 20
03d8: 20 20 20 20 20 20 22 20 "
03e0: 20 20 20 20 20 20 20 20
03e8: 20 20 20 20 20 20 20 20
03f0: 20 20 20 20 20 20 20 20
03f8: 20 20 20 20 20 20 20 20
0400: 20 20 20 20 20 20 20 20
0408: 20 20 20 20 20 20 20 20
0410: 20 20 20 20 20 20 20 20
0418: 20 20 20 20 20 20 20 20
0420: 20 20 20 20 20 20 20 20
0428: 20 20 20 20 20 20 20 20
0430: 20 20 20 20 20 20 20 20
0438: 20 20 20 20 20 20 20 20
0440: 20 20 20 20 20 20 20 20
0448: 20 20 20 20 20 20 20 20
0450: 20 20 20 20 20 20 20 20
0458: 20 20 20 20 20 20 20 20
0460: 00 .
I then fails and the following is logged:
Event Type: Warning
Event Source: MQSeries Client Trigger Service
Event Category: None
Event ID: 260
Date: 5/20/2005
Time: 1:52:31 AM
User: N/A
Computer: JHWSPR13
Description:
Error 128 trying to start process. (See "Data:" for process string)
Data:
0000: 20 20 20 20 20 20 20 20
0008: 20 20 20 20 20 20 20 20
0010: 20 20 20 20 20 20 20 20
0018: 20 20 20 20 20 20 20 20
0020: 20 20 20 20 20 20 20 20
0028: 20 20 20 20 20 20 20 20
0030: 20 20 20 20 20 20 20 20
0038: 20 20 20 20 20 20 20 20
0040: 20 20 20 20 20 20 20 20
0048: 20 20 20 20 20 20 20 20
0050: 20 20 20 20 20 20 20 20
0058: 20 20 20 20 20 20 20 20
0060: 20 20 20 20 20 20 20 20
0068: 20 20 20 20 20 20 20 20
0070: 20 20 20 20 20 20 20 20
0078: 20 20 20 20 20 20 20 20
Thanks
Greg |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jun 14, 2005 4:53 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I am going to guess that your app is getting called *too* often, and is contending with itself, and thus returning a bad return code from exit - and thus causing the Trigger Monitor to think that it failed.
Or for some other reason returning a bad code and causing the trigger monitor to think it failed.
Some guy wrote a FAQ about trigger programs. It might be helpful to review.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| FFSparky |
| Posted: Wed Jun 15, 2005 5:38 am Post subject: |
|
|
Novice
Joined: 23 Dec 2003
Posts: 16
Location: Des Moines, Iowa
|
| That's a good theory but It's happening when only one trigger occurs in a given hour and I know nothing else MQSeries or application related is running. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jun 15, 2005 6:38 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Error 128 is a bit of a strange one:
"There are no child processes to wait for. "
Is there anything interesting that your program does? (does it use threads or anything unique)? |
|
| Back to top |
|
|
| FFSparky |
| Posted: Wed Jun 15, 2005 7:08 am Post subject: |
|
|
Novice
Joined: 23 Dec 2003
Posts: 16
Location: Des Moines, Iowa
|
| Sorry to report, it's a very simple application that just reads messages off the queue and writes them to a unique file. There's no threading involved. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jun 15, 2005 8:01 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Is this the only application you trigger with Ma7k? If not, can I assume you don't get this error on any other app?
Can you also post you version of Windows and MQ client you are using?
(ie Win2k SP ??) |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jun 15, 2005 9:21 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 15, 2005 9:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's probably actually cause 1 on that page, rather than cause 2.
| Quote: |
| The executed process does not have proper security access to the window station and desktop associated with the process. |
I wonder if in the app it tries to display an error using ShowMessage or whatever it's called. Again, the "Allow Service to Interact with the Desktop" switch is a good thing to check.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jun 15, 2005 9:27 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Yes, but he says it fails randomly ..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 15, 2005 9:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wschutz wrote: |
| Yes, but he says it fails randomly ..... |
It's probably an infrequently hit error condition - like a temporary failure to connect to a database or something.
Poor code is much more likely than random failures.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| FFSparky |
| Posted: Wed Jun 15, 2005 11:04 am Post subject: |
|
|
Novice
Joined: 23 Dec 2003
Posts: 16
Location: Des Moines, Iowa
|
Boy step away for a period (darn meetings) and return to some good stuff ;^)
Ok for the record:
I have this support pack installed on roughly 20 Windows servers and as best I can tell this problem is isolated to only one system.
Windows OS level is: Windows 2003 Server Enterprise Edition with Service Pack 1 applied.
IIS is also running on this server as this is one of the production internal web servers.
MQSeries Level is: Version 5.3 with CSD06 applied
The Client Trigger Service setup was:
Global:
ShortTmr=60
ShortRty=10
LongTmr=1200
LongRty=999999999
EventLevel=2
WaitInterval=60000
MQSeriesDLL=mqic32.dll
* This defines a thread to read from a initq on qmgr "QMGR?????"
Thread:
TriggerQueueName=JHWSPR13.INITQ
TriggerQueueMgrName=DQP0000
There are currently only two triggered applications:
DEFINE PROCESS ('TDEX') REPLACE +
DESCR('Tdex applicatioin') +
APPLTYPE(WINDOWSNT) +
APPLICID('D:\Apps\TDE\TDex\RunTdex.cmd') +
USERDATA(' ') +
ENVRDATA(' ')
DEFINE PROCESS ('MQFTP.CLIENT') REPLACE +
DESCR('MQFTP for Windows NT Clinets with the client directory-
on C:') +
APPLTYPE(WINDOWSNT) +
APPLICID('c:\SysApps\mqclient\bin\mqftpr.exe') +
USERDATA(' ') +
ENVRDATA(' ')
Both of these are fairly basic applications. MQFTP is used for file transfers (basically read messages off a queue and write to a file). TDEX is a visual basic application and this one does access a Sybase data base.
I have received the dreaded "128 trying to start process" for both applications it's more common with the MQFTP application. And while I would love it to be "poor code", MQFTP is a high usage enterprise application on a high percentage of the other 20 servers outlined above.
Through my debugging, I had come to the conclusion it's something with this particular servers environment and I have had my windows technical staff looking into this however they are currently "clueless" hence my post, .
I will read through the above information provided and will continue to welcome any other insights as It's frustrating to get 02:00 wake up calls to resolve production problems by simply turning triggering off and back on again. I'm very close to having the windows support staff do this in hopes it will force them to dig deeper into finding the problem.
Thanks!
Greg |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 15, 2005 11:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Try changing your applicid to 'start c:\SysApps\mqclient\bin\mqftpr.exe' or 'start D:\Apps\TDE\TDex\RunTdex.cmd' and see what happens.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jun 15, 2005 3:47 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Greg, Im aware of another customer that is also "occassionally" getting a 128 return code from triggering a process via trigsvc.exe. Since its only happening on one machine, you should consider whether something is also running on that particular server that is using up the heap. I really sugggest you have your Windows support folks look at the article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;184802
-Wayne (Ma7K author) |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Jun 16, 2005 1:05 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Just to add a comment, whilst debugging problems reported by customers on MQ, every time I have come across a r/c 128 trying to launch apps, its caused by the desktop heap issue. Does the machine suffering from it have eg. more qmgrs on it, or more services active on it?
One way to see if its likely to be the cause, is if you have one of these say every other day, just as an experiment stop the trigger service and run the monitor from the command line instead. DONT LOG OFF, but leave it for eg. 4 days to see if the problem occurs. Chances are it wont, and then that just cuts it down to either a security issue or a desktop heap issue |
|
| Back to top |
|
|
| FFSparky |
| Posted: Thu Jun 16, 2005 5:46 am Post subject: |
|
|
Novice
Joined: 23 Dec 2003
Posts: 16
Location: Des Moines, Iowa
|
All,
Thanks again for your input. I have forwarded the Microsoft Support article to my Windows supoprt team to look into.
Thanks again for your help!
-Greg |
|
| Back to top |
|
|
|
|
