Importing Error: execution

Showing posts with label execution. Show all posts

Friday, March 23, 2012

Report Caching

When I attempt to set up an snapshot execution I get this error when clicking
the execution link:
Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
Background:
IIS running on - Pentium, Server 2003, 1.8GHz
SQL is on - Itanium, Server 2003 64 bit
As far as I've seen everything else is working fine.
ThanksDoes the ReportServersTempDB exists? Are the objects owned by dbo? If they
are not you will need to change the owner to dbo.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> When I attempt to set up an snapshot execution I get this error when
clicking
> the execution link:
> Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> Background:
> IIS running on - Pentium, Server 2003, 1.8GHz
> SQL is on - Itanium, Server 2003 64 bit
> As far as I've seen everything else is working fine.
> Thanks|||Sorry - figured it out - the operator ran rsconfig with the TEMPdb and had a
typo.
"Daniel Reib [MSFT]" wrote:
> Does the ReportServersTempDB exists? Are the objects owned by dbo? If they
> are not you will need to change the owner to dbo.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > When I attempt to set up an snapshot execution I get this error when
> clicking
> > the execution link:
> >
> > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> >
> > Background:
> >
> > IIS running on - Pentium, Server 2003, 1.8GHz
> > SQL is on - Itanium, Server 2003 64 bit
> >
> > As far as I've seen everything else is working fine.
> > Thanks
>
>|||I was wrong again - it is not fixed. The typo is ReportServersTempDB instead
of ReportServerTempDB (extra s before temp). I can't find where this is
stored. The database is correctly named and this is clearly the problem -
where is this name registered'
Since I didn't do the installation I'm not sure where it came from - we've
got a 64 bit box so the install was not traditional.
"NPShinn" wrote:
> Sorry - figured it out - the operator ran rsconfig with the TEMPdb and had a
> typo.
> "Daniel Reib [MSFT]" wrote:
> > Does the ReportServersTempDB exists? Are the objects owned by dbo? If they
> > are not you will need to change the owner to dbo.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > When I attempt to set up an snapshot execution I get this error when
> > clicking
> > > the execution link:
> > >
> > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > >
> > > Background:
> > >
> > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > SQL is on - Itanium, Server 2003 64 bit
> > >
> > > As far as I've seen everything else is working fine.
> > > Thanks
> >
> >
> >|||The easiest thing for you to do is rename your TempDB to
ReportServersTempDB. This should get you past this problem.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> I was wrong again - it is not fixed. The typo is ReportServersTempDB
instead
> of ReportServerTempDB (extra s before temp). I can't find where this is
> stored. The database is correctly named and this is clearly the problem -
> where is this name registered'
> Since I didn't do the installation I'm not sure where it came from - we've
> got a 64 bit box so the install was not traditional.
> "NPShinn" wrote:
> > Sorry - figured it out - the operator ran rsconfig with the TEMPdb and
had a
> > typo.
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > Does the ReportServersTempDB exists? Are the objects owned by dbo?
If they
> > > are not you will need to change the owner to dbo.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > >
> > >
> > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > When I attempt to set up an snapshot execution I get this error when
> > > clicking
> > > > the execution link:
> > > >
> > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > >
> > > > Background:
> > > >
> > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > SQL is on - Itanium, Server 2003 64 bit
> > > >
> > > > As far as I've seen everything else is working fine.
> > > > Thanks
> > >
> > >
> > >|||What about all of the stored procedures that point to ReportServerTempDB? I
think I will have many places to change the name.
The box is brand new, we could reinstall especially since the dbs are on a
different server.
"Daniel Reib [MSFT]" wrote:
> The easiest thing for you to do is rename your TempDB to
> ReportServersTempDB. This should get you past this problem.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > I was wrong again - it is not fixed. The typo is ReportServersTempDB
> instead
> > of ReportServerTempDB (extra s before temp). I can't find where this is
> > stored. The database is correctly named and this is clearly the problem -
> > where is this name registered'
> >
> > Since I didn't do the installation I'm not sure where it came from - we've
> > got a 64 bit box so the install was not traditional.
> >
> > "NPShinn" wrote:
> >
> > > Sorry - figured it out - the operator ran rsconfig with the TEMPdb and
> had a
> > > typo.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Does the ReportServersTempDB exists? Are the objects owned by dbo?
> If they
> > > > are not you will need to change the owner to dbo.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > >
> > > >
> > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > When I attempt to set up an snapshot execution I get this error when
> > > > clicking
> > > > > the execution link:
> > > > >
> > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > >
> > > > > Background:
> > > > >
> > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > >
> > > > > As far as I've seen everything else is working fine.
> > > > > Thanks
> > > >
> > > >
> > > >
>
>|||It sounds like the SPs are already pointing to that DB, isn't that the error
you are receiving?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> What about all of the stored procedures that point to ReportServerTempDB?
I
> think I will have many places to change the name.
> The box is brand new, we could reinstall especially since the dbs are on a
> different server.
> "Daniel Reib [MSFT]" wrote:
> > The easiest thing for you to do is rename your TempDB to
> > ReportServersTempDB. This should get you past this problem.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > I was wrong again - it is not fixed. The typo is ReportServersTempDB
> > instead
> > > of ReportServerTempDB (extra s before temp). I can't find where this
is
> > > stored. The database is correctly named and this is clearly the
problem -
> > > where is this name registered'
> > >
> > > Since I didn't do the installation I'm not sure where it came from -
we've
> > > got a 64 bit box so the install was not traditional.
> > >
> > > "NPShinn" wrote:
> > >
> > > > Sorry - figured it out - the operator ran rsconfig with the TEMPdb
and
> > had a
> > > > typo.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > Does the ReportServersTempDB exists? Are the objects owned by
dbo?
> > If they
> > > > > are not you will need to change the owner to dbo.
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > rights.
> > > > >
> > > > >
> > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > When I attempt to set up an snapshot execution I get this error
when
> > > > > clicking
> > > > > > the execution link:
> > > > > >
> > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > >
> > > > > > Background:
> > > > > >
> > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > >
> > > > > > As far as I've seen everything else is working fine.
> > > > > > Thanks
> > > > >
> > > > >
> > > > >
> >
> >
> >|||None of the stored procedures in ReportServer point to the typo - they are
all correct. here is something from the log file:
w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
GetPermissions:/Public/WalMartReportNew
w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to GetSystemPermissions
w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Data.SqlClient.SqlException: Invalid object name
'ReportServersTempDB.dbo.ExecutionCache'.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperties(Task task, Boolean updateSqlAgentSchedule)
at
Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRunTime(Task t)
at
Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunTime(Task t)
at Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
at
Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
at Microsoft.ReportingServices.Library.RSService.ListSchedules()
-- End of inner exception stack trace --
"Daniel Reib [MSFT]" wrote:
> It sounds like the SPs are already pointing to that DB, isn't that the error
> you are receiving?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > What about all of the stored procedures that point to ReportServerTempDB?
> I
> > think I will have many places to change the name.
> >
> > The box is brand new, we could reinstall especially since the dbs are on a
> > different server.
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > The easiest thing for you to do is rename your TempDB to
> > > ReportServersTempDB. This should get you past this problem.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > I was wrong again - it is not fixed. The typo is ReportServersTempDB
> > > instead
> > > > of ReportServerTempDB (extra s before temp). I can't find where this
> is
> > > > stored. The database is correctly named and this is clearly the
> problem -
> > > > where is this name registered'
> > > >
> > > > Since I didn't do the installation I'm not sure where it came from -
> we've
> > > > got a 64 bit box so the install was not traditional.
> > > >
> > > > "NPShinn" wrote:
> > > >
> > > > > Sorry - figured it out - the operator ran rsconfig with the TEMPdb
> and
> > > had a
> > > > > typo.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Does the ReportServersTempDB exists? Are the objects owned by
> dbo?
> > > If they
> > > > > > are not you will need to change the owner to dbo.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > rights.
> > > > > >
> > > > > >
> > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > When I attempt to set up an snapshot execution I get this error
> when
> > > > > > clicking
> > > > > > > the execution link:
> > > > > > >
> > > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > >
> > > > > > > Background:
> > > > > > >
> > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > >
> > > > > > > As far as I've seen everything else is working fine.
> > > > > > > Thanks
> > > > > >
> > > > > >
> > > > > >
> > >
> > >
> > >
>
>|||The thing is we don't store this name anywhere. It is only referenced via
the SPs, so some sp is referring to the wrong DB.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:9BF8553B-2CC1-427D-BE45-F2E6CD9505C2@.microsoft.com...
> None of the stored procedures in ReportServer point to the typo - they are
> all correct. here is something from the log file:
> w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
> GetPermissions:/Public/WalMartReportNew
> w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to
GetSystemPermissions
> w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details. --> System.Data.SqlClient.SqlException: Invalid object name
> 'ReportServersTempDB.dbo.ExecutionCache'.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperti
es(Task task, Boolean updateSqlAgentSchedule)
> at
>
Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRu
nTime(Task t)
> at
>
Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunT
ime(Task t)
> at
Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
> at
> Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
> at Microsoft.ReportingServices.Library.RSService.ListSchedules()
> -- End of inner exception stack trace --
>
> "Daniel Reib [MSFT]" wrote:
> > It sounds like the SPs are already pointing to that DB, isn't that the
error
> > you are receiving?
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > > What about all of the stored procedures that point to
ReportServerTempDB?
> > I
> > > think I will have many places to change the name.
> > >
> > > The box is brand new, we could reinstall especially since the dbs are
on a
> > > different server.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > The easiest thing for you to do is rename your TempDB to
> > > > ReportServersTempDB. This should get you past this problem.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > > I was wrong again - it is not fixed. The typo is
ReportServersTempDB
> > > > instead
> > > > > of ReportServerTempDB (extra s before temp). I can't find where
this
> > is
> > > > > stored. The database is correctly named and this is clearly the
> > problem -
> > > > > where is this name registered'
> > > > >
> > > > > Since I didn't do the installation I'm not sure where it came
from -
> > we've
> > > > > got a 64 bit box so the install was not traditional.
> > > > >
> > > > > "NPShinn" wrote:
> > > > >
> > > > > > Sorry - figured it out - the operator ran rsconfig with the
TEMPdb
> > and
> > > > had a
> > > > > > typo.
> > > > > >
> > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > >
> > > > > > > Does the ReportServersTempDB exists? Are the objects owned by
> > dbo?
> > > > If they
> > > > > > > are not you will need to change the owner to dbo.
> > > > > > >
> > > > > > > --
> > > > > > > -Daniel
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > rights.
> > > > > > >
> > > > > > >
> > > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > > When I attempt to set up an snapshot execution I get this
error
> > when
> > > > > > > clicking
> > > > > > > > the execution link:
> > > > > > > >
> > > > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > > >
> > > > > > > > Background:
> > > > > > > >
> > > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > > >
> > > > > > > > As far as I've seen everything else is working fine.
> > > > > > > > Thanks
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||We ended up reinstalling - twice - to resolve our problem. It did point out
an odd thing. Since we're using a 64 bit server, they installed RS by
pointing at our 32 bit development box. Since RS dbs are already on that
box, the operator changed the names of the new dbs to ReportServers and
ReportServersTempDB. The second time he did the install he named them
ReportServer2 and ReportServer2TempDB.
These dbs had to be backed up and restored onto the 64 bit box and thats
when the error change looking for ReportServer2TempDB. So...I went in and
replaced ReportServer2Tempdb back to ReportServerTempdb inall of the stored
procedures. It didn't help, even after restarting all services on both boxes,
with no reference to ReportServer2TempDB in any sp, it was still looking for
it.
We finally solved the problem by installing onto a box that didn't have RS
on it so that we could name the databases correctly. Overall, al pretty odd
day.
If I've left anything out, feel free to ask.
Nancy Shinn
"Daniel Reib [MSFT]" wrote:
> The thing is we don't store this name anywhere. It is only referenced via
> the SPs, so some sp is referring to the wrong DB.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:9BF8553B-2CC1-427D-BE45-F2E6CD9505C2@.microsoft.com...
> > None of the stored procedures in ReportServer point to the typo - they are
> > all correct. here is something from the log file:
> >
> > w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
> > GetPermissions:/Public/WalMartReportNew
> > w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to
> GetSystemPermissions
> > w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
> >
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> more
> > details., ;
> > Info:
> >
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> more
> > details. --> System.Data.SqlClient.SqlException: Invalid object name
> > 'ReportServersTempDB.dbo.ExecutionCache'.
> > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> > at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> > at
> >
> Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> > at
> >
> Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperti
> es(Task task, Boolean updateSqlAgentSchedule)
> > at
> >
> Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRu
> nTime(Task t)
> > at
> >
> Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunT
> ime(Task t)
> > at
> Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
> > at
> > Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
> > at Microsoft.ReportingServices.Library.RSService.ListSchedules()
> > -- End of inner exception stack trace --
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > It sounds like the SPs are already pointing to that DB, isn't that the
> error
> > > you are receiving?
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > > > What about all of the stored procedures that point to
> ReportServerTempDB?
> > > I
> > > > think I will have many places to change the name.
> > > >
> > > > The box is brand new, we could reinstall especially since the dbs are
> on a
> > > > different server.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > The easiest thing for you to do is rename your TempDB to
> > > > > ReportServersTempDB. This should get you past this problem.
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > > > I was wrong again - it is not fixed. The typo is
> ReportServersTempDB
> > > > > instead
> > > > > > of ReportServerTempDB (extra s before temp). I can't find where
> this
> > > is
> > > > > > stored. The database is correctly named and this is clearly the
> > > problem -
> > > > > > where is this name registered'
> > > > > >
> > > > > > Since I didn't do the installation I'm not sure where it came
> from -
> > > we've
> > > > > > got a 64 bit box so the install was not traditional.
> > > > > >
> > > > > > "NPShinn" wrote:
> > > > > >
> > > > > > > Sorry - figured it out - the operator ran rsconfig with the
> TEMPdb
> > > and
> > > > > had a
> > > > > > > typo.
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Does the ReportServersTempDB exists? Are the objects owned by
> > > dbo?
> > > > > If they
> > > > > > > > are not you will need to change the owner to dbo.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
> confers
> > > no
> > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > > > When I attempt to set up an snapshot execution I get this
> error
> > > when
> > > > > > > > clicking
> > > > > > > > > the execution link:
> > > > > > > > >
> > > > > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > > > >
> > > > > > > > > Background:
> > > > > > > > >
> > > > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > > > >
> > > > > > > > > As far as I've seen everything else is working fine.
> > > > > > > > > Thanks
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||At some point you ran rsconfig correct? If not then you were never pointing
at the new DBs. Other then that I am really stumped as to why it didn't
work.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:17E68A5B-97AF-4455-AB84-0F78BDA375B0@.microsoft.com...
> We ended up reinstalling - twice - to resolve our problem. It did point
out
> an odd thing. Since we're using a 64 bit server, they installed RS by
> pointing at our 32 bit development box. Since RS dbs are already on that
> box, the operator changed the names of the new dbs to ReportServers and
> ReportServersTempDB. The second time he did the install he named them
> ReportServer2 and ReportServer2TempDB.
> These dbs had to be backed up and restored onto the 64 bit box and thats
> when the error change looking for ReportServer2TempDB. So...I went in and
> replaced ReportServer2Tempdb back to ReportServerTempdb inall of the
stored
> procedures. It didn't help, even after restarting all services on both
boxes,
> with no reference to ReportServer2TempDB in any sp, it was still looking
for
> it.
> We finally solved the problem by installing onto a box that didn't have RS
> on it so that we could name the databases correctly. Overall, al pretty
odd
> day.
> If I've left anything out, feel free to ask.
> Nancy Shinn
> "Daniel Reib [MSFT]" wrote:
> > The thing is we don't store this name anywhere. It is only referenced
via
> > the SPs, so some sp is referring to the wrong DB.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:9BF8553B-2CC1-427D-BE45-F2E6CD9505C2@.microsoft.com...
> > > None of the stored procedures in ReportServer point to the typo - they
are
> > > all correct. here is something from the log file:
> > >
> > > w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
> > > GetPermissions:/Public/WalMartReportNew
> > > w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to
> > GetSystemPermissions
> > > w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
> > >
> >
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > > An internal error occurred on the report server. See the error log for
> > more
> > > details., ;
> > > Info:
> > >
> >
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > > An internal error occurred on the report server. See the error log for
> > more
> > > details. --> System.Data.SqlClient.SqlException: Invalid object name
> > > 'ReportServersTempDB.dbo.ExecutionCache'.
> > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > > cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> > > at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> > > at
> > >
> >
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> > > at
> > >
> >
Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperti
> > es(Task task, Boolean updateSqlAgentSchedule)
> > > at
> > >
> >
Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRu
> > nTime(Task t)
> > > at
> > >
> >
Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunT
> > ime(Task t)
> > > at
> > Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
> > > at
> > >
Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
> > > at Microsoft.ReportingServices.Library.RSService.ListSchedules()
> > > -- End of inner exception stack trace --
> > >
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > It sounds like the SPs are already pointing to that DB, isn't that
the
> > error
> > > > you are receiving?
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > > > > What about all of the stored procedures that point to
> > ReportServerTempDB?
> > > > I
> > > > > think I will have many places to change the name.
> > > > >
> > > > > The box is brand new, we could reinstall especially since the dbs
are
> > on a
> > > > > different server.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > The easiest thing for you to do is rename your TempDB to
> > > > > > ReportServersTempDB. This should get you past this problem.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > > > > I was wrong again - it is not fixed. The typo is
> > ReportServersTempDB
> > > > > > instead
> > > > > > > of ReportServerTempDB (extra s before temp). I can't find
where
> > this
> > > > is
> > > > > > > stored. The database is correctly named and this is clearly
the
> > > > problem -
> > > > > > > where is this name registered'
> > > > > > >
> > > > > > > Since I didn't do the installation I'm not sure where it came
> > from -
> > > > we've
> > > > > > > got a 64 bit box so the install was not traditional.
> > > > > > >
> > > > > > > "NPShinn" wrote:
> > > > > > >
> > > > > > > > Sorry - figured it out - the operator ran rsconfig with the
> > TEMPdb
> > > > and
> > > > > > had a
> > > > > > > > typo.
> > > > > > > >
> > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > >
> > > > > > > > > Does the ReportServersTempDB exists? Are the objects
owned by
> > > > dbo?
> > > > > > If they
> > > > > > > > > are not you will need to change the owner to dbo.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > -Daniel
> > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > rights.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in
message
> > > > > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > > > > When I attempt to set up an snapshot execution I get
this
> > error
> > > > when
> > > > > > > > > clicking
> > > > > > > > > > the execution link:
> > > > > > > > > >
> > > > > > > > > > Invalid object name
'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > > > > >
> > > > > > > > > > Background:
> > > > > > > > > >
> > > > > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > > > > >
> > > > > > > > > > As far as I've seen everything else is working fine.
> > > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >

