MT Collector: Failed updating entry

Hello,

we upgraded to 8.5 recently (from 7.0.2) and receive an error message of the mt collector process frequently. OS is Windows Server 2k8.

Looks like this:

21.04.2009 17:17:01 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OFE6E08A2A.FBC2F789-ONC125759F.00535417 & [inrcp]=ISpy on office08@OBJENTIS: No documents found

21.04.2009 17:17:01 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OFF57A1EB0.3C7C1CA4-ONC125759F.005353A9 & [inrcp]=ISpy on office08@OBJENTIS: No documents found

21.04.2009 17:17:01 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OF1F541A20.0D3CBF29-ONC125759F.0053608F & [inrcp]=ISpy on office08@OBJENTIS: No documents found

21.04.2009 17:17:01 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OFF70D97CB.D7E86978-ONC125759F.005360F2 & [inrcp]=ISpy on office08@OBJENTIS: No documents found

21.04.2009 17:17:01 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OF1BD0DBE3.723B467F-ONC125759F.00536B7F & [inrcp]=ISpy on office08@OBJENTIS: No documents found

I tried removing all .mtc files and recreating the mtstore.nsf, reindexing and so on but without any success.

Does anyone have an idea? Its quite annoying.

Greetings from Vienna,

Bernhard Klemenjak

Subject: Message data could not be found

These errors are due to the fact that messaging data could not be found in the mtstore database. The router logs message tracking data in two parts (arrival and delivery or transfer). Delivery or transfer can be success or failure. The arrival logging is to show that a message made it to the server, the router then acts on that message and logs the action so that the messaging data can be updated.

In your case, the arrival data could not be found. It is unclear why that has happened. Does the error always involve “ISpy on office08”? Are there any other MT Collector errors in the log? Without having the MTC data and MTStore.nsf it is hard to troubleshoot. If you opened a support incident and provided your data we could replay the data and might track it down.

Subject: I have the same issue

Have you found why that error message appear?

Subject: glad to hear that we’re not alone with this issue

Sadly, we haven’t found a solution yet.

Thanks to David for the informations, there are no other MTC errors and it is not only with “ISpy on office08”. Because I’m currently short at time i wasn’t able to post here regarding this issue, so my answer is a bit late :wink:

Subject: i’ve seen that

… i can correct the problem with shutting down the mtc task, delete the current .MTC file and executing “tell mtc reindex”, “tell mtc purge 30” and “tell mtc process”, but after 04.00 AM (when the mail.box maintenance takes place), the problem starts again…

is it possible, that the mail.box maintenance “destroys” something? here’s one part of the log:

16.09.2009 04:00:06 Router: Initiating daily mailbox maintenance

16.09.2009 04:00:06 Router: Received maintenance request for mail.box, processing all pending message updates

16.09.2009 04:00:08 Starting purge of old documents in log file

16.09.2009 04:00:14 Recovery Manager: Assigning new DBIID for D:\Lotus\Domino\data\mail.box (need new backup for media recovery).

16.09.2009 04:00:43 Finished purge of log file

16.09.2009 04:06:52 Admin Process: Searching Administration Requests database

16.09.2009 04:10:48 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OFECFB03FA.CAA507BB-ONC1257633.000B145C & [inrcp]=ISpy on office08@OBJENTIS: No documents found

16.09.2009 04:10:48 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OFDA329796.F745A9EF-ONC1257633.000B1492 & [inrcp]=ISpy on office08@OBJENTIS: No documents found

16.09.2009 04:10:48 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OF4E14992A.01526540-ONC1257633.000B1971 & [inrcp]=ISpy on office08@OBJENTIS: No documents found

16.09.2009 04:10:48 MT Collector: Failed updating entry in message tracking store: [inmsgid]=OFB6B6D955.ECF40693-ONC1257633.000B19AF & [inrcp]=ISpy on office08@OBJENTIS: No documents found

[and many more errors]

any idea? slowly, it’s getting funny :wink:

Subject: MT Collector: Failed updating entry

Was there ever any resolution to this? We’ve recently upgraded from v7 to 8.5.1 FP1 and experience the same problem.

Thanks

Subject: MT Collector failed

I am on FP2 and getting this error also.

Subject: Same on FP5

Yesterday I updated my 8.5 server to 8.5.1 + LanguagePack DE + FixPack 5: I now get the same error…

Subject: Same on Domino 8.5.2

previously never exist, after upgrade just now it appeared.

Subject: Experience the same issue on R8.5.2

I am seeing the same issue on a customer Domino R8.5.2 server.I have found the following IBM APAR → LO50195: MT COLLECTOR: FAILED UPDATING ENTRY IN MESSAGE TRACKING STORE

Subject: Fixed in 8.5.3

According to IBM, this has been fixed in 8.5.3. http://www-01.ibm.com/support/docview.wss?uid=swg21516042

Subject: not really

we’re still living with this problem. also with FP1 there’s no change. sadly…

hope someone sees that there are some people here with that problem

Best regards,

Bernhard