Error Rendering trough Web Service to WebArchivo format

Hi,
We are using the Reporting Services Web Service, in order to expose some
reports in our Web Application, right now I am trying to enable exporting the
report to the available formats in Reporting Services, and altough everything
seems to be working fine, when I try to render as Web Archive, I get the
following exception:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. --> The parameter is incorrect.
first I tough it was because of the device info configuration I was using,
since it was the same of the html format (which had things like turning off
the toolbar), thus I instead didnt pass any deviceinfo(null), in both cases
it works fine in all formats but it doesnt in Web Archive.
I have been searching for info about the error, but I havent found any ...
if anyone knows what is happening, I will be thankfull :) ... in the mean
time, I will keep trying, and if I find anything I will post it here.I have continued digging on the problem, I havent found anything on the
internet, and I have cleared out some things about the problem ...
so, here are some aditional info about the problem:
- it isnt only happening when I try to render the report trough the Web
Service, it also happens when I use url access.
- it is happening specifically in this report, there are other reports that
works well
- I am not using any totals/subtotals formulas (I say this, since I have
read this might cause trouble in certain rendering extensions)
- I just found something else (I have 3 reports):
- the report that is working doesnt receive any parameter
- the 2 reports that doesnt work receive 1 parameter, and additionaly have
a list of valid values ...
it looks like it were a bug, something along the lines that rendering
extension either ignores the parameters, or gets confused where there is a
list of valid values ...
Any help will be greatly appreciated ... in the mean time, I will be playing
with the reports definition, in order to find what is exactly happening, if I
dont find a solution soon I will restrict that rendering extension from being
used :(:(:( ...|||I am done with this, I am pretty certain is a bug, just not the type of bug I
tough ...
it is really weird, I played with the parameter options in the report and
the error kept happening, then I decided playing with the report design ...
well, whenever I put a third column in my report, the error happens when I
try to export it to web archive ... I put all types of definition in the
third column, to see if I managed to see anything making it fail, but didnt
arrive to anything, I tried from the simplest one (static text + no
formatting) all trough a "complex" one (formatting + dinamic text ...)

Error on Stored Procedure

I need to perform a select statement across servers... this statement works in query analyzer but not as a procedure. It tells me I need to enable the ANSI_NULLS and ANSI_WARNINGS options when put into a procedure (which it looks like i did!) I think it has something to do with this GO as the stored procedure isn't recognizing it. I tried even building it as a string and executing. Any ideas as to enable this in a procedure?

CREATE PROCEDURE TESTING AS
SET ANSI_NULLS ON
GO
SET ANSI_WARNINGS ON
GO
SELECT * FROM MIDSERV.DB000.dbo.tblcustomer
select * from #tableTake out GO statements after SET and re-run the SP.|||Originally posted by Satya
Take out GO statements after SET and re-run the SP.

CREATE PROCEDURE TESTING AS
SET ANSI_NULLS ON

SET ANSI_WARNINGS ON

SELECT * FROM MIDSERV.DB000.dbo.tblcustomer

I get the same error telling me to enable ansi_nulls and ansi_warnings...|||Aren't the ANSI_NULL and ANSI_WARNING options to has to be set at connection level?

i belive (thought not so sure) that you cannot use it inside a stored procedure, you just have to call it BEFORE you call your stored procedure.|||that is a GOOD CALL!!!!!!!!!!!

You wouldn't know how about to set those at connection level would you? I tried doing it in a job scheduled in EM and it didn't work too well

First transact-sql statement in job:
set ANSI_NULLS ON
SET ANSI_WARNINGS ON
GO

Second transact-sql statement in job
exec procedure1

also tried combining
set ANSI_NULLS ON
SET ANSI_WARNINGS ON
GO|||mmm...do have already tried to remove the "GO" statement?

to set an option at connection level you just have to call it BEFORE anything else you want to execute with that options activated.

now i cannot try, but i'll make a test as soon as i get a SQL Server console under my hand :-)sql