Wednesday, March 21, 2012

Report Builder Reports Filtering or Grouping at runtime possible?

I have a problem and i wonder whether it is possible select filter and sort
options at execution time not design time for report builder reportsGo to
http://www.msbicentral.com/Downloads/ReportingServices/RDLFiles/tabid/34/Default.aspx.
You'll have to register for a free login. There is an example of sorting at
run time, there may be one for filtering also.
"Yuksel" wrote:
> I have a problem and i wonder whether it is possible select filter and sort
> options at execution time not design time for report builder reports|||but i am not be able to download sample rdl files
"daw" wrote:
> Go to
> http://www.msbicentral.com/Downloads/ReportingServices/RDLFiles/tabid/34/Default.aspx.
> You'll have to register for a free login. There is an example of sorting at
> run time, there may be one for filtering also.
>
> "Yuksel" wrote:
> > I have a problem and i wonder whether it is possible select filter and sort
> > options at execution time not design time for report builder reports

Report Builder not working - Us Too

Hi, Running RS2005 (was running RS2000 on same system)
When trying to run Report Builder I am getting the following error;

Report Execution Error

The report might not be valid or the server could not process the data.

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

Anyone come across this error before?

Thanks in advance

Scott

anywhere I can go to get an answer to this. Excuse the pun but this renders Report Builder useless

