TM1.ClientMessage Client could not be found.

[lotsaram]

Has anyone else noticed this error message in tm1server.log files for servers running 10.2 ? It presents in the message log in the following format
<threadID> [] ERROR <yyyy-mm-dd HH:mm:ss.iii> TM1.ClientMessage Client could not be found.

Once this error message presents in the tm1server.log file it repeats at regular intervals. If this error message is present then TM1 top connections are no longer possible. This affects not only tm1top but any other 3rd party product using the same top api for a monitoring session (e.g. Ops Console, Pulse, windows top, etc. also cannot connect).

The only fix seems to be to restart the TM1 instance, but that's hardly an acceptable solution in a production environment (neither is flying blind without a server activity monitor).

Any thoughts as to cause and how to fix gratefully accepted.

[BrianL]

I have heard of this.

I believe it's the same issue as PI30888. If it's the same issue, it's triggered by an IP address change on the system running the TM1 server which causes incorrect info to be sent to the admin server.

[lotsaram]

Thanks. Looks like the same issue. I guess the "fix" then is upgrade to 10.2.2 FP3