IE debugging page 4: F12 developer tool console error message (Windows)

The F12 tool console can report errors and information messages that occur during runtime. This article describes error messages and provides suggestions on how to correct these errors.

Introduction

The error message in the F12 tool console provides Code (for example, sec7111 or html1114) that provides error information. These codes and messages are displayed on the "console" and "script" tabs of the F12 tool. For JavaScript programmers, this code is triggered by Windows Internet Explorer. ActiveX and browser extension developers can also send these errors and messages.

The tables following this topic are divided into several parts, including code, messages, instructions, and (when applicable) suggestions for solving the problem. Although the description in this table provides a starting point for problem debugging, the best way to  is to access the developer forum or Internet Explorer Developer Center online.

Security Error

The format of these errors is sec7.Xxx(For example, sec7113 ). These errors reflect the security conditions enforced by Windows Internet Explorer 9, such as mixed content and tracking protection.

Code	Message	Description	Recommended Solution
Sec7111	"HTTPS Security[Name of resource]Threat"	The Secure Hypertext Transfer Protocol (https) page contains insecure (mixed) content.	Do not include insecure content on the HTTPS page.
Sec7112	"[Url]The script is blocked because the MIME type does not match"	The HTTP Response Header of the Javascript file specified by the URL has the "x-Content-Type-options: nosniff" header, but there is no content type declaration.	Add the correct content type of a Javascript file (such as text/JavaScript, application/JavaScript). For a complete list of details and content types, see mime processing changes in Internet Explorer.
Sec7113	"Ignore CSS because the MIME type does not match"	The imported style sheet is not used because of the incorrect MIME type in the HTTP header.	Ensure that the style sheet file is transmitted using the correct HTTP Response Header that contains the text/CSS content type. For more information, see mime processing changes in Internet Explorer.
Sec7114	"The download on this page has been blocked by tracking protection.[Url provided here]"	You have used tracking protection to block scripts or content.	None-the user has started.
Sec7115	": Visited and: link styles only have different colors. Some styles are not applicable to: visited. "	You have used the visited and link styles to change multiple attributes, such as the font or size.	Only the color attribute is changed.

 

Note:Internet Explorer does not check the MIME type of the style sheet for websites in the security area trusted by users.

HTML code

The code format is html1xxx (for example, html1115 ). They can specify errors or states that developers can control or control.