Advaned thanks to anyone who has any idea

Scott

|||

We are getting same error on our shop. Have you found resolution yet?

|||

nothing from anyone....if you find anything I would appreciate anything you find.

I have searched high and low.

One person on another forum said the following;

'Did you upgrade from RS2000 to RS2005? If so, prior to the upgrade, did you have any custom controls or third party controls you may have bought installed? That error message to me seems to say that the report is trying to show a control for which a dll (control source) does not exist. This would lead me to believe - based on you saying RS2000 worked before - that when you did an upgrade, you did not setup these custom controls. '

Maybe it might help

Scott

|||

I spent at lot of time on Friday getting the SelfSSL working on the system. It was set up with the name of the computer, I managed to get it working with ComputerName.domain.com/local etc.

I have just come back to Report builder and it now works!! I am writing this just incase it gives you a clue to how I managed to get it working

Thanks

Scott

Report Builder not working - Us Too

Hi, Running RS2005 (was running RS2000 on same system)
When trying to run Report Builder I am getting the following error;

Report Execution Error

The report might not be valid or the server could not process the data.

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

Anyone come across this error before?

Thanks in advance

Scott

anywhere I can go to get an answer to this. Excuse the pun but this renders Report Builder useless

Advaned thanks to anyone who has any idea

Scott

