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