February 24, 2010 at 2:42 am
Hi All,
We have a problem where reports stop working intermittently on one of our servers.
The other servers we have which are running the same reports and which are less powerful that this machine are having no issues whatsoever. Also as far as I can see they are set up in the same way.
A server reboot seems to clear this for a while but then it starts happening again.
This is the exact error message we are getting:
Class: System.Xml.XmlException
Source: System.Xml
Stack Trace: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res, String arg)
at System.Xml.XmlTextReaderImpl.ParseDoctypeDecl()
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)
Procedure Name: Throw
Location: System.Xml.XmlTextReaderImpl
Message: 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.
This is the server which is getting the error:
Processors: 4 x Quad Xeon E5520 @ 2.27GHz
Memory: 12GB
OS: Windows 2003 R2 Enterprise 32bit with SP2
Page File: 12GB
Boot.ini: 3G and PAE switches on
SQL Server: 2005 with SP3
AWE: enabled
Min Memory: 2Gb
Max Memory: 8GB
Memory Used by SQL Server: 8Gb (via windows performance monitor)
Group Policy: "Lock pages in memory" given to the user running the SQL server
There must be something different about this server but I cannot see anything obvious.
Looking at the SSRS logs I can see the following error:
w3wp!library!7!02/22/2010-08:58:12:: i INFO: Call to RenderFirst( '/Dyesect/Technical Dyelot Performance (General Summary)' )
w3wp!bufferedresponse!7!02/22/2010-08:58:12:: w WARN: Cannot flush response to the client. The remote host closed the connection. The error code is 0x80072746.
w3wp!webserver!7!02/22/2010-08:58:12:: i INFO: Processed report. Report='/Dyesect/Technical Dyelot Performance (General Summary)', Stream=''
Any help would be greatly appreciated.
Regards,
Paul
August 31, 2010 at 9:33 am
Did you find a solution to this problem? We're seeing exactly the same thing at one customer site. We know they increased the size of the virtual memory paging file over the weekend, but we don't think anything else has changed.
Thanks,
David.
August 31, 2010 at 9:50 am
Yes we did find a solution.
The problem was with one of our applications sending a massive xml string to one of the reports.
Once we'd sorted that out things seemed to go back to normal.
We do have the same problem on some of our servers but we think its due to the set up of the server rather than anything we have done as developers. A reboot tends to fix it which is not an ideal solution but is ok for our purposes at present.
The error is definitely memory related but it seems very hard to track down exactly what is causing it.
Have you tried setting the virtual memory back to see if that sorts things out?
Paul
September 6, 2010 at 8:09 am
Thanks for your reply - we asked the customer to roll back the changes they made and the problem has gone away. We've yet to find out exactly what they changed though, as I think it was more than just the VM settings.
David.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply