Root Element MIssing & For security reasons DTD is prohibited in this XML document

This error comes up in the print preview and nothing prints.

We are using VS-2005, SQL 2005 and SSRS 2005.

We had the same problem yesterday , so we have reinstalled IIS, .Net Framework 2.0 and Reporting Services, then reconfigured RS security, uploaded all the reports and enabled remote errors. After doing everything this error was gone and we were operating pretty fine.

Suddenly just we started getting the same annoying message."ROOT ELEMENT MISSING" from Report Server and from Report Manager we have "

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. "

Please Help. I need to fix this ASAP.

Are you running out of memory on the server?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=128205&SiteID=1

|||

Thanks Greg for the quick response.

We just restarted everyting and it seems all the reports are working fine now. But what annoys me is why does this happen. Do you think the Buffer cashe was full and it triggred this operation. If yes then what do we have to do to increase the Buffer cache.(we have 150000 i.e 15gigs of buffer settings.)

If not buffer cache then what ?

Please help me understand this problem.

|||

I am an associate of VDeepak, the problem is definately not as simple as low memory. The report that is erroring out is only a page or so, and we routinely run 200 + page reports on this server. If it helps, here is the trace from the application error log:

Event Type: Error
Event Source: IHRS
Event Category: None
Event ID: 0
Date: 8/10/2007
Time: 9:28:40 PM
User: N/A
Computer: AFTRAHR-APP04
Description:
2007-08-10 21:28:40,225 [1] ERROR IHRSMESSAGE [(null)] - Root element is missing.AFTRA\escherrer
System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at Microsoft.Reporting.WinForms.WebRequestHelper.ExceptionFromWebResponse(Exception e)
at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

|||

Usually what this means in a webapp with localmode (RDLCs) is that the deployed RDLC didn't... deploy or build right...

I am not going to say this correctly, but the general idea is: when you get the "root element is missing" the actual RDLC that deployed is completely empty.

Here I see WinForms and ServerMode -- so it isn't quite the same thing, it's just a suspiciously similar error. So I am wondering: could something be wrong in the ReportServer Tempdb? Could this be refreshed after a restart?

>L<

|||

I think you may be on the right track. It is indeed cleared up after a restart, but doesnt re-occur for any particular reason. Every time we think we know what triggers it we restart and trigger again but it doesnt reoccur.

We noticed after a deloy it happened, so we restarted and it was gone. Then re-deployed the same reports and no problem. Then yesterday I was changing a report server timeout setting and the problem came back. Restarted and problem was gone. Changed setting again but problem did not reoccur.

Very frustrating indeed.

|||

Hmm.. When it happens, does it always happen with the same reports? How are you doing the deploy?

>L<

|||

We deploy from visual studio 2005 to a RS 2005 instance. The one time we correlated deployment from a set of three reports it did not ever cause the error again. There was one report in particular that the error was discovered on but it exists on all reports.

To be specific, when this error is happeneing, we can view a 1 page report, but print preview gives the root element missing error.

|||>>We deploy from visual studio 2005 to a RS 2005 instance

Have you tried the "upload file" method of deploying rather than from Visual Studio? It's not likely to make any difference, given that you can actually *see* the report although not *print preview* *** . IOW, if the report definition is not empty, then it is not, no matter what you're trying to do with it. -- This is really cr*ppy, btw, you have my sympathies.

*** I didn't realize before that the same report was giving these intermittent, different results *without* a restart.

If you can see the report and not print preview it sounds more like the report definition is there but not available. Could it be locked? Again, I'm thinking the reportserver tempdb, but I do not have any information about HTH or WTH this might occur <s>. But the fact that a timeout made a difference is suspicious.

A couple of things I'm going to ask just in case it rings a bell for any MS guys reading:

* -- were these report definitions migrated from RS 2000? what about the SQL server? Did you by any chance upgrade RS from 2000 to 2005? (I'm thinking maybe run DBCC UPDATEUSAGE in that case?)

* -- anything interesting in either the SQL Server logs or the available reports for either the ReportServer or ReportServerTempDB databases for the time period(s) in question?

>L<