Foreach file

I loop through a list of files in a directory and one of the tasks in the container is to validate the xml file against dtd if this succeeds i process the file and the lforeachloop gets the next file. If validation fails i then delete that file,the problem i am having is that whe the xml task fails it stops the whole for each container even though the failparentonfailure is set to false.

How can i get the foreach container to continue to the next file after the xmltask fails (validation) and the file is succesfully deleted?

PS is their away of posting the DTSx screenshot as this might explain it better?

Try setting the xml task's ForceExecutionResults property to Success.|||

If the xml task(valid) is success i extract the nodes if it fails(invalid) i delete the file. If i force the success it will fail down the line when it tries to process an invalid xml file. i.e Get file --> if valid Process File/If invalid delete file --> Get next File.

Below the result of next task if a force success

[XML Task] Error: An error occurred with the following error message: "Data at the root level is invalid. Line 1, position 1.".

|||Set MaximumErrorCount (package properties) to some high number, perhaps 999 or something like that.

The default is 1, so even though you've told it not to fail the parent, the package still sees one error and then stops.|||

I dont want to tamper with the package error setting as some items exit on failure correctly. What i want is in my loop conatiner if the validate xml fails i delete the invalid file and get the next file. The scope of the failrwe is within the foreach loop and the only step i want it to continue looping through files is when i detect an invalid file and successfuly delete it.

I think it would be easier to understand what i am trying to do if i could post the screen shot of the control flow.

|||

MikeTomkies wrote:

I think it would be easier to understand what i am trying to do if i could post the screen shot of the control flow.

You can send me the screen shot via my posted e-mail on my profile. I can then host it and post it here.|||Did you get my screenshot, Anybody else able to help?

For security reasons DTD is prohibited in this XML document.

When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.

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.

Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.

And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?

My development’s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727

Hi Kevin,

We found an issue like this in a recent version of pre-release SQL 2005 Reporting Services SP2. If you are running versions of Reporting Services prior to SP2, please let me know. Otherwise, this will be fixed in the the final release of SP2.

|||

I'm seeing this occur in both SP1, and the CTP release of SP2.

Please advise. Reports render some of the time, but the vast majority I revceive the same error.

|||

We just installed SP2 in our organization. I am running a very large dataset which brings out about 4 million rows. When I run this report I am getting this error.

For security reasons DTD is prohibited in this XML document......

Please help...

For security reasons DTD is prohibited in this XML document.

When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.

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.

Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.

And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?

My development’s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727

Hi Kevin,

We found an issue like this in a recent version of pre-release SQL 2005 Reporting Services SP2. If you are running versions of Reporting Services prior to SP2, please let me know. Otherwise, this will be fixed in the the final release of SP2.

|||

I'm seeing this occur in both SP1, and the CTP release of SP2.

Please advise. Reports render some of the time, but the vast majority I revceive the same error.

|||

We just installed SP2 in our organization. I am running a very large dataset which brings out about 4 million rows. When I run this report I am getting this error.

For security reasons DTD is prohibited in this XML document......

Please help...

For security reasons DTD is prohibited in this XML document and System.OutOfMemory

I am getting this error while running a very large dataset. Please help..

The full description of the error is : "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."

I am having hard time figuring out a solution for this. I am using sql 05, SSRS 05, Report viewer

I have a very big Dataset which pulls up millions of rows.

When I pass parameters from Windows forms to run on Reportviewer through webservice it is giving me "System.OutOfMemory" Exception and when I pass same parameters on the server(i.e. http:\\server\reportmanager) it is giving me this error "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".

I have no problem when I pass small dataset.

Please help me solve this annoying this problem.

|||

I found this article and i guess this should answer your question.

http://support.microsoft.com/default.aspx/kb/909678

|||

Thanks Chaitanya for the informative link.

I've already checked that and done necessary changes for the long running reports.

Right now I was able to print 55541 pages. We decided to take printout in batches if the requirement more than 55541. They best possible solution would be schedule a report and call it from Windows service using webservices.

Please let me know if we can print unlimited pages(i.e about 3 million pages).

For security reasons DTD is prohibited in this XML document

I am getting this error while running a very large dataset. Please help..

The full description of the error is : "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."

I am having hard time figuring out a solution for this. I am using sql 05, SSRS 05, Report viewer

I have a very big Dataset which pulls up millions of rows.

When I pass parameters from Windows forms to run on Reportviewer through webservice it is giving me "System.OutOfMemory" Exception and when I pass same parameters on the server(i.e. http:\\server\reportmanager) it is giving me this error "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".

I have no problem when I pass small dataset.

Please help me solve this annoying this problem.

|||

I found this article and i guess this should answer your question.

http://support.microsoft.com/default.aspx/kb/909678

|||

Thanks Chaitanya for the informative link.

