One failed subscription prevents running all others

Hello,
I was trying to invertigate why a certain report does not run properly in
some cases. I scheduled it to run daily. So far so good, i got logfiles to
study. However, since this try RS no longer executes ANY scheduled
subscription. i made no changes to the system, just scheduled a defective
report. (which BTW was in Excel and the row-count exceded 65536). Does
anybode know how to edit the (hypothetical) queue used by RS to clear the way
for my other subscriptions.
extra info: RSExecutionlog DB has no entries of executed subscriptions. The
SQL job manager says all jobs have executed succesfully as planned.(including
the subscriptions)Are there any rows in either the event table or notifications table?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ard Goossens" <ArdGoossens@.discussions.microsoft.com> wrote in message
news:175AE411-3994-4C8E-993F-8D4D258219B8@.microsoft.com...
> Hello,
> I was trying to invertigate why a certain report does not run properly in
> some cases. I scheduled it to run daily. So far so good, i got logfiles
> to
> study. However, since this try RS no longer executes ANY scheduled
> subscription. i made no changes to the system, just scheduled a defective
> report. (which BTW was in Excel and the row-count exceded 65536). Does
> anybode know how to edit the (hypothetical) queue used by RS to clear the
> way
> for my other subscriptions.
> extra info: RSExecutionlog DB has no entries of executed subscriptions.
> The
> SQL job manager says all jobs have executed succesfully as
> planned.(including
> the subscriptions)
>

OLE DB - ADO .NET

Does anybody know why in some cases you can use both connection types, in others you can't. Like for example, you start a data flow task with a Datareader Source which uses an ADO .NET connection manager, next you want to do a lookup and seems like the only type of connections you can use in a lookup table is the OLE DB.

So OLE DB is placed hard coded in a lookup task, and I thought things changed since the coming of OOP ...

I think ole db is ok

just when i use script component,i use ado.net

|||Your observation is correct -- Lookup currently only supports OLE DB connections. We hope to add ADO.NET connection support in the future.|||Ok