Schedule failing: file not found on File Repository Server

[Italo Sessegolo]

Hi,

I have several scheduled reports failing at random - the error message says "file xxxx.rep not found on file repository server". If I reschedule a report that failed like that, it runs fine. Any ideas as to what the problem is? I've searched for the error message on BOB but could not find any posts.
Thanks,

Italo

[Wolfgang Bidner]

ups -did you reschedule with another user? I think I had trouble once using different users...

Wobi

[Italo Sessegolo]

No, they are all scheduled by Administrator.... but thanks anyway...

[Wolfgang Bidner]

Re-export to Repository may help too

Wobi

[newgun]

If you have access to the FRS folders, you can easily see whether the file is there.

I have noticed some people incorrectly configured a clustered CMS to have their FRS pointing to two different locations - if that's the case, one certainly could have encountered this kind of behavior - depending on where the job is executed, it might or might not be able to find the file.

[Italo Sessegolo]

Thease are all good sugestions. This is a standalone server, so the clustering FRS location does not apply (good point, though). I guess I'll just reschedule the recurring schedule and see if that fixes it, and may also import / export the document again. I still wonder what is wrong though...

[rb44169]

Did you ever find a solution to this problem? I'm having the same issue.

[Italo Sessegolo]

It still happens to us, intermittently with random reports. Sorry...

[Italo Sessegolo]

The way we fix it is to edit the report and re-export it, then reschedule it.

[rb44169]

Have you noticed this behavior after a report has been migrated(promoted) from a development environment? Have you submitted a ticket with Business Objects?

[BoB LoblaW]

I've seen this happen when someone does a File -> Save As (instead of File -> Save) then re-exports the report to the repository. If the report is set to run on a recurring schedule, the error surfaces. Scheduling (do not click Reschedule link) the report again corrects the error.

[Italo Sessegolo]

We have the error happening for no apparent reasson, even if you do not make any changes to reports or universes. I have still to open a ticket with BO. We thought it might be related to us using the software EQM to promote reports and universes so we held off on opening a ticket with Bo for a while.

[rb44169]

I also submitted a ticket for this issue. If I get answer I will share it with you. How long ago did you submit your ticket?

[Italo Sessegolo]

I haven't opened a ticket yet... Please let me know what you find out.

Thanks,
Italo

[mimi]

Hi,
we got the same issue here. have you found any reason/solution from BO soupport?

Thanks,