I've already checked that and done necessary changes for the long running reports.

Right now I was able to print 55541 pages. We decided to take printout in batches if the requirement more than 55541. They best possible solution would be schedule a report and call it from Windows service using webservices.

Please let me know if we can print unlimited pages(i.e about 3 million pages).

For security reasons DTD is prohibited in this XML document

I have seen one other post about this and using IP addressing rather that DNS names - I am using DNS.

I have a large report that runs fine in report manager, but as soon as I try and export it to Excel it takes an age to run and I get the above error.

Any ideas anyone?

Oh, and I export loads of other reports to Excel with no problems on the same server.

More info: Curiously, I can output to pdf, xml, in fact anything except Excel.

I'm stumped

|||I can confirm that I am getting the same error when exporting with the excel plugin with large amounts of data. All other plugins work fine, just excel that's causing problems.|||

We've seen a few customers who have seen this and I'm trying to get a repro. I've tried using reports that use large result sets but cannot go beyond a certain number of rows as there is a max row limit in Excel. Then I tried to use a wide data set. Sure enough, it takes a long time when exporting to Excel but ultimately it succeeds. I've tried applying some memory pressure as well. I'm not sure if there is anything about the report or other settings that may be causing this. It will be great if you can provide additional details.

Thanks,

Sharmila

|||

I have sent a reporting services error log to someone at MS - can't remember whom and I'm not at work till next week to check my email.

It seems to be a large result set and only when rendering to Excel. Calling the report directly from within an ASP page (with the parameter to render directly to Excel) makes no difference. There are not memory problems as far as I can see, because I have tried it when the server is very quiet - with the same result. It must be a setting somewhere.

|||Sharmila - I could try and send you a data source and report if you like to see if the same thing happens on your system|||

This is now happening on a large number of reports in our reporting regime. Does anyone have a clue as to whats causing this?

Server is Windopws 2003 SP1, all clients are Windows XP SP2

|||

Please see this related thread

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

|||

Sure, you can send it to sharmila dot vijayan at microsoft dot com.

Thanks,

Sharmila

|||

Can you send me the report and other details in order for me to get a repro?

Thanks,

Sharmila

|||RDL, Data and dataset (in the form of a spreadsheet - must be pulled into an SQL server table to work) sent to Sharmila|||

I have the same issue when I tried to export reports to excel, pdf and other formats. I can display reports on aspx page. I can even pass parameters from the ASPX page from the buttonclick event. Everything works fine except the export option. How did you guys fix your problem? Anyhelp is highly appreciated. Thanks, Sundar

For security reasons DTD is prohibited in this XML document

I have seen one other post about this and using IP addressing rather that DNS names - I am using DNS.

I have a large report that runs fine in report manager, but as soon as I try and export it to Excel it takes an age to run and I get the above error.

Any ideas anyone?

Oh, and I export loads of other reports to Excel with no problems on the same server.

More info: Curiously, I can output to pdf, xml, in fact anything except Excel.

I'm stumped

|||I can confirm that I am getting the same error when exporting with the excel plugin with large amounts of data. All other plugins work fine, just excel that's causing problems.|||

We've seen a few customers who have seen this and I'm trying to get a repro. I've tried using reports that use large result sets but cannot go beyond a certain number of rows as there is a max row limit in Excel. Then I tried to use a wide data set. Sure enough, it takes a long time when exporting to Excel but ultimately it succeeds. I've tried applying some memory pressure as well. I'm not sure if there is anything about the report or other settings that may be causing this. It will be great if you can provide additional details.

Thanks,

Sharmila

|||

I have sent a reporting services error log to someone at MS - can't remember whom and I'm not at work till next week to check my email.

It seems to be a large result set and only when rendering to Excel. Calling the report directly from within an ASP page (with the parameter to render directly to Excel) makes no difference. There are not memory problems as far as I can see, because I have tried it when the server is very quiet - with the same result. It must be a setting somewhere.

|||Sharmila - I could try and send you a data source and report if you like to see if the same thing happens on your system|||

This is now happening on a large number of reports in our reporting regime. Does anyone have a clue as to whats causing this?

Server is Windopws 2003 SP1, all clients are Windows XP SP2

|||

Please see this related thread

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

|||

Sure, you can send it to sharmila dot vijayan at microsoft dot com.

Thanks,

Sharmila

|||

Can you send me the report and other details in order for me to get a repro?

Thanks,

Sharmila

|||RDL, Data and dataset (in the form of a spreadsheet - must be pulled into an SQL server table to work) sent to Sharmila|||

I have the same issue when I tried to export reports to excel, pdf and other formats. I can display reports on aspx page. I can even pass parameters from the ASPX page from the buttonclick event. Everything works fine except the export option. How did you guys fix your problem? Anyhelp is highly appreciated. Thanks, Sundar