Page 1 of 1
TM1.ClientMessage Job ID does not match
Posted: Tue Jul 12, 2011 1:40 pm
by dan.kelleher
Hi,
After running a TI process which itself kicks off a series of nested TI processes, my screen freezes and I get no confirmation of success or failure.
The process just hangs.
However, when I check the log files and kill architect, the process has completed, but the following entry has been added to the message log:
TM1.ClientMessage Job ID does not match
Any ideas?
Thanks,
Dan
Re: TM1.ClientMessage Job ID does not match
Posted: Mon Jan 28, 2013 9:12 pm
by mberson
Did you ever get a resolution on this? I'm having similar behavior in a new Citrix environment.
Re: TM1.ClientMessage Job ID does not match
Posted: Mon Jan 28, 2013 9:23 pm
by moby91
Regarding the error message "TM1.ClientMessage Job ID does not match" in the TM1 server mesage logfile tm1server.log, are you aware of the IBM Technote 1572613 ?
http://www-01.ibm.com/support/docview.w ... wg21572613
What is causing the error message "Job ID does not match" in the TM1 server message logfile tm1server.log ?
Re: TM1.ClientMessage Job ID does not match
Posted: Tue Jan 29, 2013 3:40 am
by mberson
Yes - the issue is actually that the chore or process progress messages get hung up and never advance to "Chore Completed Successfully".
The TM1Server log shows that the chore or process has completed, but this is never communicated to the client. When the client tries to cancel, the TM1Server log message shows TM1.ClientMessage Job ID does not match because the job being cancelled has actually completed.
The question is - why isn't the client properly updated with the chore or process status? I've seen this at a couple of sites now and seems to only occur over Citrix clients.
Re: TM1.ClientMessage Job ID does not match
Posted: Tue Jun 11, 2013 7:15 pm
by mvaspal
Hi
Has anybody ever found a solution for this?
Thanks
Re: TM1.ClientMessage Job ID does not match
Posted: Mon Aug 18, 2014 11:53 am
by mvaspal
Hi
Just wanted to ping this thread, maybe somebody has solved this since then? Process completes successfully but the message does not come through. Of course we cannot steadily reproduce the issue...
v10.1.1 FP2
Would be also good to know whether anybody experienced this with 10.2.2 as we plan to upgrade from 10.1.1
Thanks