sql server reporting services: If I publish a website in vs05 and Check "Allow this precompiled
website to be updatable", everything works.

If I uncheck the box, then the rdlc files get sent to the website
minus their guts, but with the standard placeholder text you see in
aspx files that are precompiled.

When you request a local report in your web page, it errors out:

An error occurred during local report processing.
The definition of the report 'Main Report' is invalid.

The report definition is not valid. Details: Data at the root level
is invalid. Line 1, position 1.


Any solution for this?

FYI -others

Hi Chuck,

Thank you for posting.

Yes, as for the problem you mentioend, it does be an existing problem with
the VS 2005/ASP.NET 2.0 when we use the "publish web site" function with
"not updatable" option. Actually under such mode, the ASP.NET2.0 compiler
will precompile all the pages and other document stuffs in the application
directory and remove the code files (only put a dummy file in the target
directory). So files such as our custom rdlc file will also be corrupted in
such cases.

I've also had a look at the forum thread you mentioned, and that thread
does point out the workarounds we have currently.

#1 One is manually copy the original file to the target server to overwrite
the dummy one(produced by the compiler when using 'nonupdatable' option).
And to do this in VS 2005 IDE, you can consider use the "Copy Web Site"
function to update such individual file, this won't cause recompilation.

#2 Another option will be using automation script or batch build file to do
the precompilation work ( the aspnet_compiler.exe tool is the commandline
tool for precompiling asp.net website application), we can add additional
script to copy the correct rdlc file after the precompilation command
executed.

In addition, I think you can also post this issue in our msdn product
feedback site though some other members may already have pointed out this
issue:

http://lab.msdn.microsoft.com/productfeedback/default.aspx

Anyway, I'm sorry for the inconvenience this brings you as this does be a
big pain when there exists many static documents need publishing under
"non-updatable" precompiling option.

Thanks for your understanding.


Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Hi Chuck,

How are you doing on this or does the information I mentioned helps a
little on this? If there is still anything we can help, please feel free to
post here.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Anyone know if there's been any progress on getting this fixed?

From http://developmentnow.com/g/115_2006_5_0_0_753708/Precompile-asp-net-and-Reports-bomb.htm

Posted via DevelopmentNow.com Groups

Hi Steven

I usually precompiled my site with the aspnet_compiler (with not-updatable) option. Indeed the rdlc file was corrupted during this process ( 1 KB vs original 17 KB). Your fix #2(replacing the rdlc with the original rdlc file) worked well.

Thanks,
Ram

From http://developmentnow.com/g/115_2006_5_0_0_753708/Precompile-asp-net-and-Reports-bomb.htm

Posted via DevelopmentNow.com Groups