Receving error with no description

I have designed quite a few reports over the past few weeks, and today I received the following error:

An error occured during local report processing.
The definition of the report /Discharge7.rdl is invalid.
Exception of type: 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown.

I've never seen this error before. I've gotten errors with typos in names of fields in my expressions, but I've never gotten an error on the 40 someodd other forms I have.

Does anyone know what could be causing this?

Did u tried to preview this report before uploading it to the server, the error says that is not definned correctly, so the report must be bad, when you make a preview on the reporting services it will show you the detailed errors.

|||You can also look at the logs for more detailed error messages. These are located here on a default installation: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles\

For more information about the various Reporting Services log files:
http://msdn2.microsoft.com/en-us/library/ms157403.aspx|||This was while I was previewing it in Visual Studio in the report designer. I haven't published it to the server yet.

Recataloging a log backup disk file

Backup Log DataBaseName to
DISK='\\ServerName\ShareName\Path\FileName.TRN' with
RetainDays=1, Description='Daily Backup Routine'
When I restore a database and logs to an alternate
server, I can restore the full database backup and the
first iteration of the log backups without any problems.
The problem is with all subsequent log backups that were
performed and apended to the file created by the above
statement. I know and can get to the subsequent appended
logs via TSQL, but not an easy task if there are 15
appended log backups on the device. Is there a way I can
recatalog all the log backups so I can use Enterprise
Manager's point an click interface to restore? Will the
STOPAT parameter restore the first log backup, and all
subsequent backups, up to the STOPAT? The command used
to create the log backup is stated above.
Thanx soo much for your help,
D2David,
> Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore?
Not easily. I guess you can write a TSQL script that uses RESTORE HEADERONLY and based on that
inserts data into the backup history tables in msdb. Note that *this is not supported*! EM has an
option to generate backuphistory as you select a backup device in the restore dialog, but that isn't
dine on a file basis, but on a backup basis, so using EM to generate backuphistory, you would have
to go through that dialog 15 times.
> Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT?
No. All RESTORE commands only addresses one backup at a time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Danh" <anonymous@.discussions.microsoft.com> wrote in message
news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
> Backup Log DataBaseName to
> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
> RetainDays=1, Description='Daily Backup Routine'
> When I restore a database and logs to an alternate
> server, I can restore the full database backup and the
> first iteration of the log backups without any problems.
> The problem is with all subsequent log backups that were
> performed and apended to the file created by the above
> statement. I know and can get to the subsequent appended
> logs via TSQL, but not an easy task if there are 15
> appended log backups on the device. Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore? Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT? The command used
> to create the log backup is stated above.
> Thanx soo much for your help,
> D2
>|||Thanks for the help... I ended up doing this...
RESTORE VERIFYONLY FROM DISK='FilePath' WITH
FILE=#,LOADHISTORY
Replaced the # with 1 2 3 4 5 6 7 ...
I just wish it can be done with one command.
>--Original Message--
>David,
>> Is there a way I can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore?
>Not easily. I guess you can write a TSQL script that
uses RESTORE HEADERONLY and based on that
>inserts data into the backup history tables in msdb.
Note that *this is not supported*! EM has an
>option to generate backuphistory as you select a backup
device in the restore dialog, but that isn't
>dine on a file basis, but on a backup basis, so using EM
to generate backuphistory, you would have
>to go through that dialog 15 times.
>> Will the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT?
>No. All RESTORE commands only addresses one backup at a
time.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"David Danh" <anonymous@.discussions.microsoft.com> wrote
in message
>news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
>> Backup Log DataBaseName to
>> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
>> RetainDays=1, Description='Daily Backup Routine'
>> When I restore a database and logs to an alternate
>> server, I can restore the full database backup and the
>> first iteration of the log backups without any
problems.
>> The problem is with all subsequent log backups that
were
>> performed and apended to the file created by the above
>> statement. I know and can get to the subsequent
appended
>> logs via TSQL, but not an easy task if there are 15
>> appended log backups on the device. Is there a way I
can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore? Will
the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT? The command used
>> to create the log backup is stated above.
>> Thanx soo much for your help,
>> D2
>
>.
>

Really simple question on Matrix rendering

Hi all,
I have a little problem with matrix rendering.
Here is a description of my report :
Landscape format (29.7cm by 21cm), report header and footer, one matrix
with 1 line group an 1 column group (easy ^o^)
Height of the matrix columns header : 1,3cm
Height of a line element : 2.3cm
Height of the report header : 1.7cm
Height of the report footer : 0.9cm
Margin (top and bottom) of the report : 0.5cm
So "Page height" - "Margins" - "Report Header" - "Report Footer" -
"Matrix Heder" = 16.1cm
And 16.1 = 7x2.3. So, if i'm right, there will be 7 rows by page
Here is the problem :
When I preview the report, I there are 8 rows instead of 7 on the first
page.
And what is really odd, the second page contains 7 rows, as
excpected...
I tried with a table instead of a matrix, just to see if I get the same
thing.
But with a table, I have 7 rows by page, on each page.
It seems that th matrix doesn'y use the same algorithm to calculate
pagebreaks than the table.
Can someone help me please ?
Thanks
DAOK,
Don't search it seems to be a bug of the preview.
When exporting to pdf, the report is correct.
If someone of the RS Team have some time to waste (^o^), I am
interrested in an explanation of the problem.
Thanks for reading ^O^
Bye