Books, articles on printing reports

I am a developer. I current have the Developer Edition of SQL Server 2000 on
my desktop and I am installing VB.Net 2003 and Reporting Services so that a
report, that uses data from a SQL Server 2000 database, can be printed.
I seek the minimal education available that will enable me to design this
report that my customers, who using the database, will print. Are there
suggestions for books or articles that meet this need?
Thanks.
JimMicrosoft SQL Server 2000 Reporting Services is pretty straight forward if
you avoid the filler about how the engine works (actually to be fair all the
books I've seen spend a lot of time on this), there is a better book but its
quite a bit more techy - hitch hikers guide to reporting services.
Phil
"James_101" <James101@.discussions.microsoft.com> wrote in message
news:F730DE37-5437-4E9C-BB8B-BA7776BDEBC9@.microsoft.com...
>I am a developer. I current have the Developer Edition of SQL Server 2000
>on
> my desktop and I am installing VB.Net 2003 and Reporting Services so that
> a
> report, that uses data from a SQL Server 2000 database, can be printed.
> I seek the minimal education available that will enable me to design this
> report that my customers, who using the database, will print. Are there
> suggestions for books or articles that meet this need?
> Thanks.
> Jim|||'Hitchhiker's Guide to SQL Server 2000 Reporting Services' is a very good
book on the subject ...
http://www.sqlreportingservices.net/
There are lot's of on-line resources here ...
http://msdn.microsoft.com/sql/2000/learn/bi/reporting/default.aspx
--
Brendan Reynolds
"James_101" <James101@.discussions.microsoft.com> wrote in message
news:F730DE37-5437-4E9C-BB8B-BA7776BDEBC9@.microsoft.com...
>I am a developer. I current have the Developer Edition of SQL Server 2000
>on
> my desktop and I am installing VB.Net 2003 and Reporting Services so that
> a
> report, that uses data from a SQL Server 2000 database, can be printed.
> I seek the minimal education available that will enable me to design this
> report that my customers, who using the database, will print. Are there
> suggestions for books or articles that meet this need?
> Thanks.
> Jim|||Best book I've read on RS is "CodeFez Guide to Reporting Services". They
released a PDF version a few weeks ago, PDF version is about $20. I found
it a lot easier to read than the others.
http://www.falafel.com/Products/tabid/58/CatalogItemID/19/CatalogID/1/psnavcmd/CatalogItemDetails/Default.aspx
--
Floyd
"James_101" <James101@.discussions.microsoft.com> wrote in message
news:F730DE37-5437-4E9C-BB8B-BA7776BDEBC9@.microsoft.com...
>I am a developer. I current have the Developer Edition of SQL Server 2000
>on
> my desktop and I am installing VB.Net 2003 and Reporting Services so that
> a
> report, that uses data from a SQL Server 2000 database, can be printed.
> I seek the minimal education available that will enable me to design this
> report that my customers, who using the database, will print. Are there
> suggestions for books or articles that meet this need?
> Thanks.
> Jim

Book Suggestion?

Can anyone recommend good books for learning Reporting Services? Assume the reader is familiar with Crystal Reports and other reporting environments, but has no experience with SQL Server 2005 and very little with Visual Studio 2005.

Try

Microsoft SQL Server 2005 Reporting Services step by step

Misner, Stacia. 2006

Book Recommendation for SRS2005 Designing Reports

Hi,
Does anyone have any book recommendations for designing Reports? I am
looking for a book that covers the basics but also moves onto more
advanced examples.
Thanks.I just picked up "Microsoft SQL Server 2005 Reporting Services 2005" by
Brian Larson (McGraw Hill). The ISBN is 0-07-226239-7. It was highly rated
on Amazon and it's turned out to be excellent.
"Gareth King" <QBVBKADUOIUJ@.spammotel.com> wrote in message
news:WtFKf.111376$AL5.53955@.fe01.news.easynews.com...
> Hi,
> Does anyone have any book recommendations for designing Reports? I am
> looking for a book that covers the basics but also moves onto more
> advanced examples.
> Thanks.

Book on Business Intelligent Reports ?

Does any one know of a good reference or book dealing specifically with Business Intelligent Reports? I need to figure out how to fully utilize the reports.

Thanks
CalSurely someone has an answer to this question.

Calsql

Bold in a textbox ms-access

In my reports of MS-ACCESS I need to combine Bold in a textbox. I do not program in VB

so I would like something like this:

=Format([name],"bold" & " " & [lastname])

and the output shoul be

Mike Andersen

Is it posible to do?

no it isnt, ms-access doesnt support different styles in on textbox (as far as i know)

a little workaround would be to create 2 textboxes next to each other

the first bold, the second normal

sql

Bold in a textbox ms-access

In my reports of MS-ACCESS I need to combine Bold in a textbox. I do not program in VB

so I would like something like this:

=Format([name],"bold" & " " & [lastname])

and the output shoul be

Mike Andersen

Is it posible to do?

no it isnt, ms-access doesnt support different styles in on textbox (as far as i know)

a little workaround would be to create 2 textboxes next to each other

the first bold, the second normal

Body BackgroundImage not displayed in browser

I have been trying to set up reports with a background image. The background displays correctly on the preview tab in Visual Studio, but is not visible when deployed to the report server and rendered in Internet Explorer.

However, if the report is printed, or exported to PDF or Excel, the background displays correctly.

It does not seem to make any difference if the image is external or embedded. Also, the problem only seems to affect the Body properties; a background image attached to a table, for example, seems to display correctly.

Has anybody else seen this behavior? I have not done extensive testing, but every report that I have tried seems to have the same problem. Is there a setting someplace that I am missing, or is this perhaps a bug in IE?

This sounds like a known issue in RS 2005 SP1 where the background images does not show up when rendering with the ReportViewer control. This was addressed in a Hotfix and will also be fixed in Visual Studio 2005 SP1.

-Chris

|||

I am running RS 2005 with SP2. When I render a RS report to Internet Explorer the background image still is not displaying, though the image does print. Exactly as described in the origional message. Any ideas?

Thanks!

Body BackgroundImage not displayed in browser

I have been trying to set up reports with a background image. The background displays correctly on the preview tab in Visual Studio, but is not visible when deployed to the report server and rendered in Internet Explorer.

However, if the report is printed, or exported to PDF or Excel, the background displays correctly.

It does not seem to make any difference if the image is external or embedded. Also, the problem only seems to affect the Body properties; a background image attached to a table, for example, seems to display correctly.

Has anybody else seen this behavior? I have not done extensive testing, but every report that I have tried seems to have the same problem. Is there a setting someplace that I am missing, or is this perhaps a bug in IE?

This sounds like a known issue in RS 2005 SP1 where the background images does not show up when rendering with the ReportViewer control. This was addressed in a Hotfix and will also be fixed in Visual Studio 2005 SP1.

-Chris

|||

I am running RS 2005 with SP2. When I render a RS report to Internet Explorer the background image still is not displaying, though the image does print. Exactly as described in the origional message. Any ideas?

Thanks!

blank pages in reports through subscriptions

I have Reporting Services 2005 wsp1, SQL Server 2005 version 9.00.2047. When
I generate reports through Reports Admin interface and then export them to
PDF, they come out ok. When I set up a subscription that is supposed to send
a report in pdf format - I get the same report with around 50 blank pages
inserted in it.
Anybody ran across the same stuff?On Mar 2, 11:39 am, "ilona" <ilona_scramb...@.no-go.com> wrote:
> I have Reporting Services 2005 wsp1, SQL Server 2005 version 9.00.2047. When
> I generate reports through Reports Admin interface and then export them to
> PDF, they come out ok. When I set up a subscription that is supposed to send
> a report in pdf format - I get the same report with around 50 blank pages
> inserted in it.
> Anybody ran across the same stuff?
I've had some problems with this before...I would try to eliminate any
unused space in the report designer area and check your page
setting...
Cheers,
-Ben

Blank pages in print preview for sub reports

Hi,

I have serveral subreports in main report. I have no problem print the orignal report but when I print them as subreport so get extra blank pages. I try to set the width of sub report in main report the max width value (19.6 cm width) without succeed. Any help would be appreiciate!

Hi,The extra blank page is coming for the Page Layout that you set for your report.Decrease the Left Margin and right margin percentage and try to move your Textbox fields bit closer to each other from right side and remove the extra space left on the right side of your report just draging it towards left.Hope this will solve your problem.|||Hi,In Sql report the preview take extra space for the extra width that you give to your report.So remove the extra width from your report.Do not increase the default width of the report by draging it towards right.Hope this will solve your problem.

Regards
Gelu

Blank Pages following report

I have a report that uses 7 subreports. Some reports show, some don't
depending on the data received from the Shared Datasource. My initial report
appears fine in the viewer, however I have a single page following the last
page with data containing only the header. When I create a pdf, I have 4
pages at the end with only headers. The main report and the first subreport
should be the only ones outputting data.
Ideas?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200510/1I have found my problem, but no solution. When the subreports run, they are
given "space" on the report even if their visibility is set to False. This
is what is generating my "blank pages". This poses a new and even uglier
issue for me, What Now? My requirements are to have a single report that
gives alternate data depending on the needs of the user. I have two ideas:
1) Can I manually launch a subreport in code WITHOUT navigating away from
the parent report?
2) Is it possible to dynamically add a Subreport to the main report via VB
Code so only the subreports needed are run?
I am researching both avenues, but any advice you could offer would be WELL
received!
Rick wrote:
>I have a report that uses 7 subreports. Some reports show, some don't
>depending on the data received from the Shared Datasource. My initial report
>appears fine in the viewer, however I have a single page following the last
>page with data containing only the header. When I create a pdf, I have 4
>pages at the end with only headers. The main report and the first subreport
>should be the only ones outputting data.
>Ideas?
Message posted via http://www.sqlmonster.com|||I am also running into the same issue and finding no solution. Any help is
appreciated.
"Rick via SQLMonster.com" wrote:
> I have found my problem, but no solution. When the subreports run, they are
> given "space" on the report even if their visibility is set to False. This
> is what is generating my "blank pages". This poses a new and even uglier
> issue for me, What Now? My requirements are to have a single report that
> gives alternate data depending on the needs of the user. I have two ideas:
> 1) Can I manually launch a subreport in code WITHOUT navigating away from
> the parent report?
> 2) Is it possible to dynamically add a Subreport to the main report via VB
> Code so only the subreports needed are run?
> I am researching both avenues, but any advice you could offer would be WELL
> received!
> Rick wrote:
> >I have a report that uses 7 subreports. Some reports show, some don't
> >depending on the data received from the Shared Datasource. My initial report
> >appears fine in the viewer, however I have a single page following the last
> >page with data containing only the header. When I create a pdf, I have 4
> >pages at the end with only headers. The main report and the first subreport
> >should be the only ones outputting data.
> >
> >Ideas?
>
> --
> Message posted via http://www.sqlmonster.com
>|||Has Microsoft any answer to this problem as this is something has been faced
by many people and doesnt seem to find any solution.
Setting page size and margine is one part of avoiding blank pages but with
sub reports, it not only introduce blank pages and sometimes change the whole
look of the report.
"manish" wrote:
> I am also running into the same issue and finding no solution. Any help is
> appreciated.
> "Rick via SQLMonster.com" wrote:
> > I have found my problem, but no solution. When the subreports run, they are
> > given "space" on the report even if their visibility is set to False. This
> > is what is generating my "blank pages". This poses a new and even uglier
> > issue for me, What Now? My requirements are to have a single report that
> > gives alternate data depending on the needs of the user. I have two ideas:
> >
> > 1) Can I manually launch a subreport in code WITHOUT navigating away from
> > the parent report?
> >
> > 2) Is it possible to dynamically add a Subreport to the main report via VB
> > Code so only the subreports needed are run?
> >
> > I am researching both avenues, but any advice you could offer would be WELL
> > received!
> >
> > Rick wrote:
> > >I have a report that uses 7 subreports. Some reports show, some don't
> > >depending on the data received from the Shared Datasource. My initial report
> > >appears fine in the viewer, however I have a single page following the last
> > >page with data containing only the header. When I create a pdf, I have 4
> > >pages at the end with only headers. The main report and the first subreport
> > >should be the only ones outputting data.
> > >
> > >Ideas?
> >
> >
> > --
> > Message posted via http://www.sqlmonster.com
> >|||This is a good question, I see this issue often on many boards I post to. In
this case, it was my error. I was setting sub reports to hidden, however the
Rectangle they were in were not being set to hidden. Hence the blank pages.
When I set the Rectangle to invisible, it works like a charm. If you run
into this issue, I suggest you look at the container you placed your Sub
Report in, that just might be your error.
manish wrote:
>Has Microsoft any answer to this problem as this is something has been faced
>by many people and doesnt seem to find any solution.
>Setting page size and margine is one part of avoiding blank pages but with
>sub reports, it not only introduce blank pages and sometimes change the whole
>look of the report.
>> I am also running into the same issue and finding no solution. Any help is
>> appreciated.
>[quoted text clipped - 22 lines]
>> > >
>> > >Ideas?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200511/1|||Also, if you set the subreport (or its container) to be invisible
conditionally, any pagebreaks selected for that subreport or container
will be ignored. For me, it is a really anoying "feature".

Blank page at http://localhost/reports and VS.Net Crashes on Preview

I have two questions. I am trying to work through some very simple reports to get the feel for SSRS. I am running SQL Server 2005 Developer Edition and I have VS.Net 2005 Pro installed on Windows XP SP2. I can walk through the report wizard just fine. But when I go to preview the report I get an exception in VS.Net.

Faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699, faulting module kernel32.dll, version 5.1.2600.2180, stamp 411096b4, debug? 0, fault address 0x0001eb33.

Now I know that this doesn't mean much in terms of sorting out the issue, but I thought that I would include it.

My second question is that I have created a data source and data model. When I try to bring up Report Manager at http://localhost/reports, all I see is a blank page. Nothing is displayed. I can't seem to find anything on the forums about this.

Thanks,

Scott

check reporting services have been installed properly

check Reports and ReportServer folders under default Website folder in ISS

check ReportServerDb and ReportServerTemp Db databases in sqlserver

always install first reporting services and then VS .NET ..

Blank IE screen

Hi everybody,
I have a problem with our new setup of RS 2005.
I can access de report manager an show reports fine.
I have the Bruce-workaround t.i. a "dummy"-report that refreshes itself
every few minutes to keep connections alive.
Still somtimes when I open up a report I get a blank IE window and have to
wait a full minute for "report is being generated" to appear. Although I ran
a report e few minutes earlier (certainly les than 20 minutes AND my dummy
report is running).
I ran a trace, but I can't really see the problem, could anybody please help.
I added the trace here below starting from the point I reqeusted the report
to the time that the "report is being generated" appeared. I can't add the
complete trace here (to long) I will put the rest in a next post.
Trace Start 2007-05-17 14:06:46.403
ExistingConnection -- network protocol: LPC
set quoted_identifier off
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
SQLAgent - Generic Refresher adminsql KLINA\adminsql 3232 51 2007-05-04
12:47:40.653
ExistingConnection -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 52 2007-05-17 12:54:29.373
ExistingConnection -- network protocol: TCP/IP
set quoted_identifier on
set arithabort on
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Toad for SQL Server sa 1364 55 2007-05-17 11:31:23.827
ExistingConnection -- network protocol: TCP/IP
set quoted_identifier off
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
SQLDMO_1 sa 1364 56 2007-05-17 11:31:25.890
ExistingConnection -- network protocol: LPC
set quoted_identifier off
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
SQLAgent - Job invocation
engine adminsql KLINA\adminsql 3232 58 2007-05-05 00:10:00.810
ExistingConnection -- network protocol: TCP/IP
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Microsoft® Visual Studio®
2005 vansinan KLINA\vansinan 1920 62 2007-05-10 20:23:44.327
ExistingConnection -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:04:29.090
ExistingConnection -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:42.717
Audit Logout Report
Server adminsql KLINA\adminsql 0 45 0 10000 2056 103 2007-05-17
14:06:42.717 2007-05-17 14:06:52.717
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:06:52.717 2007-05-17
14:06:52.717 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:52.717
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:52.717
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:06:52.717 2007-05-17 14:06:52.717
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:52.717
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:06:52.717 2007-05-17 14:06:52.717
Audit Logout Report
Server adminsql KLINA\adminsql 0 45 0 10250 2056 103 2007-05-17
14:06:52.717 2007-05-17 14:07:02.967
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:02.967 2007-05-17
14:07:02.967 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:02.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:02.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:02.967 2007-05-17 14:07:02.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:02.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:02.967 2007-05-17 14:07:02.967Here's the rest of it:
Audit Logout Report
Server adminsql KLINA\adminsql 0 45 0 10000 2056 103 2007-05-17
14:07:02.967 2007-05-17 14:07:12.967
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:12.967 2007-05-17
14:07:12.967 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:12.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:12.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:12.967 2007-05-17 14:07:12.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:12.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:12.967 2007-05-17 14:07:12.967
Audit Logout Report
Server adminsql KLINA\adminsql 0 9082 39 173876 2056 65 2007-05-17
14:04:29.090 2007-05-17 14:07:22.967
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:22.967 2007-05-17
14:07:22.967 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:22.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:22.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:22.967 2007-05-17 14:07:22.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:22.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:22.967 2007-05-17 14:07:22.967
Audit Logout Report
Server adminsql KLINA\adminsql 0 9082 39 4970 2056 65 2007-05-17
14:07:22.967 2007-05-17 14:07:27.937
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:27.937 2007-05-17
14:07:27.937 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:27.937
RPC:Completed exec GetMyRunningJobs
@.ComputerName=N'REPORTSRV',@.JobType=1 Report
Server adminsql KLINA\adminsql 0 2 0 0 2056 65 2007-05-17
14:07:27.937 2007-05-17
14:07:27.937 0X000000000300000020004700650074004D007900520075006E006E0069006E0067004A006F00620073005200000082001600E7306E0076006100720063006800610072002800390029001A00400043006F006D00700075007400650072004E0061006D006500120000005200450050004F00520054005300520056002E00000002001000341073006D0061006C006C0069006E007400100040004A006F006200540079007000650001001400000003000600380469006E00740000000000
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 5324 53 2007-05-17 14:07:28.140
RPC:Completed exec GetOneConfigurationInfo
@.Name=N'SharePointIntegrated' Report Server NETWORK SERVICE NT
AUTHORITY\NETWORK SERVICE 0 2 0 0 5324 53 2007-05-17 14:07:28.140 2007-05-17
14:07:28.140 0X00000000020000002E004700650074004F006E00650043006F006E00660069006700750072006100740069006F006E0049006E0066006F005A00000082001800E7306E00760061007200630068006100720028003200300029000A0040004E0061006D006500280000005300680061007200650050006F0069006E00740049006E00740065006700720061007400650064001400000003000600380469006E00740000000000
Audit Logout Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 0 2 0 76 5324 53 2007-05-17 14:07:28.140 2007-05-17 14:07:28.217
RPC:Completed exec sp_reset_connection Report Server NETWORK SERVICE NT
AUTHORITY\NETWORK SERVICE 0 0 0 0 5324 53 2007-05-17 14:07:28.217 2007-05-17
14:07:28.217 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 5324 53 2007-05-17 14:07:28.217
SQL:BatchStarting SELECT SERVERPROPERTY('Edition') Report Server NETWORK
SERVICE NT AUTHORITY\NETWORK SERVICE 5324 53 2007-05-17 14:07:28.217
SQL:BatchCompleted SELECT SERVERPROPERTY('Edition') Report Server NETWORK
SERVICE NT AUTHORITY\NETWORK SERVICE 0 0 0 0 5324 53 2007-05-17
14:07:28.217 2007-05-17 14:07:28.217
RPC:Completed exec GetOneConfigurationInfo @.Name=N'EnableMyReports' Report
Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 0 2 0 0 5324 53 2007-05-17 14:07:28.233 2007-05-17
14:07:28.233 0X00000000020000002E004700650074004F006E00650043006F006E00660069006700750072006100740069006F006E0049006E0066006F005000000082001800E7306E00760061007200630068006100720028003100350029000A0040004E0061006D0065001E00000045006E00610062006C0065004D0079005200650070006F007200740073001400000003000600380469006E00740000000000
Audit Logout Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 0 4 0 16 5324 53 2007-05-17 14:07:28.217 2007-05-17 14:07:28.233
RPC:Completed exec sp_reset_connection Report Server NETWORK SERVICE NT
AUTHORITY\NETWORK SERVICE 0 0 0 0 5324 53 2007-05-17 14:07:28.233 2007-05-17
14:07:28.233 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 5324 53 2007-05-17 14:07:28.233

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black Reports in Print Layout

