Exception of type Microsoft.ReportingServices.ReportProcessing.bk

Hi,
I am receiving the following error for a new data driven subscription I have
setup.
Exception of type Microsoft.ReportingServices.ReportProcessing.bk
I have searched this newsgroup and google and can't seem to find any
description of the error. The RS logs also yield very little other than the
exception itself.
When running the subscription with a "Run Once" schedule it doesn't seem to
throw the error; if I schedule the report to run on a daily schedule it does
throw the error.
Any help is greatly appreciated. If more details are needed please let me
know.
Thanks,
Nickwhat's the delivery mechanism?
make sure the account with which RS runs for unattended execution has
permissions to access the data store being used by your subscription. The
default account for RS from the setup is the Network Service account in
Win2003 Server.
Is this RS 2000 or 2005?
--
Regards,
Thiago Silva
"Nick @. INDATA" wrote:
> Hi,
> I am receiving the following error for a new data driven subscription I have
> setup.
> Exception of type Microsoft.ReportingServices.ReportProcessing.bk
> I have searched this newsgroup and google and can't seem to find any
> description of the error. The RS logs also yield very little other than the
> exception itself.
> When running the subscription with a "Run Once" schedule it doesn't seem to
> throw the error; if I schedule the report to run on a daily schedule it does
> throw the error.
> Any help is greatly appreciated. If more details are needed please let me
> know.
> Thanks,
> Nick|||This is SQL RS 2000, I will double check the permissions for the unattended
execution account. I also have a case open with MSFT on this right now, will
share anything I find out from them here.
"HC" wrote:
> what's the delivery mechanism?
> make sure the account with which RS runs for unattended execution has
> permissions to access the data store being used by your subscription. The
> default account for RS from the setup is the Network Service account in
> Win2003 Server.
> Is this RS 2000 or 2005?
> --
> Regards,
> Thiago Silva
> "Nick @. INDATA" wrote:
> > Hi,
> >
> > I am receiving the following error for a new data driven subscription I have
> > setup.
> >
> > Exception of type Microsoft.ReportingServices.ReportProcessing.bk
> >
> > I have searched this newsgroup and google and can't seem to find any
> > description of the error. The RS logs also yield very little other than the
> > exception itself.
> >
> > When running the subscription with a "Run Once" schedule it doesn't seem to
> > throw the error; if I schedule the report to run on a daily schedule it does
> > throw the error.
> >
> > Any help is greatly appreciated. If more details are needed please let me
> > know.
> >
> > Thanks,
> >
> > Nick|||FileShare Delivery Extension
"HC" wrote:
> what's the delivery mechanism?
> make sure the account with which RS runs for unattended execution has
> permissions to access the data store being used by your subscription. The
> default account for RS from the setup is the Network Service account in
> Win2003 Server.
> Is this RS 2000 or 2005?
> --
> Regards,
> Thiago Silva
> "Nick @. INDATA" wrote:
> > Hi,
> >
> > I am receiving the following error for a new data driven subscription I have
> > setup.
> >
> > Exception of type Microsoft.ReportingServices.ReportProcessing.bk
> >
> > I have searched this newsgroup and google and can't seem to find any
> > description of the error. The RS logs also yield very little other than the
> > exception itself.
> >
> > When running the subscription with a "Run Once" schedule it doesn't seem to
> > throw the error; if I schedule the report to run on a daily schedule it does
> > throw the error.
> >
> > Any help is greatly appreciated. If more details are needed please let me
> > know.
> >
> > Thanks,
> >
> > Nick|||Hey, Nick
Did you ever get a resolution for this issue?
I am not quite sure what the error means, since I've never seen an
exception type "ReportProcessing.bk."
Can you look at your RS logs to get more information on the issue. The
RS log is located in "C:\Program Files\Microsoft SQL
Server\MSSQL.x\Reporting Services\LogFiles".
Take a look at the log file for the time when you encountered the
issue. Try recreating the problem first, so you can have a fresh
logged entry, then look it up on the log.
Also, take a peek at the event log on the server, for anything
suspicious.
If you can post the message from the log, that may help in
troubleshooting that issue.
regards,
Thiago Silva