March 26, 2008 at 8:52 am
I have created many reports using VS 2005 Business Intelligence Projects Report Server Project. I created a control that I use to display these reports. I was using the print preview control using PrintPreviewWebPage.SERVER_NAME.ReportingService to create the report. Then one day a few months ago, all the reports for all the users (not just mine) had a black background (the report was not visible, just a black page). I have no idea what changed. I had to go and change all the reports to have a white background instead of transparent. The print preview control still had the black background. I have recently changed the control to use the Microsoft.Reporting.WinForms.ReportViewer. I do not have to change the background of the controls on the report to be transparent to view the report. When I checked the Print Layout and the dreaded black page came up again. It is a nuisance having to change all backgrounds to white. Does anyone know what would cause this black background and how I can set it to white again?
March 26, 2008 at 10:32 am
Look for a messed up css file.
March 26, 2008 at 10:43 am
Where would the css file be? I don't use css files for this. It has to do with the default settings because I just created a dummy report with nothing but a textbox and the same thing happens.
March 26, 2008 at 10:51 am
Your report server uses some css files during rendering. You should find them in the reporting services install folder on the report server.
March 26, 2008 at 12:58 pm
I found the following CSS files:
MSSQL.3\ReportingServices\ReportManager\Styles\ReportingServices.css
MSSQL.3\ReportingServices\ReportManager\Styles\RSWebParts.css
MSSQL.3\ReportingServices\ReportServer\Styles\HtmlViewer.css
MSSQL.3\ReportingServices\ReportServer\Styles\SP_Full.css
MSSQL.3\ReportingServices\ReportServer\Styles\SP_Small.css
Are any of these the files that you would think it would be in? What am I looking for in these css files?
March 26, 2008 at 1:00 pm
Start by comparing them to the ones that are installed by default.
March 31, 2008 at 7:34 am
There is a bug relating to this situation. Look for the hotfix on the MSDN website.
April 8, 2008 at 6:53 am
Thanks a bunch. The hotfix fixed it.
December 3, 2009 at 2:04 pm
I have the same type of problem do you have the kb# that goes with the hotfix?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply