Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: DTD prohibited


This question is answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 6 - Last Post: Dec 21, 2016 4:55 AM Last Post By: Soren Hartig
Soren Hartig

Posts: 13
Registered: 7/17/04
DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Aug 22, 2016 4:41 AM
Hello,
On some machines (IIS's) I get an error saying "For security reasons DTD is prohibited..." And I cannot see where it is from. I run 32-bit ISAPI.
Does anyone know this error?

Edited by: Soren Hartig on Aug 22, 2016 4:41 AM
Daniel Fields

Posts: 622
Registered: 11/29/04
Re: DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Aug 22, 2016 10:29 AM   in response to: Soren Hartig in response to: Soren Hartig
It's an XML processing error. That could be anything from an external file, to a manifest for elements of the operating system. If your application is directly processing XML files, I would start there.

Here is what DTD is http://www.w3schools.com/XML/xml_dtd_intro.asp.

Here is a good explanation of the same problem you are having. There is supposed to be a setting to control the error reporting.
http://stackoverflow.com/questions/13854068/dtd-prohibited-in-xml-document-exception
Soren Hartig

Posts: 13
Registered: 7/17/04
Re: DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 6, 2016 4:39 AM   in response to: Daniel Fields in response to: Daniel Fields
Thank you for your answer, I had hoped on a little more to the point help.
To reproduce (on some IIS’s):
1: Create an ISAPI project.
2: Browse the ISAPI DLL with the IIS administrator.

Result (the green screen of IntraWeb death):

Application error.

Error message: DTD is prohibited.

Line 3:
<!DOCTYPE html>

Depending on the error condition, it might ....
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 17, 2016 1:51 AM   in response to: Soren Hartig in response to: Soren Hartig
Soren Hartig wrote:
Thank you for your answer, I had hoped on a little more to the point help.
To reproduce (on some IIS’s):
1: Create an ISAPI project.
2: Browse the ISAPI DLL with the IIS administrator.

Result (the green screen of IntraWeb death):

Application error.

Error message: DTD is prohibited.

Line 3:
<!DOCTYPE html>

Depending on the error condition, it might ....

Hi Soren,

the green screen of death ;-) has a little more information than this. If you have stack trace enabled in your IW application (more info here: http://docs.atozed.com/docs.dll/development/Using%20the%20Exception%20Logger.html), the exception screen will contain the stack trace and show exactly where the exception occurred.

Can you please check this and let me know?
Soren Hartig

Posts: 13
Registered: 7/17/04
Re: DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 24, 2016 7:17 AM   in response to: Alexandre Machado in response to: Alexandre Machado
Sorry for the delay. I'll try to get the stack trace, problem is that I don't get this error on my own PC.
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Nov 1, 2016 1:33 AM   in response to: Soren Hartig in response to: Soren Hartig
Soren Hartig wrote:
Sorry for the delay. I'll try to get the stack trace, problem is that I don't get this error on my own PC.

The exception logger, among other things, also saves the complete stack trace + exception information when enabled (in a sub folder). You just need to enable it and wait till the problem occurs in production. Then you will have a file containing the whole stack trace.
Soren Hartig

Posts: 13
Registered: 7/17/04
Re: DTD prohibited  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 21, 2016 4:55 AM   in response to: Soren Hartig in response to: Soren Hartig
And the problem was only a bad formatted web.config in a asmx web service that the IntraWeb server called.
A very misleading error message....
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02