Code	Message	Description	Recommended Solution
Html1112	"From[Encoding]To[Encoding]Code Page restarts"	Specifies a different code page from the server.	Use the same code page as the server to avoid messages.
Html1113	Slave[Mode]To[Mode]The document mode is restarted.	The document mode required by the web page is not the document mode currently set by the browser.	This message is displayed when you browse other pages, so it is not controlled by developers.
Html1114	"[Domain]Code page[CodePage]Replaced conflicting[Domain]Code Page in[CodePage]"	Specify the conflicting code page in the HTTP header and tag of the website.	Resolves the code page conflict.
Html1115	"The X-UA-compatible meta tag is ignored ("[Meta tag]") Because the document mode is complete"	Generally, the "meta" tag is placed after the "script" or "style" Declaration (fixed the document mode of the page.	Try to move the meta tags that match the X-UA forward in the header. It is best to place it after "<title>" and character set value.
Html1116	"The meta tag that matches the X-UA ("[Meta tag]") Because the previous meta tag conforms to the X-UA ("[Meta tag]") And ignore"	In the	Except for leaving a "meta compliant with the X-UA" tag, all other tags are removed and make sure that they are positioned as before the header as much as possible. It is best to place it after "<title>" and character set value.
Html1200	"[Domain]In the Compatibility View list of Internet Explorer 9 ('[Path to local Compatibility View list]. "	The current website is listed in the internal list of Internet Explorer.	Website developers can follow the Guide to delete their websites from the Compatibility View list. Microsoft regularly updates this list, so these changes can be downloaded and reflected.
Html1201	"[Domain]Is the website you added to the "Compatibility View. "	You have clicked the "Compatibility View" button of the current website or added the website through "Compatibility View Settings.	The user has started.
Html1202	"[Domain]Running in Compatibility View because "show Intranet site in Compatibility View" is selected ". "	You have selected the "show Intranet site in Compatibility View" check box in "Compatibility View Settings.	You need to press Alt + T, click "Compatibility View Settings", and then clear the "show Intranet site in Compatibility View" check box.
Html1203	"[Domain]You have configured the Group Policy to run in Compatibility View. "	The Network Administrator has specified that the webpage will run in Compatibility View.	You must contact the network administrator.
Html1204	"[Domain]Running in Compatibility View because "show all websites in Compatibility View" is selected ". "	You have selected the "show all websites in Compatibility View" check box in "Compatibility View Settings.	You need to press Alt + T, click "Compatibility View Settings", and then clear the "show all websites in Compatibility View" check box.
Html1300	"Navigation"	Navigate to the new page or the current page is refreshed.	This is an information message, not an error. To filter this message, right-click the console pane, click filter, and deselect information ".

 

HTML5 analysis program warning

The following warning may appear during verification during HTML analysis. These warnings do not necessarily mean that the page is damaged, but the provided HTML is invalid according to the HTML5 standard. Content created based on earlier versions of HTML or XHTML may be invalid in HTML5, especially in the use of doctype. For more information, see create a standardized website.

Common causes of these warnings include missing or extra characters, and tag mismatch. After these warnings are resolved, the compatibility with earlier browsers and the HTML5 standard compliance of webpages will be improved. To help identify the warning source, Internet Explorer contains line and character offset information and links to the location where the problem occurs.

Code	Message
Html1400	"The starting character referenced by the digit character does not meet the requirements. It must be [0-9]. "
Html1401	"The starting character referenced by the hexadecimal number character is not required and should be: [0-9], [A-F], or [A-F]. "
Html1402	"The end Semicolon"; "is missing for the character reference. "
Html1403	"Numeric character reference is not resolved to a valid character. "
Html1404	"Unrecognized name character reference. "
Html1405	"Invalid character: U + 0000 null. Do not use null characters. "
Html1406	"Invalid start mark:" <?". The question mark cannot be used as the start mark. "
Html1407	"Invalid Tag name. The first character must be [A-Za-Z]. "
Html1408	"Invalid end mark" </> ". The end tag should not be empty. "
Html1409	"Invalid attribute name character. Attribute names cannot contain ("), ('), (<), or (= ). "
Html1410	"Invalid attribute values without quotation marks. Attribute values without quotation marks cannot contain ("), ('), (<), (=), or ('). "
Html1411	"The end of the file does not meet the requirements. "
Html1412	"The comment format is incorrect. The comment should be "<! . "
Html1413	"Invalid characters: U + 003e greater-than sign (> )"
Html1414	"Invalid character: U + 0021 exclamation mark (!) "
Html1415	"Invalid characters: U + 002d hyphen-minus (-)"
Html1416	"The character ending with the comment does not meet the requirements. It should be "--> ". "
Html1417	"Empty doctype. The shortest valid doctype is "<! Doctype HTML> ". "
Html1418	"Doctype contains invalid characters. "
Html1419	"Doctype contains non-conforming keywords. The keyword should be "public" or "system ". "
Html1420	The keyword "" public "or" system "should not be enclosed in quotation marks. It must be a space. "
Html1421	"The format of the end tag is incorrect. The end tag should not contain attributes. "
Html1422	"The start tag format is incorrect. Follow U + 003e greater-than sign (>) after the end slash ). "
Html1423	"The start tag format is incorrect. Properties should be separated by spaces. "
Html1424	"Invalid character"
Html1500	"The tag cannot end automatically. Use an explicit end tag. "
Html1501	"The end of the file does not meet the requirements. "
Html1502	"Doctype does not meet the requirements. Only one doctype is allowed, and it must appear before all elements. "
Html1503	"Start flag does not meet the requirements. "
Html1504	"The End mark does not meet the requirements. "
Html1505	"The Character Mark does not meet the requirements. "
Html1506	"The tag does not meet the requirements. "
Html1507	"Invalid character: U + 0000 null. Do not use null characters. "
Html1508	"The end tag does not match. "
Html1509	"The end tag does not match. "
Html1510	"The required node is not in the scope. "
Html1511	"A non-conforming Header element exists outside of"
Html1512	"The end tag does not match. "
Html1513	"Find the redundant" <HTML> "tag. Each document must contain only one <HTML> mark. "
Html1514	"Find the redundant" <body> "mark. Each document must contain only one <body> mark. "
Html1515	"Find" <frameset> "at the very back of the document ". This tag should appear before "<body>" is created. "
Html1516	"Invalid nesting. Header tags such as
Html1517	"Invalid nesting. The "<form>" tag should not be placed in another "<form>. "
Html1518	"Invalid nesting. The "<button>" mark should not be placed in another "<button>. "
Html1519	"Invalid nesting. The "<A>" mark should not be placed in another "<A>. "
Html1520	"Non-conforming start mark: the" <isindex> "element has been discarded and therefore should not be used. "
Html1521	"Invalid" </body> "or the end of the file. All elements with the start mark should end correctly before the end of the document. "
Html1522	"Invalid end mark:" </BR> ". Use "<br>" or "<br/>" instead ". "
Html1523	"Overlapping end tag. The marked structure should be "<B> <I> </B>", rather than "<B> <I> </B> </I> ". "
Html1524	"Invalid doctype. The shortest valid doctype is "<! Doctype HTML> ". "
Html1525	"Non-conforming HTML tags are found in external content (MathML/SVG. "
Html1526	"Invalid nesting. The "<nobr>" mark should not be placed in another "<nobr>. "
Html1527	"Should be doctype. The shortest valid doctype is "<! Doctype HTML> ". "
Html1528	"The HTML content contains" <image> "that does not meet the requirements ". Use "
Html1529	"Xmlns: The xlink property value is invalid. The value must be "http://www.w3.org/5o/xlink.pdf ". "
Html1530	"Text is found in structured table elements. The table text can only be placed in the <caption>, <TD>, or <TH> element. "
Html1531	"The xmlns attribute value is invalid. For an SVG element, the value must be "http://www.w3.org/2000/svg.pdf ". "
Html1532	"The xmlns attribute value is invalid. For a MathML element, the value must be "http://www.w3.org/1998/math/mathml.pdf ". "

 

