Has anyone seen this type of error in the event viewer?
Event Type: Error
Event Source: BusinessObjects_CMS
Event Category: General
Event ID: 47706
Date: 3/25/2007
Time: 3:35:01 AM
User: N/A
Computer: CMS Server
Description:
The schedule result provided by the Job Server for the object identified by nnnnnn is invalid.
The nnnnnn is not a constant number, and I’ve seen this happening alot lately, actually, we had 7 over the weekend.
Please provide some info if you have come across this type of error and have a fix.
I have seen the same error in our event logs.
Would like to know whats the object id “nnnnnn” refering to.
Its not the SI_ID of an object in CI_INFOOBJECTS table.
Wonder what else it could be !!
Anyone has a clue?
It would be good to know which report was affected as a result of this error.
Edit:
Didnt find what “Object Id” is, but got some info on probable cause.
Cause:
This error is caused when a “Running” instance of a scheduled report is deleted by a user.
Resolution is obviously to avoid deleting a “Running” report.
I don't know if anyone has determined what the number within the error message correlates to yet, but thought I'd share what I found with you.
The number correlates to the unique instance identifier within the output file store. If you search the output file store on the server for that number (as part of the file name) you'll find a file folder. If you open that folder you'll find the report that was deleted before finishing.
I had encountered this error previously but didn't have the time to research it as extensively as I wanted to but "found" the time today. I don't know if anyone is tracking this older post but decided to reply for anyone who may need to know.
Hopefully what I've posted makes sent to everyone.
Thanks!!!
I dont think its causing just because of deleting a running instance, otherwise it could be one time issue, but this is not the case at my end, I see hunderds of such messages in the logs even after making sure that no one is deleting the running instance. I beleive there is something else which is causing the issue, I will spend some time on investigating this and will update if found any.
Meanwhile if there is any idea that anyone can share here will be more helpful.