Hi,

This is the first time we are being reported such an error.

As you did, I have googled for a while and it looks like there is no clear answer to this problem.

I supposed you have already checked the possible causes that have been reported in some forum. I would recommend this thread : http://forums.asp.net/t/1180524.aspx

Though, I have no specific reason to believe it will help, could you try the following:

• Could you try to remove the schema used for Enesys RS Data Extension query before deploying the report.
  For example, instead of this query:

 

 

<?xml version="1.0" encoding="utf-8" ?>

<root xmlns="http://enesyssoftware.com/schemas">

    <list title="Products" relativeSiteUrl="/sites/demo/" tableName="Products">

        <fields>Title, Category, Supplier, UnitPrice</fields>

        <query>

        </query>

    </list>

    <resultSet>Products</resultSet>

</root>

Use rather this query without the xmlns root attribute

 

<?xml version="1.0" encoding="utf-8" ?>

<root>

    <list title="Products" relativeSiteUrl="/sites/demo/" tableName="Products">

        <fields>Title, Category, Supplier, UnitPrice</fields>

        <query>

        </query>

    </list>

    <resultSet>Products</resultSet>

</root>

 

Could you also try to load your report directly into your report server rather than deploying it through the BI dev studio.

Does it make any difference?

Regards,

 

 

 

---

Frederic LATOUR
ENESYS

Hi,

We have already been reported of such a problem on a 64bits bi-processor machine. It looks like there is something wrong on MS side but we are investigating if we can find a workaround.

Have you applied the net framework 2.0 SP1?

Regards,

---

Frederic LATOUR
ENESYS

Hi,

Yes please, keep me inform as we are eager to find a solution to this problem.

Could you also let me know the hardware configuration of your server? Is it a bi-processor machine?

Regards,

---

Frederic LATOUR
ENESYS

Hi,

We have the same results after applying patches SP1 to dotnet and SP2 to Windows server 2003.

Please note that our Reporting Server is not running in SharePoint integration mode.

We plan to open a call with Microsoft but we'd like to run a standard XML query ( not using your extension) and reproduce the problem before calling Microsoft.

By chance, our xml query experience being limited, have you such a query we can use.

Below you will see a complete error message tracing which is improved with our new version (identification removed and replaced by xxxxxx)

Regards

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 11/27/2007 2:50:05 PM

Event time (UTC): 11/27/2007 1:50:05 PM

Event ID: 4c27bbf73660453c9e069fa7c42829f0

Event sequence: 62

Event occurrence: 1

Event detail code: 0

 

Application information:

Application domain: /LM/W3SVC/1/root/Reportserver-1-128406448722443966

Trust level: RosettaMgr

Application Virtual Path: /Reportserver

Application Path: D:\Apps\Microsoft SQL Server\MSSQL.3\MSSQL.4\Reporting Services\ReportManager\

Machine name: XXXXXXXXX

 

Process information:

Process ID: 5400

Process name: w3wp.exe

Account name: NT AUTHORITY\NETWORK SERVICE

 

Exception information:

Exception type: XmlException

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

 

Request information:

Request URL: XXXXXXXXXXXXXXXX

http://go.microsoft.com/fwlink/events.asp.  

Request path: /Reportserver/Reserved.ReportViewerWebControl.axd

User host address: XXXXXXXXXXXXX

User: XXXXX

Is authenticated: True

Authentication Type: Negotiate

Thread account name: NT AUTHORITY\NETWORK SERVICE

 

Thread information:

Thread ID: 1

Thread account name: NT AUTHORITY\NETWORK SERVICE

Is impersonating: True

Stack trace: at System.Xml.XmlTextReaderImpl.Throw(Exception e)

at System.Xml.XmlTextReaderImpl.ParseDoctypeDecl()

at System.Xml.XmlTextReaderImpl.ParseDocumentContent()

at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)

at System.Xml.XmlDocument.Load(XmlReader reader)

at Microsoft.Reporting.WebForms.WebRequestHelper.ExceptionFromWebResponse(Exception e)

at Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)

at Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)

at Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& fileExtension)

at Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)

at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)

at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

 

 

Custom event details:

For more information, see Help and Support Center at

 

Hi,

We have uploaded the enesys report on another test multiprocessor 32 bits Machine and it works!!!!!!

The problem we have with DB and reporting services on 2 different machine is that the single sign is not working and we have to provide again the same credential .

Anyway we want to solve the 64 bits problems and interested to receive your xml reference query.

Regards