greenfootglobal.com has Alexa Rank 30.023 and Google Page Rank is 2

greenfootglobal.com
  • Domain Name
    greenfootglobal.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #30023
  • Page Size
    19.5 KB
  • Ip Address
    207.36.224.122
  • Heading
    H1: 0, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 8 JPG, 0 PNG

Website Meta Analysis

  • Title
    Greenfoot Global ::
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    207.36.224.122
  • Domain Age
    3 Years, 9 Months, 29 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from greenfootglobal.com.

HTML Analysis

  • cache-control: private
  • content-length: 19737
  • content-type: text/html; Charset=utf-8
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • date: Wed, 06 Feb 2013 21:44:03 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Green Foot Global
375 N. Stephanie St Suite 1411
Henderson, Nevada 89014
United States

Domain Name: GREENFOOTGLOBAL.COM
Created: 29-Apr-09
Expires: 29-Apr-13
Updated: 17-Feb-11

Administrative Contact:
Foot, Green email
Green Foot Global
375 N. Stephanie St Suite 1411
Henderson, Nevada 89014
United States
+1.2625697599 Fax -

Technical Contact:
Foot, Green email
Green Foot Global
375 N. Stephanie St Suite 1411
Henderson, Nevada 89014
United States
+1.2625697599 Fax -

Name Servers:
NS1.NSVHOST.COM
NS2.NSVHOST.COM

DNS Analysis


DNS servers
ns1.nsvhost.com [64.34.51.251]
ns2.nsvhost.com [64.34.51.252]


DNS Records

Answer records
greenfootglobal.com MX
preference: 10
exchange: mailstore1.secureserver.net
86400s
greenfootglobal.com MX
preference: 15
exchange: smtp.secureserver.net
86400s
greenfootglobal.com NS  ns2.nsvhost.com 86400s
greenfootglobal.com NS  ns1.nsvhost.com 86400s
greenfootglobal.com TXT v=spf1 +all 86400s
greenfootglobal.com SOA
server: ns1.nsvhost.com
email: rick@internetnextstep.com
serial: 1349228946
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
greenfootglobal.com A 207.36.224.122 86400s

Authority records

Additional records
ns1.nsvhost.com A 64.34.51.251 86400s
ns2.nsvhost.com A 64.34.51.252 86400s

IP 207.36.224.122 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 207.36.224.122

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 166 Errors
  • 235 Warnings
Ratio Text/Html
  • 0.6626203852327448
Message Error
  • Error Line 6, Column 39: end tag for "meta" omitted, but OMITTAG NO was specified
      <meta name="description" content="">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 6, Column 3: start tag was here
      <meta name="description" content="">
  • Error Line 7, Column 36: end tag for "meta" omitted, but OMITTAG NO was specified
      <meta name="keywords" content="">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 7, Column 3: start tag was here
      <meta name="keywords" content="">
  • Error Line 8, Column 33: end tag for "meta" omitted, but OMITTAG NO was specified
      <meta name="title" content="">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 8, Column 3: start tag was here
      <meta name="title" content="">
  • Error Line 13, Column 67: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 13, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
  • Error Line 15, Column 88: end tag for "meta" omitted, but OMITTAG NO was specified
    …me="Copyright" content="Internet Next Step - http://www.InternetNextStep.com/">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 15, Column 1: start tag was here
    <meta name="Copyright" content="Internet Next Step - http://www.InternetNextSte…
  • Error Line 16, Column 86: end tag for "meta" omitted, but OMITTAG NO was specified
    …name="creator" content="Internet Next Step - http://www.InternetNextStep.com/">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 16, Column 1: start tag was here
    <meta name="creator" content="Internet Next Step - http://www.InternetNextStep.…
  • Error Line 17, Column 88: end tag for "meta" omitted, but OMITTAG NO was specified
    …me="publisher" content="Internet Next Step - http://www.InternetNextStep.com/">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 17, Column 1: start tag was here
    <meta name="publisher" content="Internet Next Step - http://www.InternetNextSte…
  • Error Line 18, Column 85: end tag for "meta" omitted, but OMITTAG NO was specified
    … name="author" content="Internet Next Step - http://www.InternetNextStep.com/">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 18, Column 1: start tag was here
    <meta name="author" content="Internet Next Step - http://www.InternetNextStep.c…
  • Error Line 22, Column 86: end tag for "link" omitted, but OMITTAG NO was specified
    …rel="stylesheet" href="/clientinc/styles/template4/styles.css" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 22, Column 1: start tag was here
    <link rel="stylesheet" href="/clientinc/styles/template4/styles.css" type="text…
  • Error Line 23, Column 89: end tag for "link" omitted, but OMITTAG NO was specified
    …="stylesheet" href="/common/jquery/jquery-ui-1.8.1.custom.css" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 23, Column 1: start tag was here
    <link rel="stylesheet" href="/common/jquery/jquery-ui-1.8.1.custom.css" type="t…
  • Error Line 24, Column 78: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" href="/common/jquery/css/confirm.css" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 24, Column 1: start tag was here
    <link rel="stylesheet" href="/common/jquery/css/confirm.css" type="text/css">
  • Error Line 25, Column 95: end tag for "link" omitted, but OMITTAG NO was specified
    …esheet" href="/common/jquery/css/jquery.validate.password.css" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 25, Column 1: start tag was here
    <link rel="stylesheet" href="/common/jquery/css/jquery.validate.password.css" t…
  • Error Line 29, Column 54: required attribute "type" not specified
    <script language="JavaScript" src="/common/script.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 30, Column 71: required attribute "type" not specified
    <script language="JavaScript" src="/common/jquery/jquery-1.6.1.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 31, Column 74: required attribute "type" not specified
    …ipt language="JavaScript" src="/common/jquery/jquery.validate.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 32, Column 77: required attribute "type" not specified
    … language="JavaScript" src="/common/jquery/jquery.validate.extend.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 33, Column 81: required attribute "type" not specified
    …guage="JavaScript" src="/common/jquery/jquery-ui-1.8.1.custom.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 34, Column 97: required attribute "type" not specified
    …t" src="/common/jquery/jquery.iframe-auto-height.plugin.1.5.0.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 35, Column 73: required attribute "type" not specified
    …ript language="JavaScript" src="/common/jquery/jquery.simplemodal.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 77: required attribute "type" not specified
    … language="JavaScript" src="/common/jquery/jquery.validate.custom.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 37, Column 79: required attribute "type" not specified
    …anguage="JavaScript" src="/common/jquery/jquery.validate.password.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 38, Column 80: required attribute "type" not specified
    …nguage="JavaScript" src="/common/jquery/jquery.scrollTo-1.4.2-min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 50, Column 13: there is no attribute "class"
    <BODY class="wholeBg" >

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 50, Column 23: element "BODY" undefined
    <BODY class="wholeBg" >

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 56, Column 76: required attribute "alt" not specified
    …<div id="logoNew"><img src="/clientinc/upload/newAssets/header-logo.gif"></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 56, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    …<div id="logoNew"><img src="/clientinc/upload/newAssets/header-logo.gif"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 56, Column 22: start tag was here
    			<div id="logoNew"><img src="/clientinc/upload/newAssets/header-logo.gif"></d…
  • Error Line 61, Column 16: required attribute "action" not specified
    										<form>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 62, Column 71: there is no attribute "onChange"
    …Oselector" id="bodyLOselector" onChange="javascript:location.href=this.value;">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 64, Column 65: cannot generate system identifier for general entity "UID"
    …"/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 64, Column 65: general entity "UID" not defined and no default entity
    …"/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 64, Column 68: reference not terminated by REFC delimiter
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 64, Column 68: reference to external entity in attribute value
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 64, Column 68: reference to entity "UID" for which no system identifier could be generated
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 64: entity was defined here
    …="/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-B…
  • Warning Line 64, Column 74: cannot generate system identifier for general entity "guid"
    …clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C146…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 64, Column 74: general entity "guid" not defined and no default entity
    …clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C146…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 64, Column 78: reference not terminated by REFC delimiter
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 64, Column 78: reference to external entity in attribute value
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 64, Column 78: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 64, Column 116: cannot generate system identifier for general entity "lo"
    …=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engli…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 64, Column 116: general entity "lo" not defined and no default entity
    …=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engli…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 64, Column 118: reference not terminated by REFC delimiter
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 64, Column 118: reference to external entity in attribute value
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 64, Column 118: reference to entity "lo" for which no system identifier could be generated
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 115: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engl…
  • Error Line 64, Column 130: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 66, Column 68: reference not terminated by REFC delimiter
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 66, Column 68: reference to external entity in attribute value
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 66, Column 68: reference to entity "UID" for which no system identifier could be generated
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 64: entity was defined here
    …="/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-B…
  • Warning Line 66, Column 78: reference not terminated by REFC delimiter
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 66, Column 78: reference to external entity in attribute value
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 66, Column 78: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 66, Column 118: reference not terminated by REFC delimiter
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=8">Spanish&nbsp;-&nbsp;Espa&ntilde;ol</…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 66, Column 118: reference to external entity in attribute value
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=8">Spanish&nbsp;-&nbsp;Espa&ntilde;ol</…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 66, Column 118: reference to entity "lo" for which no system identifier could be generated
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=8">Spanish&nbsp;-&nbsp;Espa&ntilde;ol</…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 115: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engl…
  • Warning Line 68, Column 68: reference not terminated by REFC delimiter
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 68, Column 68: reference to external entity in attribute value
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 68, Column 68: reference to entity "UID" for which no system identifier could be generated
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 64: entity was defined here
    …="/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-B…
  • Warning Line 68, Column 78: reference not terminated by REFC delimiter
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 68, Column 78: reference to external entity in attribute value
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 68, Column 78: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 68, Column 118: reference not terminated by REFC delimiter
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=107">Russian&nbsp;-&nbsp;Русский</optio…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 68, Column 118: reference to external entity in attribute value
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=107">Russian&nbsp;-&nbsp;Русский</optio…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 68, Column 118: reference to entity "lo" for which no system identifier could be generated
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=107">Russian&nbsp;-&nbsp;Русский</optio…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 115: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engl…
  • Error Line 76, Column 91: required attribute "alt" not specified
    …socialLogos"><img src="/clientinc/upload/newAssets/soc.jpg" usemap="#soclinks">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 76, Column 92: end tag for "img" omitted, but OMITTAG NO was specified
    …socialLogos"><img src="/clientinc/upload/newAssets/soc.jpg" usemap="#soclinks">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 76, Column 26: start tag was here
    			<div id="socialLogos"><img src="/clientinc/upload/newAssets/soc.jpg" usemap=…
  • Error Line 77, Column 24: required attribute "id" not specified
    			<map name="soclinks">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 78, Column 128: required attribute "alt" not specified
    …http://www.facebook.com/pages/-Greenfoot-Global-EnviroTabs-/160761363968979" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 79, Column 91: required attribute "alt" not specified
    …ape="rect" coords="67,0,82,40" href="http://www.twitter.com/greenfootGlobal" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 93, Column 14: required attribute "action" not specified
    								<form>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 94, Column 44: ID "bodyLOselector" already defined
    …				<select name="bodyLOselector" id="bodyLOselector" onChange="javascript:loc…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 62, Column 46: ID "bodyLOselector" first defined here
    …				<select name="bodyLOselector" id="bodyLOselector" onChange="javascript:loc…
  • Warning Line 96, Column 66: reference not terminated by REFC delimiter
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 96, Column 66: reference to external entity in attribute value
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 96, Column 66: reference to entity "UID" for which no system identifier could be generated
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 64: entity was defined here
    …="/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-B…
  • Warning Line 96, Column 76: reference not terminated by REFC delimiter
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 96, Column 76: reference to external entity in attribute value
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 96, Column 76: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 96, Column 116: reference not terminated by REFC delimiter
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 96, Column 116: reference to external entity in attribute value
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 96, Column 116: reference to entity "lo" for which no system identifier could be generated
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 115: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engl…
  • Error Line 96, Column 128: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;English</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 98, Column 66: reference not terminated by REFC delimiter
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 98, Column 66: reference to external entity in attribute value
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 98, Column 66: reference to entity "UID" for which no system identifier could be generated
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 64: entity was defined here
    …="/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-B…
  • Warning Line 98, Column 76: reference not terminated by REFC delimiter
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 98, Column 76: reference to external entity in attribute value
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 98, Column 76: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 98, Column 116: reference not terminated by REFC delimiter
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=8">Spanish&nbsp;-&nbsp;Espa&ntilde;ol</…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 98, Column 116: reference to external entity in attribute value
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=8">Spanish&nbsp;-&nbsp;Espa&ntilde;ol</…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 98, Column 116: reference to entity "lo" for which no system identifier could be generated
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=8">Spanish&nbsp;-&nbsp;Espa&ntilde;ol</…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 115: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engl…
  • Warning Line 100, Column 66: reference not terminated by REFC delimiter
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 100, Column 66: reference to external entity in attribute value
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 100, Column 66: reference to entity "UID" for which no system identifier could be generated
    …ommon/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 64: entity was defined here
    …="/common/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-B…
  • Warning Line 100, Column 76: reference not terminated by REFC delimiter
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 100, Column 76: reference to external entity in attribute value
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 100, Column 76: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 100, Column 116: reference not terminated by REFC delimiter
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=107">Russian&nbsp;-&nbsp;Русский</optio…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 100, Column 116: reference to external entity in attribute value
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=107">Russian&nbsp;-&nbsp;Русский</optio…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 100, Column 116: reference to entity "lo" for which no system identifier could be generated
    …81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=107">Russian&nbsp;-&nbsp;Русский</optio…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 115: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&lo=0" selected>English&nbsp;-&nbsp;Engl…
  • Error Line 112, Column 32: there is no attribute "valign"
          <ul class="menu2" valign="bottom">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 114, Column 76: cannot generate system identifier for general entity "SectionID"
    …ef="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 114, Column 76: general entity "SectionID" not defined and no default entity
    …ef="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 114, Column 85: reference not terminated by REFC delimiter
    …on/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 114, Column 85: reference to external entity in attribute value
    …on/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 114, Column 85: reference to entity "SectionID" for which no system identifier could be generated
    …on/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 114, Column 92: reference not terminated by REFC delimiter
    …ntCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 114, Column 92: reference to external entity in attribute value
    …ntCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 114, Column 92: reference to entity "guid" for which no system identifier could be generated
    …ntCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 116, Column 50: reference not terminated by REFC delimiter
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 116, Column 50: reference to external entity in attribute value
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 116, Column 50: reference to entity "guid" for which no system identifier could be generated
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 116, Column 88: cannot generate system identifier for general entity "SubSectionID"
    …=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="to…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 116, Column 88: general entity "SubSectionID" not defined and no default entity
    …=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="to…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 116, Column 100: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><spa…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 116, Column 100: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><spa…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 116, Column 100: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><spa…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 116, Column 104: cannot generate system identifier for general entity "treeUID"
    …EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span cl…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 116, Column 104: general entity "treeUID" not defined and no default entity
    …EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span cl…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 116, Column 111: reference not terminated by REFC delimiter
    …B-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span class="do…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 116, Column 111: reference to external entity in attribute value
    …B-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span class="do…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 116, Column 111: reference to entity "treeUID" for which no system identifier could be generated
    …B-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span class="do…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 120, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51422&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 120, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51422&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 120, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51422&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 120, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51422&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 120, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=51422&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 120, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51422&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 120, Column 124: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Mission</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 120, Column 124: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Mission</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 120, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Mission</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 120, Column 134: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Mission</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 120, Column 134: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Mission</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 120, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Mission</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 122, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51432&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 122, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51432&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 122, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51432&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 122, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51432&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 122, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=51432&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 122, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51432&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 122, Column 124: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our History</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 122, Column 124: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our History</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 122, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our History</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 122, Column 134: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our History</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 122, Column 134: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our History</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 122, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our History</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 124, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51442&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 124, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51442&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 124, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51442&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 124, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51442&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 124, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=51442&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 124, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51442&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 124, Column 124: reference not terminated by REFC delimiter
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Team</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 124, Column 124: reference to external entity in attribute value
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Team</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 124, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Team</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 124, Column 134: reference not terminated by REFC delimiter
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Team</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 124, Column 134: reference to external entity in attribute value
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Team</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 124, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Our Team</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 126, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51412&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 126, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51412&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 126, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51412&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 126, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51412&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 126, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=51412&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 126, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51412&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 126, Column 124: reference not terminated by REFC delimiter
    …5-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Newsletter</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 126, Column 124: reference to external entity in attribute value
    …5-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Newsletter</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 126, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …5-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Newsletter</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 126, Column 134: reference not terminated by REFC delimiter
    …5-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Newsletter</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 126, Column 134: reference to external entity in attribute value
    …5-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Newsletter</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 126, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …5-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51132">Newsletter</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 133, Column 50: reference not terminated by REFC delimiter
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 133, Column 50: reference to external entity in attribute value
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 133, Column 50: reference to entity "guid" for which no system identifier could be generated
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 133, Column 100: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=34&treeUID=51122" class="top_link"><spa…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 133, Column 100: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=34&treeUID=51122" class="top_link"><spa…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 133, Column 100: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=34&treeUID=51122" class="top_link"><spa…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 133, Column 111: reference not terminated by REFC delimiter
    …B-BA7BD52C1466&SubSectionID=34&treeUID=51122" class="top_link"><span class="do…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 133, Column 111: reference to external entity in attribute value
    …B-BA7BD52C1466&SubSectionID=34&treeUID=51122" class="top_link"><span class="do…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 133, Column 111: reference to entity "treeUID" for which no system identifier could be generated
    …B-BA7BD52C1466&SubSectionID=34&treeUID=51122" class="top_link"><span class="do…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 137, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50952&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 137, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50952&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 137, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50952&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 137, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50952&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 137, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50952&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 137, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50952&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 137, Column 124: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">How Does It Work?</a><…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 137, Column 124: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">How Does It Work?</a><…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 137, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">How Does It Work?</a><…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 137, Column 134: reference not terminated by REFC delimiter
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">How Does It Work?</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 137, Column 134: reference to external entity in attribute value
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">How Does It Work?</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 137, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">How Does It Work?</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 139, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50962&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 139, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50962&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 139, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50962&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 139, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50962&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 139, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50962&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 139, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50962&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 139, Column 124: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Is It Safe?</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 139, Column 124: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Is It Safe?</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 139, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Is It Safe?</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 139, Column 134: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Is It Safe?</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 139, Column 134: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Is It Safe?</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 139, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Is It Safe?</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 141, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50972&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 141, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50972&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 141, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50972&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 141, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50972&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 141, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50972&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 141, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50972&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 141, Column 124: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Why use EnviroTabs?</a…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 141, Column 124: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Why use EnviroTabs?</a…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 141, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Why use EnviroTabs?</a…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 141, Column 134: reference not terminated by REFC delimiter
    …FA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Why use EnviroTabs?</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 141, Column 134: reference to external entity in attribute value
    …FA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Why use EnviroTabs?</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 141, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …FA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Why use EnviroTabs?</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 143, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51472&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 143, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51472&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 143, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51472&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 143, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51472&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 143, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=51472&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 143, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51472&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 143, Column 124: reference not terminated by REFC delimiter
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Benefits</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 143, Column 124: reference to external entity in attribute value
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Benefits</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 143, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Benefits</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 143, Column 134: reference not terminated by REFC delimiter
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Benefits</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 143, Column 134: reference to external entity in attribute value
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Benefits</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 143, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Benefits</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 145, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50982&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 145, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50982&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 145, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50982&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 145, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50982&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 145, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50982&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 145, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50982&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 145, Column 124: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">100% Guarantee</a></li…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 145, Column 124: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">100% Guarantee</a></li…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 145, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">100% Guarantee</a></li…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 145, Column 134: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">100% Guarantee</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 145, Column 134: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">100% Guarantee</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 145, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">100% Guarantee</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 147, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50992&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 147, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50992&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 147, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50992&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 147, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50992&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 147, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50992&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 147, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50992&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 147, Column 124: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Commercial Use</a></li…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 147, Column 124: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Commercial Use</a></li…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 147, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Commercial Use</a></li…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 147, Column 134: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Commercial Use</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 147, Column 134: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Commercial Use</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 147, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Commercial Use</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 149, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50602&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 149, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50602&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 149, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50602&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 149, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50602&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 149, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50602&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 149, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50602&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 149, Column 124: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Testing Results</a></l…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 149, Column 124: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Testing Results</a></l…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 149, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Testing Results</a></l…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 149, Column 134: reference not terminated by REFC delimiter
    …8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Testing Results</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 149, Column 134: reference to external entity in attribute value
    …8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Testing Results</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 149, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51122">Testing Results</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 156, Column 85: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50552&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 156, Column 85: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50552&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 156, Column 85: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50552&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 156, Column 92: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50552&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 156, Column 92: reference to external entity in attribute value
    …tCustom.asp?UID=50552&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 156, Column 92: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50552&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 158, Column 50: reference not terminated by REFC delimiter
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 158, Column 50: reference to external entity in attribute value
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 158, Column 50: reference to entity "guid" for which no system identifier could be generated
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 158, Column 100: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=35&treeUID=51112" class="top_link"><spa…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 158, Column 100: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=35&treeUID=51112" class="top_link"><spa…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 158, Column 100: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=35&treeUID=51112" class="top_link"><spa…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 158, Column 111: reference not terminated by REFC delimiter
    …B-BA7BD52C1466&SubSectionID=35&treeUID=51112" class="top_link"><span class="do…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 158, Column 111: reference to external entity in attribute value
    …B-BA7BD52C1466&SubSectionID=35&treeUID=51112" class="top_link"><span class="do…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 158, Column 111: reference to entity "treeUID" for which no system identifier could be generated
    …B-BA7BD52C1466&SubSectionID=35&treeUID=51112" class="top_link"><span class="do…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 162, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 162, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 162, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 162, Column 80: reference not terminated by REFC delimiter
    …m.asp?UID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 162, Column 80: reference to external entity in attribute value
    …m.asp?UID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 162, Column 80: reference to entity "SectionID" for which no system identifier could be generated
    …m.asp?UID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 162, Column 87: reference not terminated by REFC delimiter
    …ID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 162, Column 87: reference to external entity in attribute value
    …ID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 162, Column 87: reference to entity "guid" for which no system identifier could be generated
    …ID=50572&SectionID=35&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 162, Column 137: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Building your GFG Busi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 162, Column 137: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Building your GFG Busi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 162, Column 137: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Building your GFG Busi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 162, Column 147: reference not terminated by REFC delimiter
    …FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Building your GFG Business</a></…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 162, Column 147: reference to external entity in attribute value
    …FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Building your GFG Business</a></…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 162, Column 147: reference to entity "treeUID" for which no system identifier could be generated
    …FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Building your GFG Business</a></…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 164, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50632&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 164, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50632&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 164, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50632&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 164, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50632&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 164, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=50632&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 164, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50632&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 164, Column 124: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Comp Plan At A Glance<…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 164, Column 124: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Comp Plan At A Glance<…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 164, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Comp Plan At A Glance<…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 164, Column 134: reference not terminated by REFC delimiter
    …-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Comp Plan At A Glance</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 164, Column 134: reference to external entity in attribute value
    …-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Comp Plan At A Glance</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 164, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51112">Comp Plan At A Glance</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 166, Column 88: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50642&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 166, Column 88: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50642&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 166, Column 88: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50642&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 166, Column 95: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50642&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 166, Column 95: reference to external entity in attribute value
    …tCustom.asp?UID=50642&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 166, Column 95: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50642&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 166, Column 145: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=5&treeUID=51112" class="fly">Compensati…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 166, Column 145: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=5&treeUID=51112" class="fly">Compensati…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 166, Column 145: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=5&treeUID=51112" class="fly">Compensati…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 166, Column 155: reference not terminated by REFC delimiter
    …FB-BA7BD52C1466&SubSectionID=5&treeUID=51112" class="fly">Compensation Plan<!-…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 166, Column 155: reference to external entity in attribute value
    …FB-BA7BD52C1466&SubSectionID=5&treeUID=51112" class="fly">Compensation Plan<!-…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 166, Column 155: reference to entity "treeUID" for which no system identifier could be generated
    …FB-BA7BD52C1466&SubSectionID=5&treeUID=51112" class="fly">Compensation Plan<!-…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Error Line 170, Column 39: end tag for "ul" which is not finished
                                      </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 180, Column 88: reference not terminated by REFC delimiter
    …/sc_cart/sc_CatTy.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 180, Column 88: reference to external entity in attribute value
    …/sc_cart/sc_CatTy.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 180, Column 88: reference to entity "guid" for which no system identifier could be generated
    …/sc_cart/sc_CatTy.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 182, Column 50: reference not terminated by REFC delimiter
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 182, Column 50: reference to external entity in attribute value
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 182, Column 50: reference to entity "guid" for which no system identifier could be generated
    …lass="top"><a href="#?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 182, Column 100: reference not terminated by REFC delimiter
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=36&treeUID=51102" class="top_link"><spa…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 182, Column 100: reference to external entity in attribute value
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=36&treeUID=51102" class="top_link"><spa…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 182, Column 100: reference to entity "SubSectionID" for which no system identifier could be generated
    …C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=36&treeUID=51102" class="top_link"><spa…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 182, Column 111: reference not terminated by REFC delimiter
    …B-BA7BD52C1466&SubSectionID=36&treeUID=51102" class="top_link"><span class="do…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 182, Column 111: reference to external entity in attribute value
    …B-BA7BD52C1466&SubSectionID=36&treeUID=51102" class="top_link"><span class="do…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 182, Column 111: reference to entity "treeUID" for which no system identifier could be generated
    …B-BA7BD52C1466&SubSectionID=36&treeUID=51102" class="top_link"><span class="do…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 186, Column 67: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51022&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 186, Column 67: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51022&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 186, Column 67: reference to entity "SectionID" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51022&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 114, Column 75: entity was defined here
    …ref="/common/clientCustom.asp?UID=1000&SectionID=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 186, Column 74: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51022&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 186, Column 74: reference to external entity in attribute value
    …tCustom.asp?UID=51022&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 186, Column 74: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51022&SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 186, Column 124: reference not terminated by REFC delimiter
    …3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Company</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 186, Column 124: reference to external entity in attribute value
    …3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Company</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 186, Column 124: reference to entity "SubSectionID" for which no system identifier could be generated
    …3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Company</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 186, Column 134: reference not terminated by REFC delimiter
    …3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Company</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 186, Column 134: reference to external entity in attribute value
    …3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Company</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 186, Column 134: reference to entity "treeUID" for which no system identifier could be generated
    …3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Company</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 188, Column 56: reference not terminated by REFC delimiter
    …ref="/txt/aboutme.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 188, Column 56: reference to external entity in attribute value
    …ref="/txt/aboutme.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 188, Column 56: reference to entity "guid" for which no system identifier could be generated
    …ref="/txt/aboutme.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&Su…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 188, Column 106: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Distributor</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 188, Column 106: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Distributor</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 188, Column 106: reference to entity "SubSectionID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Distributor</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 87: entity was defined here
    …d=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="t…
  • Warning Line 188, Column 116: reference not terminated by REFC delimiter
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Distributor</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 188, Column 116: reference to external entity in attribute value
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Distributor</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 188, Column 116: reference to entity "treeUID" for which no system identifier could be generated
    …-F4C8-4EFA-B6FB-BA7BD52C1466&SubSectionID=0&treeUID=51102">Distributor</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 116, Column 103: entity was defined here
    …4EFA-B6FB-BA7BD52C1466&SubSectionID=39&treeUID=51132" class="top_link"><span c…
  • Warning Line 195, Column 76: reference not terminated by REFC delimiter
    …f="/signup/signup.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 195, Column 76: reference to external entity in attribute value
    …f="/signup/signup.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 195, Column 76: reference to entity "guid" for which no system identifier could be generated
    …f="/signup/signup.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 197, Column 78: reference not terminated by REFC delimiter
    …"/members/default.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 197, Column 78: reference to external entity in attribute value
    …"/members/default.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 197, Column 78: reference to entity "guid" for which no system identifier could be generated
    …"/members/default.asp?SectionID=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466" c…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Error Line 241, Column 23: document type does not allow element "style" here
    <style type="text/css">@import url(/clientinc/template0/styles.css);</style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 242, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 405, Column 18: end tag for "br" omitted, but OMITTAG NO was specified
    	<br clear="all">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 405, Column 2: start tag was here
    	<br clear="all">
  • Warning Line 413, Column 48: reference not terminated by REFC delimiter
    … href="/faq/query.asp?sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 413, Column 48: reference to external entity in attribute value
    … href="/faq/query.asp?sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 413, Column 48: reference to entity "guid" for which no system identifier could be generated
    … href="/faq/query.asp?sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 414, Column 52: cannot generate system identifier for general entity "sectionid"
    …f="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 414, Column 52: general entity "sectionid" not defined and no default entity
    …f="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 414, Column 61: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 414, Column 61: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 414, Column 61: reference to entity "sectionid" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 414, Column 51: entity was defined here
    …ef="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 414, Column 68: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">P…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 414, Column 68: reference to external entity in attribute value
    …tCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">P…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 414, Column 68: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">P…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 415, Column 61: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50792&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 415, Column 61: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50792&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 415, Column 61: reference to entity "sectionid" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50792&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 414, Column 51: entity was defined here
    …ef="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 415, Column 68: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50792&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">R…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 415, Column 68: reference to external entity in attribute value
    …tCustom.asp?UID=50792&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">R…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 415, Column 68: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50792&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">R…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 416, Column 61: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50802&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 416, Column 61: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50802&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 416, Column 61: reference to entity "sectionid" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50802&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 414, Column 51: entity was defined here
    …ef="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 416, Column 68: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50802&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">D…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 416, Column 68: reference to external entity in attribute value
    …tCustom.asp?UID=50802&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">D…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 416, Column 68: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50802&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">D…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 417, Column 61: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50702&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 417, Column 61: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50702&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 417, Column 61: reference to entity "sectionid" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50702&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 414, Column 51: entity was defined here
    …ef="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 417, Column 68: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50702&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">T…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 417, Column 68: reference to external entity in attribute value
    …tCustom.asp?UID=50702&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">T…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 417, Column 68: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50702&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">T…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 418, Column 61: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=50712&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 418, Column 61: reference to external entity in attribute value
    …n/clientCustom.asp?UID=50712&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 418, Column 61: reference to entity "sectionid" for which no system identifier could be generated
    …n/clientCustom.asp?UID=50712&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 414, Column 51: entity was defined here
    …ef="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 418, Column 68: reference not terminated by REFC delimiter
    …tCustom.asp?UID=50712&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">E…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 418, Column 68: reference to external entity in attribute value
    …tCustom.asp?UID=50712&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">E…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 418, Column 68: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=50712&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">E…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Warning Line 419, Column 61: reference not terminated by REFC delimiter
    …n/clientCustom.asp?UID=51262&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 419, Column 61: reference to external entity in attribute value
    …n/clientCustom.asp?UID=51262&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 419, Column 61: reference to entity "sectionid" for which no system identifier could be generated
    …n/clientCustom.asp?UID=51262&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 414, Column 51: entity was defined here
    …ef="/common/clientCustom.asp?UID=50692&sectionid=1&guid=C81D3605-F4C8-4EFA-B6F…
  • Warning Line 419, Column 68: reference not terminated by REFC delimiter
    …tCustom.asp?UID=51262&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">M…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 419, Column 68: reference to external entity in attribute value
    …tCustom.asp?UID=51262&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">M…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 419, Column 68: reference to entity "guid" for which no system identifier could be generated
    …tCustom.asp?UID=51262&sectionid=1&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C1466">M…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 64, Column 73: entity was defined here
    …/clientCustom.asp?SectionID=1&UID=1000&guid=C81D3605-F4C8-4EFA-B6FB-BA7BD52C14…
  • Error Line 434, Column 7: end tag for element "HTML" which is not open
    </HTML>	  

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 434, Column 11: "html" not finished but document ended
    </HTML>	  
  • Error Line 434, Column 11: end tag for "html" omitted, but OMITTAG NO was specified
    </HTML>	  

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 5.600 visits
Daily Visitor