running 2005 rdl on a RS 2000 server

We have written some RS 2005 reports on a development server which now needs
to have SQL Server 2005 re-installed due to 'Database Services' not
installing successfully with SP1. Some of the 2005 reports are currently in
use and I wanted to install them on a RS 2000 report manager on another
server during the downtime.
I am receiving the error 'report definition not valid' which relates to the
schema definition when I try to import these reports into Visual Studio 2003.
Changing 2005 to 2003 in the schema def does not work. Is it possible to
run a RS 2005 report in RS 2000 Report Manager? The report does not use any
of the new features available in RS 2005.No it is not possible natively. You might be able to hand edit the RDL (in
notepad) to make it work. I have heard that this might be possible.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bhorwatt" <bhorwatt@.discussions.microsoft.com> wrote in message
news:06261017-B5CD-497E-A468-ABED703B0D8A@.microsoft.com...
> We have written some RS 2005 reports on a development server which now
> needs
> to have SQL Server 2005 re-installed due to 'Database Services' not
> installing successfully with SP1. Some of the 2005 reports are currently
> in
> use and I wanted to install them on a RS 2000 report manager on another
> server during the downtime.
> I am receiving the error 'report definition not valid' which relates to
> the
> schema definition when I try to import these reports into Visual Studio
> 2003.
> Changing 2005 to 2003 in the schema def does not work. Is it possible to
> run a RS 2005 report in RS 2000 Report Manager? The report does not use
> any
> of the new features available in RS 2005.sql

Runaway Log Files

Our production server ran out of disk space over the weekend due to a
runaway log file condition (again).
We had this happen about 2 months ago, prior to SP1, and I reported it here.
MS admitted that had seen the problem, but was not able to reproduce.
In the Event Log, I see thousands of entries like:
Event Type: Warning
Event Source: Schedule and Delivery Processor
Event Category: Logging
Event ID: 123
Date: 8/30/2004
Time: 11:55:16 AM
User: N/A
Computer: KYLE
Description:
The report server failed to write to the trace log.
In the log files, about 8 megabytes in size each until 10 gigabyte disk
capacity was reached, contains repeated entries as follows:
ReportingServicesService!dbcleanup!1308!8/30/2004-11:55:16:: i INFO: Cleaned
0 broken snapshots, 0 chunks
ReportingServicesService!runningjobs!1308!8/30/2004-11:55:16:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 50683 seconds
ReportingServicesService!dbcleanup!e44!8/30/2004-11:55:16:: i INFO: Expiring
old execution log entries
ReportingServicesService!dbcleanup!e44!8/30/2004-11:55:16:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
I was hoping this was fixed in SP1, which we are running now. Any ideas?
thx
JeffI already replied to your other post, but will duplicate info here. We have
found the bug and you should contact PSS for a fix to the issue.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:OYofuMsjEHA.2948@.TK2MSFTNGP11.phx.gbl...
> Our production server ran out of disk space over the weekend due to a
> runaway log file condition (again).
> We had this happen about 2 months ago, prior to SP1, and I reported it
here.
> MS admitted that had seen the problem, but was not able to reproduce.
> In the Event Log, I see thousands of entries like:
> Event Type: Warning
> Event Source: Schedule and Delivery Processor
> Event Category: Logging
> Event ID: 123
> Date: 8/30/2004
> Time: 11:55:16 AM
> User: N/A
> Computer: KYLE
> Description:
> The report server failed to write to the trace log.
> In the log files, about 8 megabytes in size each until 10 gigabyte disk
> capacity was reached, contains repeated entries as follows:
> ReportingServicesService!dbcleanup!1308!8/30/2004-11:55:16:: i INFO:
Cleaned
> 0 broken snapshots, 0 chunks
> ReportingServicesService!runningjobs!1308!8/30/2004-11:55:16:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 50683 seconds
> ReportingServicesService!dbcleanup!e44!8/30/2004-11:55:16:: i INFO:
Expiring
> old execution log entries
> ReportingServicesService!dbcleanup!e44!8/30/2004-11:55:16:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> I was hoping this was fixed in SP1, which we are running now. Any ideas?
> thx
> Jeff
>