Showing posts with label further. Show all posts
Showing posts with label further. Show all posts

Wednesday, March 21, 2012

ReportServer as a separate component

Can the ReportServer web services application be installed without installing SQL Server?

Let me explain a little further what I'm trying to do and if I need to take a different path, I'm open to suggestions.

I am going to be using XML files for data input and RDL files to describe the reports themselves. That being said, I am not in need of a database of any kind (and don't want to be required to use one), but I want to take advantage of Microsoft's rendering capabilities. I have looked into the ReportViewer control, but that control doesn't support all of the rendering extensions that ReportServer does (mostly HTML). I know that ReportServer stores its metadata in a database on the local SQL Server, but I didn't know if there was maybe a standalone installation that I could get my hands on that exposed the SOAP API, but didn't require an SQL Server (or any other database for that matter) for it to exist.

Thanks,
Ken

In order to run the Report Server, you do need a SQL Server database engine to be deployed somewhere on your network - not strictly on the local computer.

To get all the rendering capabilities of the report server, you will need to deploy a report server.

If you don't want to use a report server at all, then the ReportViewer control that ships with Visual Studio 2005 is your best bet.

If you don't want to deploy a report server for every instance of your application, you might choose to use a remote report server. In SQL Server 2005, reporting services provides a method for loading a report on the server without saving it in the report server namespace. To do this you use the LoadReportDefinition SOAP API. You'll also need to add any users of your applications to the System User role on the report server, at the system scope (Site Settings in Report Manager, then edit site wide security settings). Your application would then use the LoadReportDefinition method and privision any information needed through the report server execution SOAP endpoint.

Otherwise, you're stuck iinstalling a report server and then choosing either to have a local sql server relational database or a remote one.

-Lukasz

Tuesday, March 20, 2012

Reports Not Refreshing

Hi
We have a report which is linked to a subreport of further information. The
subreport is simply linked through URL access with querystring parameters. If
however you return to the main report and then click a subreport, we get the
swirling logo (which I assumed would mean that it was refreshing), but the
same data gets returned even though more has been added since. Only clicking
the refresh button will the data get refreshed!
Does anyone have any ideas why this report is not refreshing by simply
clicking through?
Thanks in advance
DaveI'm having the same issue. There was a post on the 12th July that suggested
adding &rs:ClearSession=true to the URL you could give that a try.
James
"Dave Court" wrote:
> Hi
> We have a report which is linked to a subreport of further information. The
> subreport is simply linked through URL access with querystring parameters. If
> however you return to the main report and then click a subreport, we get the
> swirling logo (which I assumed would mean that it was refreshing), but the
> same data gets returned even though more has been added since. Only clicking
> the refresh button will the data get refreshed!
> Does anyone have any ideas why this report is not refreshing by simply
> clicking through?
> Thanks in advance
> Dave

Wednesday, March 7, 2012

ReportIoError 2 - Further Info

Context
--
The first of the failed log backups was run after a series
of indexes on the database were rebuilt.
Recovery mode is changed to "bulk-logged" before rebuiding
indexes. This is followed by the log backup and then
recovery mode is changed back to "full".
Additional Error Messages in SQL Server Log
---
BackupMedium::ReportIoError: write failure on backup
device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
system error 2(error not found).
Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
0x3BE50000, Size: 65536, Position: 4293497344, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
\backup\Proclaim_backup.bak
BACKUP failed to complete the command BACKUP LOG
[Proclaim] TO DISK = N'D:\mssql7
\backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMATHi Kim,
When ever you perform a recovery model change, it is always suggested to do
a full database backup and
then goahead with Transaction log backup.
This I/O issue can araises due to free space in hard disk, permissions on
the disk.
Thanks
Hari
MCDBA
"Kim" <anonymous@.discussions.microsoft.com> wrote in message
news:25bce01c46248$42024970$a601280a@.phx
.gbl...
> Context
> --
> The first of the failed log backups was run after a series
> of indexes on the database were rebuilt.
> Recovery mode is changed to "bulk-logged" before rebuiding
> indexes. This is followed by the log backup and then
> recovery mode is changed back to "full".
>
> Additional Error Messages in SQL Server Log
> ---
> BackupMedium::ReportIoError: write failure on backup
> device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
> system error 2(error not found).
> Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
> 0x3BE50000, Size: 65536, Position: 4293497344, UMS:
> Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
> OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
> m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
> \backup\Proclaim_backup.bak
> BACKUP failed to complete the command BACKUP LOG
> [Proclaim] TO DISK = N'D:\mssql7
> \backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
> NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT|||Thanks for the suggestion.
I'll add a full backup to the scheduled job before and
after the recovery mode change and see if the issue
persists.

ReportIoError 2 - Further Info

Context
The first of the failed log backups was run after a series
of indexes on the database were rebuilt.
Recovery mode is changed to "bulk-logged" before rebuiding
indexes. This is followed by the log backup and then
recovery mode is changed back to "full".
Additional Error Messages in SQL Server Log
BackupMedium::ReportIoError: write failure on backup
device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
system error 2(error not found).
Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
0x3BE50000, Size: 65536, Position: 4293497344, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
\backup\Proclaim_backup.bak
BACKUP failed to complete the command BACKUP LOG
[Proclaim] TO DISK = N'D:\mssql7
\backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT
Hi Kim,
When ever you perform a recovery model change, it is always suggested to do
a full database backup and
then goahead with Transaction log backup.
This I/O issue can araises due to free space in hard disk, permissions on
the disk.
Thanks
Hari
MCDBA
"Kim" <anonymous@.discussions.microsoft.com> wrote in message
news:25bce01c46248$42024970$a601280a@.phx.gbl...
> Context
> --
> The first of the failed log backups was run after a series
> of indexes on the database were rebuilt.
> Recovery mode is changed to "bulk-logged" before rebuiding
> indexes. This is followed by the log backup and then
> recovery mode is changed back to "full".
>
> Additional Error Messages in SQL Server Log
> BackupMedium::ReportIoError: write failure on backup
> device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
> system error 2(error not found).
> Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
> 0x3BE50000, Size: 65536, Position: 4293497344, UMS:
> Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
> OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
> m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
> \backup\Proclaim_backup.bak
> BACKUP failed to complete the command BACKUP LOG
> [Proclaim] TO DISK = N'D:\mssql7
> \backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
> NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT
|||Thanks for the suggestion.
I'll add a full backup to the scheduled job before and
after the recovery mode change and see if the issue
persists.