|||

We are getting same error on our shop. Have you found resolution yet?

|||

nothing from anyone....if you find anything I would appreciate anything you find.

I have searched high and low.

One person on another forum said the following;

Maybe it might help

Scott

|||

I spent at lot of time on Friday getting the SelfSSL working on the system. It was set up with the name of the computer, I managed to get it working with ComputerName.domain.com/local etc.

I have just come back to Report builder and it now works!! I am writing this just incase it gives you a clue to how I managed to get it working

Thanks

Scott

Report Builder not working

Hi, Running RS2005 (was running RS2000 on same system)
When trying to run Report Builder I am getting the following error;

Report Execution Error

The report might not be valid or the server could not process the data.

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

Anyone come across this error before?

Thanks in advance

Scott

anywhere I can go to get an answer to this. Excuse the pun but this renders Report Builder useless

Advaned thanks to anyone who has any idea

Scott

|||

We are getting same error on our shop. Have you found resolution yet?

|||

nothing from anyone....if you find anything I would appreciate anything you find.

I have searched high and low.

One person on another forum said the following;

Maybe it might help

Scott

|||

I spent at lot of time on Friday getting the SelfSSL working on the system. It was set up with the name of the computer, I managed to get it working with ComputerName.domain.com/local etc.

I have just come back to Report builder and it now works!! I am writing this just incase it gives you a clue to how I managed to get it working