Hello all,
We have an issue with reports we created using the VS 2005 Team System. When
we open a report everything looks fine and report prints fine as well.
The problem is that when we click the Print Layout button on the report we
get a black page and only report title and group headers are visible. Mind
you, the report still prints fine on the printer but none of the data is
visible in the report.
Any ideas and solutions appreciated.
BR,
GAZOn Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> Hello all,
> We have an issue with reports we created using the VS 2005 Team System. When
> we open a report everything looks fine and report prints fine as well.
> The problem is that when we click the Print Layout button on the report we
> get a black page and only report title and group headers are visible. Mind
> you, the report still prints fine on the printer but none of the data is
> visible in the report.
> Any ideas and solutions appreciated.
> BR,
> GAZ
This should help.
http://support.microsoft.com/kb/935356/en-us
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
> On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
>> Hello all,
>> We have an issue with reports we created using the VS 2005 Team System.
>> When
>> we open a report everything looks fine and report prints fine as well.
>> The problem is that when we click the Print Layout button on the report
>> we
>> get a black page and only report title and group headers are visible.
>> Mind
>> you, the report still prints fine on the printer but none of the data is
>> visible in the report.
>> Any ideas and solutions appreciated.
>> BR,
>> GAZ
>
> This should help.
> http://support.microsoft.com/kb/935356/en-us
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Thanks for the info. Got it but it won't install. Every single hotfix
reports a failure to install. Has anyone else had any problems with the
installation of the said hotfix?
BR,
GAZ|||On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
>
> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> >> Hello all,
> >> We have an issue with reports we created using the VS 2005 Team System.
> >> When
> >> we open a report everything looks fine and report prints fine as well.
> >> The problem is that when we click the Print Layout button on the report
> >> we
> >> get a black page and only report title and group headers are visible.
> >> Mind
> >> you, the report still prints fine on the printer but none of the data is
> >> visible in the report.
> >> Any ideas and solutions appreciated.
> >> BR,
> >> GAZ
> > This should help.
> >http://support.microsoft.com/kb/935356/en-us
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks for the info. Got it but it won't install. Every single hotfix
> reports a failure to install. Has anyone else had any problems with the
> installation of the said hotfix?
> BR,
> GAZ
You're welcome. You may have to install the Hot fixes in a particular
order. Have you tried verifying the order in which the hot fixes must
be installed? Hope this helps further.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
> On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
>> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
>>
>> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
>> >> Hello all,
>> >> We have an issue with reports we created using the VS 2005 Team
>> >> System.
>> >> When
>> >> we open a report everything looks fine and report prints fine as well.
>> >> The problem is that when we click the Print Layout button on the
>> >> report
>> >> we
>> >> get a black page and only report title and group headers are visible.
>> >> Mind
>> >> you, the report still prints fine on the printer but none of the data
>> >> is
>> >> visible in the report.
>> >> Any ideas and solutions appreciated.
>> >> BR,
>> >> GAZ
>> > This should help.
>> >http://support.microsoft.com/kb/935356/en-us
>> > Regards,
>> > Enrique Martinez
>> > Sr. Software Consultant
>> Thanks for the info. Got it but it won't install. Every single hotfix
>> reports a failure to install. Has anyone else had any problems with the
>> installation of the said hotfix?
>> BR,
>> GAZ
>
> You're welcome. You may have to install the Hot fixes in a particular
> order. Have you tried verifying the order in which the hot fixes must
> be installed? Hope this helps further.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Thanks for your answer.
The hotfixes are acutally rolled into one package which does not give you an
option to choose a particular order for installation. When we start the
installation it always asks for the SQL installation disk and then it reads
files from it and reports that the hotfix installation failed. And so on for
each of the components.
Well, I guess that we'll have to wait for the SP3 to have the issue
resolved.
Thanks again for your help.
BR,
GAZ|||On Dec 26, 1:58 am, "GAZ" <g...@.gaz.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
>
> > On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >>news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
> >> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> >> >> Hello all,
> >> >> We have an issue with reports we created using the VS 2005 Team
> >> >> System.
> >> >> When
> >> >> we open a report everything looks fine and report prints fine as well.
> >> >> The problem is that when we click the Print Layout button on the
> >> >> report
> >> >> we
> >> >> get a black page and only report title and group headers are visible.
> >> >> Mind
> >> >> you, the report still prints fine on the printer but none of the data
> >> >> is
> >> >> visible in the report.
> >> >> Any ideas and solutions appreciated.
> >> >> BR,
> >> >> GAZ
> >> > This should help.
> >> >http://support.microsoft.com/kb/935356/en-us
> >> > Regards,
> >> > Enrique Martinez
> >> > Sr. Software Consultant
> >> Thanks for the info. Got it but it won't install. Every single hotfix
> >> reports a failure to install. Has anyone else had any problems with the
> >> installation of the said hotfix?
> >> BR,
> >> GAZ
> > You're welcome. You may have to install the Hot fixes in a particular
> > order. Have you tried verifying the order in which the hot fixes must
> > be installed? Hope this helps further.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks for your answer.
> The hotfixes are acutally rolled into one package which does not give you an
> option to choose a particular order for installation. When we start the
> installation it always asks for the SQL installation disk and then it reads
> files from it and reports that the hotfix installation failed. And so on for
> each of the components.
> Well, I guess that we'll have to wait for the SP3 to have the issue
> resolved.
> Thanks again for your help.
> BR,
> GAZ
You're welcome. Have you checked the Event Viewer for errors that
might be logged during the process? That might provide some better
details. Hope this helps further.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:7c2d5ac2-a280-4fe0-9a51-a53e315ea7dd@.1g2000hsl.googlegroups.com...
> On Dec 26, 1:58 am, "GAZ" <g...@.gaz.com> wrote:
>> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
>>
>> > On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
>> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> >>news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
>> >> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
>> >> >> Hello all,
>> >> >> We have an issue with reports we created using the VS 2005 Team
>> >> >> System.
>> >> >> When
>> >> >> we open a report everything looks fine and report prints fine as
>> >> >> well.
>> >> >> The problem is that when we click the Print Layout button on the
>> >> >> report
>> >> >> we
>> >> >> get a black page and only report title and group headers are
>> >> >> visible.
>> >> >> Mind
>> >> >> you, the report still prints fine on the printer but none of the
>> >> >> data
>> >> >> is
>> >> >> visible in the report.
>> >> >> Any ideas and solutions appreciated.
>> >> >> BR,
>> >> >> GAZ
>> >> > This should help.
>> >> >http://support.microsoft.com/kb/935356/en-us
>> >> > Regards,
>> >> > Enrique Martinez
>> >> > Sr. Software Consultant
>> >> Thanks for the info. Got it but it won't install. Every single hotfix
>> >> reports a failure to install. Has anyone else had any problems with
>> >> the
>> >> installation of the said hotfix?
>> >> BR,
>> >> GAZ
>> > You're welcome. You may have to install the Hot fixes in a particular
>> > order. Have you tried verifying the order in which the hot fixes must
>> > be installed? Hope this helps further.
>> > Regards,
>> > Enrique Martinez
>> > Sr. Software Consultant
>> Thanks for your answer.
>> The hotfixes are acutally rolled into one package which does not give you
>> an
>> option to choose a particular order for installation. When we start the
>> installation it always asks for the SQL installation disk and then it
>> reads
>> files from it and reports that the hotfix installation failed. And so on
>> for
>> each of the components.
>> Well, I guess that we'll have to wait for the SP3 to have the issue
>> resolved.
>> Thanks again for your help.
>> BR,
>> GAZ
>
> You're welcome. Have you checked the Event Viewer for errors that
> might be logged during the process? That might provide some better
> details. Hope this helps further.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Thanks for your help. Unfortunatelly the Event Log is of no help as it does
not provide any useful information. The logs created by the installation
process say that the hotfix package could not be found but i have no idea
what to do with that information as the package physically exists on the
hard drive where the setup process extracted it.
Well, I can only wait for the next SP i guess.
BR,
GAZ|||On Dec 27, 12:06 pm, "GAZ" <g...@.gaz.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:7c2d5ac2-a280-4fe0-9a51-a53e315ea7dd@.1g2000hsl.googlegroups.com...
>
> > On Dec 26, 1:58 am, "GAZ" <g...@.gaz.com> wrote:
> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >>news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
> >> > On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
> >> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >> >>news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
> >> >> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> >> >> >> Hello all,
> >> >> >> We have an issue with reports we created using the VS 2005 Team
> >> >> >> System.
> >> >> >> When
> >> >> >> we open a report everything looks fine and report prints fine as
> >> >> >> well.
> >> >> >> The problem is that when we click the Print Layout button on the
> >> >> >> report
> >> >> >> we
> >> >> >> get a black page and only report title and group headers are
> >> >> >> visible.
> >> >> >> Mind
> >> >> >> you, the report still prints fine on the printer but none of the
> >> >> >> data
> >> >> >> is
> >> >> >> visible in the report.
> >> >> >> Any ideas and solutions appreciated.
> >> >> >> BR,
> >> >> >> GAZ
> >> >> > This should help.
> >> >> >http://support.microsoft.com/kb/935356/en-us
> >> >> > Regards,
> >> >> > Enrique Martinez
> >> >> > Sr. Software Consultant
> >> >> Thanks for the info. Got it but it won't install. Every single hotfix
> >> >> reports a failure to install. Has anyone else had any problems with
> >> >> the
> >> >> installation of the said hotfix?
> >> >> BR,
> >> >> GAZ
> >> > You're welcome. You may have to install the Hot fixes in a particular
> >> > order. Have you tried verifying the order in which the hot fixes must
> >> > be installed? Hope this helps further.
> >> > Regards,
> >> > Enrique Martinez
> >> > Sr. Software Consultant
> >> Thanks for your answer.
> >> The hotfixes are acutally rolled into one package which does not give you
> >> an
> >> option to choose a particular order for installation. When we start the
> >> installation it always asks for the SQL installation disk and then it
> >> reads
> >> files from it and reports that the hotfix installation failed. And so on
> >> for
> >> each of the components.
> >> Well, I guess that we'll have to wait for the SP3 to have the issue
> >> resolved.
> >> Thanks again for your help.
> >> BR,
> >> GAZ
> > You're welcome. Have you checked the Event Viewer for errors that
> > might be logged during the process? That might provide some better
> > details. Hope this helps further.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks for your help. Unfortunatelly the Event Log is of no help as it does
> not provide any useful information. The logs created by the installation
> process say that the hotfix package could not be found but i have no idea
> what to do with that information as the package physically exists on the
> hard drive where the setup process extracted it.
> Well, I can only wait for the next SP i guess.
> BR,
> GAZ
You're welcome. Do you have SQL Server and/or Reporting Services
installed in a non-standard location (i.e., on a D or E partition)? If
that is the case, this could be the problem.
Regards,
Enrique Martinez
Sr. Software Consultant