CSS code

The format of these errors is css31.XxIt is also related to "Web open font format (woff)" and "embedded opentype font (EOT)" source and host server issues.

Code	Message	Description	Recommended Solution
Css3111	"@ Font-face unknown error"	Unknown issues are encountered in Cascading Style Sheet (CSS) fonts such as "Web open font format (woff)" and "embedded opentype font (EOT.	Check the source of the "woff" font. Try other fonts or sources to see if the problem persists.
Css3112	"@ Font-face does not pass the woff integrity check"	The Web open font format (woff) may be damaged, incomplete, or incorrect.	Check the font source. Check whether the correct font or source is correct.
Css3113	"@ Font-face does not match between the document source and the EOT root string"	This font cannot be used because the URL (rootstring) in "embedded opentype font (EOT)" does not match the domain of the document using this font.	The URL checksum in "EOT" rootstring may be incorrect, indicating that the font is damaged or that the font URL has changed. Make sure that the font is authorized or you have the appropriate permissions for the website that will use the font.
Css3114	"@ Font-face does not pass the OpenType embedded permission check. The permission must be installable. "	You are not authorized to install the font on the current webpage.	Obtain the correct permission or the authorization to embed the font.
Css3115	"@ Font-FACE: Invalid OpenType fonts cannot be loaded. "	This font is invalid for such use.	Obtain the permission or authorization for the current valid font.
Css3116	"@ Font-face cross-Source request failed. No access-control-allow-origin header. "	This font may not be configured as cross-origin access.	The font is not the same source as the document. Use the "access-control-allow-origin" HTTP header to ensure that the font can be used by hosts that process the font.
Css3117	"@ Font-face cross-Source request failed. Resource Access is restricted. "	The "access-control-allow-origin" header may be incorrectly configured or the font host may not allow your page to use this font.	Make sure that you have the correct permissions and correctly configure the HTTP Response Headers for hosts that process fonts that have cross-origin access sources.

 

Scalable Vector Graphics (SVG) Code

The F12 tool currently does not support extensive SVG debugging, but displays several console messages to help debug SVG code.