Thanks

Scott

Report Builder not working

Hi, Running RS2005 (was running RS2000 on same system)
When trying to run Report Builder I am getting the following error;

Report Execution Error

The report might not be valid or the server could not process the data.

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

Anyone come across this error before?

Thanks in advance

Scott

anywhere I can go to get an answer to this. Excuse the pun but this renders Report Builder useless

Advaned thanks to anyone who has any idea

Scott

|||

We are getting same error on our shop. Have you found resolution yet?

|||

nothing from anyone....if you find anything I would appreciate anything you find.

I have searched high and low.

One person on another forum said the following;

Maybe it might help

Scott

|||

I spent at lot of time on Friday getting the SelfSSL working on the system. It was set up with the name of the computer, I managed to get it working with ComputerName.domain.com/local etc.

I have just come back to Report builder and it now works!! I am writing this just incase it gives you a clue to how I managed to get it working

Thanks

Scott

sql

Friday, March 9, 2012

Report Builder "Report Execution Error"

I get this error with Report Builder "Report Execution Error" the report might not be valid or the server could not process the data.
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

aspnet_wp.exe (PID: 2828) was recycled because memory consumption exceeded the 690 MB (60 percent of available RAM).
Perhaps my server memory is the problem, not enought? I wish it gave me a message relating to the real problem. Its when I am returning a large number of rows but I don't know what the exact limit is.

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

I am hitting a similar issue when i return a large set of data from the Report Server (SQL 2005 Reporting Services). A report will run fine with a smaller set of data, but when I run it with less restrictive filter criteria (which results in a larger data set), I get the error below (which I believe is the same error you were getting):

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

Did anyone manage to fix this error? I can add filters and drag and drop columns, i can see data in filters, but when I run report I get "report execution error the report might not be valid or the server could not process the data"

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Report Builder "Report Execution Error"

What does this error mean?

I did get my report to run, it seems to work if I add another filter or limit the data to reduce the number of rows returned.

see

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=101047&SiteID=1|||I am using domain names and I still get this same error and when I go to EVENT VIEWER, I always get this error as well

|||

Hello,

Did you ever get a response to your posting or figure out what the cause/solution was?

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Any help is greatly appreciated!

|||

Hi, next you get this error, could you please grab recent report server logs (ReportServer__{date}.log) and send them to almineev tata microsoft todtod com

thanks!

|||

Alexandre,

would you mind posting that email address again?

Brian

|||I have sent the above requested info to Alexandre - am awaiting a response|||The error with DTD prohibited usually appears as a result of report processing/rendering running out of memory.|||

Perhaps in the next Service Pack of SQL 2005, MSFT can provide a more specific error message or one that provides more insight into the issue?

Is there any documentation on the amount of data (rows/columns) that SQL reporting services can handle?

Are there settings that allow you to allocate more memory for Reporting Services?

Thanks!

Brian

|||

Hello,

I use the ReportingServices from MS SQL Server 2005 Standard Edition.

The services are used by ASP.NET client (ReportViewer-control). Sometimes, I get the following error-message when I try to open the webform with the ReportViewer-control:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Then I found this thread about the problem in msdn. Now my questions:

- Do the ReportingServices have a problem with large amount of data?

- Which workaround should we use to avoid this problem?

Thanks in advance.

|||

Hi,

Did anyone of you got the solution for this issue.

I am facing the same issue:

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method

Kindly suggest!!!

Regards,

Evan

|||

I have the same isssue .but actually when no data return by the search condition , it also have this issue .

Hope some one can help.

|||

I'm having this issue and it's not disk space or memory, any other help on this issue. There never seemed to be a straight answer.

|||

thanks

|||

Hi,

No, I never received a real answer to this issue, we were in the process of testing Report Builder so we just stopped using it. JJones

Friday, March 23, 2012

Report Caching

Wednesday, March 21, 2012

Report Builder Reports Filtering or Grouping at runtime possible?

Report Builder not working - Us Too

Report Builder not working - Us Too

Report Builder not working

Report Builder not working

Friday, March 9, 2012

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Report Builder "Report Execution Error"

Importing Error

Blog Archive

About Me