Hi,

I've create a fex that generates me a hold-file accessible for other reports. (=Cached data-set)
To have the hold file refreshed regularly, I've scheduled the report in reportcaster.

Right now, I've scheduled it to send its output in HTML to the Managed Repository because I needed to fill in something, but as a result I'm each time getting an error 'No report to distribute' in my logs. (makes sense - there's only a hold file to generate)

My question: how do I prevent this error knowing I have to provide a format & distribution? (I basically need the report to execute, but not distribute anything)

Regards,
Peter

This message has been edited. Last edited by: Peter,

Do this all the time , it's annoying the "no report error"
To get around it do a simple report at the end
which maybe does a checksum and mail that.
It's also a sanity check your job has worked.

TABLE FILE CAR
SUM CNT.MODEL
BY MODEL
END

We had the same issue and solved it.
There's a setting in the report caster configuration called "Processing for No Report to Distribute" (under Distribution Servers) which defaults to Error.
You can set that to Warning.

Thank you both - the Distribution server option worked best for me!
--> warning in the log, but successful completion