"john pryor" wrote:

> I need to be able to run this parameterized report on the fly, and
> specifically from within a SSIS package. I appreciate your solution, but it
> doesn't answer the question of why one MS app's WSDL can not be understood by
> another MS app.
>
> I'd like to know if MS has an answer or fix, or if anyone else has found a
> workaround when using SSRS's WSDL within SSIS. Thanks.
>
> --
> John Pryor
>
>
> "Charles Kangai" wrote:
>
> > Hi John,
> >
> > I don't understand what you are trying to do. Where will the report display?
> > If you are simply wanting to output a report to a file such as an Excel file,
> > I suggest that in Reporting Services you create a subscription to a file
> > share with a one time schedule of a time in the past. Go to SQL Server Agent
> > and find the name of the job that it has created as a result. In SSIS, use
> > the Execute SQL Task to run the SQL Server Agent job using the stored
> > procedure sp_start_job.
> >
> > If you are trying to view the report while the package is running, then you
> > have to control things from Reporting Services side. Just create your package
> > with a DataReader data destination and in Reporting Services use this as a
> > data source to your report [after uncommenting the SSIS sections in
> > RSReportDesigner.config].
> >
> > Charles Kangai, MCT, MCDBA
> >
> > "john pryor" wrote:
> >
> > > I would like to execute a ssrs report from within a ssis foreach loop but
> > > there is no task especially for this so I tried to use the web service task
> > > and connect to the ssrs web service but ssis complained about the ssrs wsdl,
> > > does anyone know why and what I can do to fix? Thanks.
> > > --