Code	Message	Description	Recommended Solution
Svg5601	"The format of SVG path data is incorrect and may not be completely parsed. "	SVGPathThe string format is incorrect or contains unrecognized commands.	Check the command format.
Svg5602	"The format of the SVG vertex list is incorrect and may not be completely parsed. "	List of vertices used for elements (for examplePolyline.	Make sure that these points are complete and the correct format is set for the user's coordinate system.

 

Script code

The F12 tool also reports JavaScript runtime errors. The format of these errors is script50.Xx(For example, script5001 ). These errors will be described on the Javascript error page.

XML Code

The F12 tool console can report XML code. The format of these errors is xml5.Xxx(For example, xml5603 ). For more information about XML, see xmllite reference.

Code	Message
Xml5001	"Applying integrated XSLT processing. "
Xml5601	"Mx_e_mx"
Xml5602	"The input ended unexpectedly. "
Xml5603	"The encoding cannot be identified. "
Xml5604	"The encoding cannot be switched. "
Xml5605	"The input encoding signature cannot be identified. "
Xml5606	"Wc_e_wc"
Xml5607	"Should be blank. "
Xml5608	"Should be a semicolon. "
Xml5609	"Must be"> ". "
Xml5610	"Must be a quote character. "
Xml5611	"Should be" = ". "
Xml5612	"The <character is not allowed in the attribute value. "
Xml5613	"Should be a hexadecimal number. "
Xml5614	"Should be a decimal number. "
Xml5615	"Should be" [". "
Xml5616	"Should be" (". "
Xml5617	The XML character is invalid. "
Xml5618	The name is invalid. "
Xml5619	"The Document Syntax is incorrect. "
Xml5620	"The CDATA syntax is incorrect. "
Xml5621	"The annotation syntax is incorrect. "
Xml5622	"The condition syntax is incorrect. "
Xml5623	"The ATTLIST declaration syntax is incorrect. "
Xml5624	"The doctype declaration syntax is incorrect. "
Xml5625	"The element declaration syntax is incorrect. "
Xml5626	"The entity statement syntax is incorrect. "
Xml5627	"The notation declaration syntax is incorrect. "
Xml5628	"Should be" ndata ". "
Xml5629	"Should be" public ". "
Xml5630	"Should be" system ". "
Xml5631	"The name is invalid. "
Xml5632	"Only one root element is allowed. "
Xml5633	"The end tag name does not match the corresponding start tag name. "
Xml5634	"An attribute with the same name already exists on this element. "
Xml5635	"XML Declaration can only be used at the beginning of a file. "
Xml5636	"Leading" XML ". "
Xml5637	"The text declaration syntax is incorrect. "
Xml5638	"The XML declaration syntax is incorrect. "
Xml5639	"The encoding name syntax is incorrect. "
Xml5640	"The syntax for public identifiers is incorrect. "
Xml5641	"Parameter entity reference is not allowed in the tag Declaration of the internal DTD subset. "
Xml5642	"The parameter object reference replacement text used between each tag declaration must contain a complete set of tag declarations. "
Xml5643	"The resolved entity cannot contain direct or indirect references to itself. "
Xml5644	"The specified object content format is incorrect. "
Xml5645	"The specified object has not been declared. "
Xml5646	"Object reference cannot contain the name of an unresolved object. "
Xml5647	"Attribute values cannot contain direct or indirect references to external entities. "
Xml5648	"The Processing Instruction syntax is incorrect. "
Xml5649	"The syntax of the system identifier is incorrect. "
Xml5650	"Should be a question mark (?). "
Xml5651	"Do not use the CDATA-section-close separator"]> "in the element content ". "
Xml5652	"Not all data blocks are read. "
Xml5653	"The DTD has been found but is forbidden. "
Xml5654	"The XML: space property value found is invalid. The valid values are "preserve" or "default ". "
Xml5655	"Nc_e_nc"
Xml5656	The specified name is invalid. "
Xml5657	"The specified name cannot contain multiple colons": ". "
Xml5658	"The colon": "is not allowed in the name. "
Xml5659	"The prefix has been declared. "
Xml5660	"The specified prefix has not been declared. "
Xml5661	"Non-default namespace declarations cannot contain empty Uris. "
Xml5662	The "XML" prefix is a reserved item and must have Uri "http://www.w3.org/xml/1998/namespace.pdf ". "
Xml5663	The prefix "" xmlns "is reserved for XML. "
Xml5664	"Only XML namespace URI (http://www.w3.org/XML/1998/namespace) can be assigned to the prefix" XML ". "
Xml5665	"Xmlns namespace URI (http://www.w3.org/2000/xmlns/) is retained and cannot be used. "
Xml5666	"SC _e_ SC"
Xml5667	"Exceeds the maximum depth of nested elements. "
Xml5668	"The maximum number of entity extensions is exceeded. "
Xml5669	"Wr_e_wr"
Xml5670	"Wr_e_nonwhitespace: writer: the specified string is not a space. "
Xml5671	"Wr_e_nsprefixdeclared: writer: The namespace prefix has been declared with another namespace. "
Xml5672	"Wr_e_nsprefixwithemptynsuri: writer: the prefix cannot be used with an empty namespace URI. "
Xml5673	"Wr_e_duplicateattribute: writer: duplicate attribute. "
Xml5674	"Wr_e_xmlnsprefixdeclaration: writer: The xmlns prefix cannot be redefined. "
Xml5675	"Wr_e_xmlprefixdeclaration: writer: the XML prefix must have a http://www.w3.org/XML/1998/namespace Uri. "
Xml5676	"Wr_e_xmlurideclaration: writer: XML namespace URI (http://www.w3.org/XML/1998/namespace) can only be assigned to the prefix" XML ". "
Xml5677	"Wr_e_xmlnsurideclaration: writer: xmlns namespace URI (http://www.w3.org/2000/xmlns/) retained, not available. "
Xml5678	"Wr_e_namespaceundeclared: writer: The namespace is not declared. "
Xml5679	"Wr_e_invalidxmlspace: writer: XML: space property value is invalid (allowed values are" default "and" preserve "). "
Xml5680	"Wr_e_invalidaction: writer: the XML document is invalid when the request is executed. "
Xml5681	"Wr_e_invalidsurrow.pair: writer: The entered agent pair is invalid or incomplete. "
Xml5682	"The character entity contains unexpected characters. It must be a decimal number. "
Xml5683	"The character entity contains unexpected characters. It must be a hexadecimal number. "
Xml5684	"The Unicode value of the specified character entity is invalid. "
Xml5685	"The encoding is invalid. "
Xml5686	"Unexpected XML error. "