: ساعت 1392/06/18 : امروز        *     دريافت حکم ترميم سال 1392   دریافت حکم حقوقی     دریافت فیش حقوقی     بازنشستگان خارج ازکشور   BbqJiiKBF3OEpvcQ5MZxRg== 18/06/1392 ...

cspf.ir
  • Domain Name
    cspf.ir
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #55049
  • Page Size
    118.6 KB
  • Ip Address
    95.38.61.15
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    105 GIF, 0 JPG, 14 PNG

Website Meta Analysis

  • Title
    به سايت صندوق بازنشستگی کشوری خوش آمديد
  • Meta Keyword
  • Meta Description
    : ساعت 1392/06/18 : امروز        *     دريافت حکم ترميم سال 1392   دریافت حکم حقوقی     دریافت فیش حقوقی     بازنشستگان خارج ازکشور   BbqJiiKBF3OEpvcQ5MZxRg== 18/06/1392  :  مرگ ناباورانه خبرنگار جوان حوزه رفاه ایرنا «حنانه زاکانی» از خبرنگاران ...

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    95.38.61.15
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from cspf.ir.

HTML Analysis

  • date: Mon, 09 Sep 2013 14:10:22 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 2.0.50727
  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-length: 127789
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for cspf.ir

DNS Analysis


DNS servers
ns1.fanavaidc.com [95.38.120.241]
ns2.fanavaidc.com [95.38.120.242]


DNS Records

Answer records
cspf.ir A 95.38.61.15 3600s
cspf.ir NS  alborz.fanavaidc.com 3600s
cspf.ir SOA
server: alborz.fanavaidc.com
email: hostmaster@fanavaidc.com
serial: 14
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
cspf.ir MX
preference: 10
exchange: amg.dpi.ir
3600s

Authority records

Additional records
alborz.fanavaidc.com A 95.38.120.206 3600s
alborz.fanavaidc.com A 95.38.120.241 3600s
alborz.fanavaidc.com A 95.38.120.200 3600s
alborz.fanavaidc.com A 192.168.11.51 3600s
alborz.fanavaidc.com A 95.38.120.205 3600s
alborz.fanavaidc.com A 95.38.120.204 3600s
alborz.fanavaidc.com A 95.38.120.207 3600s

IP 95.38.61.15 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 112 Errors
  • 66 Warnings
Ratio Text/Html
  • 0.6235043192542389
Message Error
  • Error Line 8, Column 47: required attribute "type" not specified
        <script src="~/JQuery/jquery-1.7.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>.

  • Warning Line 17, Column 36: character "&" is the first character of a delimiter but occurred as data
                    if(($mozChar >= 48 && $mozChar <= 57) || $mozChar == 0 || $char…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 17, Column 37: character "&" is the first character of a delimiter but occurred as data
                    if(($mozChar >= 48 && $mozChar <= 57) || $mozChar == 0 || $char…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 17, Column 48: character "<" is the first character of a delimiter but occurred as data
    …       if(($mozChar >= 48 && $mozChar <= 57) || $mozChar == 0 || $char == 8 ||…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 26, Column 37: character "&" is the first character of a delimiter but occurred as data
                        if(($char >= 48 && $char <= 57) || $char == 13) $RetVal = t…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 26, Column 38: character "&" is the first character of a delimiter but occurred as data
                        if(($char >= 48 && $char <= 57) || $char == 13) $RetVal = t…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 26, Column 46: character "<" is the first character of a delimiter but occurred as data
    …                if(($char >= 48 && $char <= 57) || $char == 13) $RetVal = true;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 44, Column 47: character "<" is the first character of a delimiter but occurred as data
                // add a zero in front of numbers < 10

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 52, Column 18: character "<" is the first character of a delimiter but occurred as data
                if (i<10)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 74, Column 98: character "&" is the first character of a delimiter but occurred as data
    …rCase().indexOf('opera');if(operbr==-1&&navigator.product&&navigator.product==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 74, Column 100: cannot generate system identifier for general entity "navigator.product"
    …ase().indexOf('opera');if(operbr==-1&&navigator.product&&navigator.product=="G…

    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 74, Column 100: general entity "navigator.product" not defined and no default entity
    …ase().indexOf('opera');if(operbr==-1&&navigator.product&&navigator.product=="G…

    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 74, Column 117: reference not terminated by REFC delimiter
    …era');if(operbr==-1&&navigator.product&&navigator.product=="Gecko"){var agt = …

    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.

  • Error Line 74, Column 117: reference to entity "navigator.product" for which no system identifier could be generated
    …era');if(operbr==-1&&navigator.product&&navigator.product=="Gecko"){var agt = …

    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 74, Column 99: entity was defined here
    …Case().indexOf('opera');if(operbr==-1&&navigator.product&&navigator.product=="…
  • Warning Line 74, Column 117: character "&" is the first character of a delimiter but occurred as data
    …era');if(operbr==-1&&navigator.product&&navigator.product=="Gecko"){var agt = …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 74, Column 136: reference not terminated by REFC delimiter
    …&&navigator.product&&navigator.product=="Gecko"){var agt = navigator.userAgent…

    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.

  • Error Line 74, Column 136: reference to entity "navigator.product" for which no system identifier could be generated
    …&&navigator.product&&navigator.product=="Gecko"){var agt = navigator.userAgent…

    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 74, Column 99: entity was defined here
    …Case().indexOf('opera');if(operbr==-1&&navigator.product&&navigator.product=="…
  • Error Line 77, Column 325: element "nobr" undefined
    …ft=wwidth+"px";iedivw.innerHTML='<nobr>'+wwholemessage+'</nobr>';sizeupw=iediv…

    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 77, Column 686: element "nobr" undefined
    …wwidth;ns4layerw.document.write('<nobr>'+wwholemessage+'</nobr>');ns4layerw.do…

    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 77, Column 1052: element "nobr" undefined
    …t=wwidth+"px";ns6divw.innerHTML='<nobr>'+wwholemessage+'</nobr>';sizeupw=ns6di…

    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 77, Column 1177: element "nobr" undefined
    …ntById('operaslider').innerHTML='<nobr>'+wwholemessage+'</nobr>';sizeupw=docum…

    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 187, Column 86: required attribute "type" not specified
    …         <script language="JavaScript">document.write('<table align="center" b…

    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 187, Column 135: document type does not allow element "table" here
    …rite('<table align="center" border="0"><tr><td width='+wwidth+'px><font color=…

    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 187, Column 162: "px" is not a member of a group specified for any attribute
    … border="0"><tr><td width='+wwidth+'px><font color="#000080">');if(document.ge…
  • Error Line 187, Column 424: there is no attribute "onMouseover"
    …th+'px '+wheight+'px 0);" onMouseover="sspeed=0;" onMouseout="sspeed=restart">…

    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 187, Column 447: there is no attribute "onMouseout"
    …;" onMouseover="sspeed=0;" onMouseout="sspeed=restart">');if(operbr!=-1)docume…

    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 187, Column 463: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …sspeed=0;" onMouseout="sspeed=restart">');if(operbr!=-1)document.write('<div i…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 187, Column 685: end tag for "font" omitted, but OMITTAG NO was specified
    …style="position:absolute;height:'+wheight+'px;"></div></div></span>')}</script>

    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 187, Column 163: start tag was here
    …border="0"><tr><td width='+wwidth+'px><font color="#000080">');if(document.get…
  • Error Line 187, Column 685: end tag for "td" omitted, but OMITTAG NO was specified
    …style="position:absolute;height:'+wheight+'px;"></div></div></span>')}</script>

    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 187, Column 140: start tag was here
    …'<table align="center" border="0"><tr><td width='+wwidth+'px><font color="#000…
  • Error Line 187, Column 685: end tag for "tr" omitted, but OMITTAG NO was specified
    …style="position:absolute;height:'+wheight+'px;"></div></div></span>')}</script>

    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 187, Column 136: start tag was here
    …ite('<table align="center" border="0"><tr><td width='+wwidth+'px><font color="…
  • Error Line 187, Column 685: end tag for "table" omitted, but OMITTAG NO was specified
    …style="position:absolute;height:'+wheight+'px;"></div></div></span>')}</script>

    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 187, Column 103: start tag was here
    …language="JavaScript">document.write('<table align="center" border="0"><tr><td…
  • Error Line 189, Column 71: there is no attribute "width"
    …                        <ilayer width="&{wwidth};" height="&{wheight};" name="…

    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 189, Column 72: character "&" is the first character of a delimiter but occurred as data
    …                       <ilayer width="&{wwidth};" height="&{wheight};" name="w…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 189, Column 91: there is no attribute "height"
    …    <ilayer width="&{wwidth};" height="&{wheight};" name="wslider1" bgcolor="&…

    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 189, Column 92: character "&" is the first character of a delimiter but occurred as data
    …   <ilayer width="&{wwidth};" height="&{wheight};" name="wslider1" bgcolor="&{…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 189, Column 110: there is no attribute "name"
    … width="&{wwidth};" height="&{wheight};" name="wslider1" bgcolor="&{wbcolor};">

    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 189, Column 129: there is no attribute "bgcolor"
    … width="&{wwidth};" height="&{wheight};" name="wslider1" bgcolor="&{wbcolor};">

    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 189, Column 130: character "&" is the first character of a delimiter but occurred as data
    … width="&{wwidth};" height="&{wheight};" name="wslider1" bgcolor="&{wbcolor};">

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 189, Column 142: element "ilayer" undefined
    … width="&{wwidth};" height="&{wheight};" name="wslider1" bgcolor="&{wbcolor};">

    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 190, Column 69: there is no attribute "name"
    …                          <layer name="wslider2" width=&{wwidth}; height=&{whe…

    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 190, Column 86: there is no attribute "width"
    …         <layer name="wslider2" width=&{wwidth}; height=&{wheight}; onMouseove…

    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 190, Column 86: an attribute value must be a literal unless it contains only name characters
    …         <layer name="wslider2" width=&{wwidth}; height=&{wheight}; onMouseove…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 190, Column 104: there is no attribute "height"
    …me="wslider2" width=&{wwidth}; height=&{wheight}; onMouseover="sspeed=0;" onMo…

    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 190, Column 104: an attribute value must be a literal unless it contains only name characters
    …me="wslider2" width=&{wwidth}; height=&{wheight}; onMouseover="sspeed=0;" onMo…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 190, Column 128: there is no attribute "onMouseover"
    …idth}; height=&{wheight}; onMouseover="sspeed=0;" onMouseout="sspeed=restart">…

    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 190, Column 151: there is no attribute "onMouseout"
    …wheight}; onMouseover="sspeed=0;" onMouseout="sspeed=restart"></layer></ilayer>

    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 190, Column 167: element "layer" undefined
    …wheight}; onMouseover="sspeed=0;" onMouseout="sspeed=restart"></layer></ilayer>

    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 191, Column 63: end tag for element "font" which is not open
                                                            </font>

    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 276, Column 116: end tag for "a" omitted, but OMITTAG NO was specified
    …       <img alt="" src="Images/JahadPensioner.gif" style="border: 0px" /></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 275, Column 41: start tag was here
    <a href="JahadPensioner/Default.aspx" id…
  • Error Line 277, Column 40: end tag for element "a" which is not open
                                        </a></td>

    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 302, Column 256: required attribute "alt" not specified
    …"ورود مديريتها و دستگاههای اجرايی" src="Images/Loginicon.gif" border="0" /></a>

    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 303, Column 73: end tag for "div" omitted, but OMITTAG NO was specified
                                                                        </td>

    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 301, Column 73: start tag was here
    <div align="center">
  • Warning Line 474, Column 109: cannot generate system identifier for general entity "Serv"
    … href="http://www.dolat.ir/NSite/Information/?Info=11&Serv=81" target="_blank">

    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 474, Column 109: general entity "Serv" not defined and no default entity
    … href="http://www.dolat.ir/NSite/Information/?Info=11&Serv=81" target="_blank">

    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 474, Column 113: reference not terminated by REFC delimiter
    … href="http://www.dolat.ir/NSite/Information/?Info=11&Serv=81" target="_blank">

    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 474, Column 113: reference to external entity in attribute value
    … href="http://www.dolat.ir/NSite/Information/?Info=11&Serv=81" target="_blank">

    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 474, Column 113: reference to entity "Serv" for which no system identifier could be generated
    … href="http://www.dolat.ir/NSite/Information/?Info=11&Serv=81" target="_blank">

    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 474, Column 108: entity was defined here
    … href="http://www.dolat.ir/NSite/Information/?Info=11&Serv=81" target="_blank">
  • Error Line 490, Column 96: there is no attribute "bordercolor"
    …  padding-right: 1px; padding-top: 0; padding-bottom: 0" bordercolor="#D1E0D3">

    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 522, Column 74: value of attribute "align" cannot be "Justify"; must be one of "left", "center", "right"
    …ing="0" cellpadding="4" align="Justify" bordercolor="#B3CFB8" border="0" id="c…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 525, Column 103: cannot generate system identifier for general entity "bvcud53gd"
    …hx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje8…

    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 525, Column 103: general entity "bvcud53gd" not defined and no default entity
    …hx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje8…

    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 525, Column 112: reference not terminated by REFC delimiter
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 112: reference to external entity in attribute value
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 112: reference to entity "bvcud53gd" for which no system identifier could be generated
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 102: entity was defined here
    …shx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje…
  • Warning Line 525, Column 171: cannot generate system identifier for general entity "ghbvf97fd"
    …73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=…

    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 525, Column 171: general entity "ghbvf97fd" not defined and no default entity
    …73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=…

    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 525, Column 180: reference not terminated by REFC delimiter
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmk…

    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 525, Column 180: reference to external entity in attribute value
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmk…

    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 525, Column 180: reference to entity "ghbvf97fd" for which no system identifier could be generated
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmk…

    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 525, Column 170: entity was defined here
    …y73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd…
  • Warning Line 525, Column 206: cannot generate system identifier for general entity "hcbd"
    …sS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="c…

    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 525, Column 206: general entity "hcbd" not defined and no default entity
    …sS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="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.

  • Warning Line 525, Column 210: reference not terminated by REFC delimiter
    …hbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 210: reference to external entity in attribute value
    …hbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 210: reference to entity "hcbd" for which no system identifier could be generated
    …hbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 205: entity was defined here
    …psS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="…
  • Error Line 529, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <div align="right" style="text-align: justify">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 539, Column 112: reference not terminated by REFC delimiter
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 539, Column 112: reference to external entity in attribute value
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 539, Column 112: reference to entity "bvcud53gd" for which no system identifier could be generated
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 102: entity was defined here
    …shx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje…
  • Warning Line 539, Column 180: reference not terminated by REFC delimiter
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=tl7l/aY45GCvAVp5rWP55Q==&hcbd=Jr843ndmk…

    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 539, Column 180: reference to external entity in attribute value
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=tl7l/aY45GCvAVp5rWP55Q==&hcbd=Jr843ndmk…

    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 539, Column 180: reference to entity "ghbvf97fd" for which no system identifier could be generated
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=tl7l/aY45GCvAVp5rWP55Q==&hcbd=Jr843ndmk…

    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 525, Column 170: entity was defined here
    …y73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd…
  • Warning Line 539, Column 210: reference not terminated by REFC delimiter
    …hbvf97fd=tl7l/aY45GCvAVp5rWP55Q==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 539, Column 210: reference to external entity in attribute value
    …hbvf97fd=tl7l/aY45GCvAVp5rWP55Q==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 539, Column 210: reference to entity "hcbd" for which no system identifier could be generated
    …hbvf97fd=tl7l/aY45GCvAVp5rWP55Q==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 205: entity was defined here
    …psS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="…
  • Error Line 543, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <div align="right" style="text-align: justify">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 553, Column 112: reference not terminated by REFC delimiter
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 553, Column 112: reference to external entity in attribute value
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 553, Column 112: reference to entity "bvcud53gd" for which no system identifier could be generated
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 102: entity was defined here
    …shx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje…
  • Warning Line 553, Column 180: reference not terminated by REFC delimiter
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=osRAeNCEOwqlCKJdYrMNpw==&hcbd=Jr843ndmk…

    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 553, Column 180: reference to external entity in attribute value
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=osRAeNCEOwqlCKJdYrMNpw==&hcbd=Jr843ndmk…

    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 553, Column 180: reference to entity "ghbvf97fd" for which no system identifier could be generated
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=osRAeNCEOwqlCKJdYrMNpw==&hcbd=Jr843ndmk…

    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 525, Column 170: entity was defined here
    …y73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd…
  • Warning Line 553, Column 210: reference not terminated by REFC delimiter
    …hbvf97fd=osRAeNCEOwqlCKJdYrMNpw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 553, Column 210: reference to external entity in attribute value
    …hbvf97fd=osRAeNCEOwqlCKJdYrMNpw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 553, Column 210: reference to entity "hcbd" for which no system identifier could be generated
    …hbvf97fd=osRAeNCEOwqlCKJdYrMNpw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 205: entity was defined here
    …psS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="…
  • Error Line 557, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <div align="right" style="text-align: justify">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 567, Column 112: reference not terminated by REFC delimiter
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 567, Column 112: reference to external entity in attribute value
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 567, Column 112: reference to entity "bvcud53gd" for which no system identifier could be generated
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 102: entity was defined here
    …shx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje…
  • Warning Line 567, Column 180: reference not terminated by REFC delimiter
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=YAELIgmC2Ayd/KAbwF3i9g==&hcbd=Jr843ndmk…

    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 567, Column 180: reference to external entity in attribute value
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=YAELIgmC2Ayd/KAbwF3i9g==&hcbd=Jr843ndmk…

    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 567, Column 180: reference to entity "ghbvf97fd" for which no system identifier could be generated
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=YAELIgmC2Ayd/KAbwF3i9g==&hcbd=Jr843ndmk…

    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 525, Column 170: entity was defined here
    …y73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd…
  • Warning Line 567, Column 210: reference not terminated by REFC delimiter
    …hbvf97fd=YAELIgmC2Ayd/KAbwF3i9g==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 567, Column 210: reference to external entity in attribute value
    …hbvf97fd=YAELIgmC2Ayd/KAbwF3i9g==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 567, Column 210: reference to entity "hcbd" for which no system identifier could be generated
    …hbvf97fd=YAELIgmC2Ayd/KAbwF3i9g==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 205: entity was defined here
    …psS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="…
  • Error Line 571, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <div align="right" style="text-align: justify">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 583, Column 112: reference not terminated by REFC delimiter
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 583, Column 112: reference to external entity in attribute value
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 583, Column 112: reference to entity "bvcud53gd" for which no system identifier could be generated
    …kd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje883jehd8js…

    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 525, Column 102: entity was defined here
    …shx?ge73dlkd8whdk=HJfcRVqKeh843hD8s9eN&bvcud53gd=HDf2inDBif872Ksmsiey73ndmlaje…
  • Warning Line 583, Column 180: reference not terminated by REFC delimiter
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=QehkZNKklfI4FWI9y++QUQ==&hcbd=Jr843ndmk…

    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 583, Column 180: reference to external entity in attribute value
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=QehkZNKklfI4FWI9y++QUQ==&hcbd=Jr843ndmk…

    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 583, Column 180: reference to entity "ghbvf97fd" for which no system identifier could be generated
    …883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=QehkZNKklfI4FWI9y++QUQ==&hcbd=Jr843ndmk…

    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 525, Column 170: entity was defined here
    …y73ndmlaje883jehd8jsjlFeyshdJVKflFJpsS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd…
  • Warning Line 583, Column 210: reference not terminated by REFC delimiter
    …hbvf97fd=QehkZNKklfI4FWI9y++QUQ==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 583, Column 210: reference to external entity in attribute value
    …hbvf97fd=QehkZNKklfI4FWI9y++QUQ==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 583, Column 210: reference to entity "hcbd" for which no system identifier could be generated
    …hbvf97fd=QehkZNKklfI4FWI9y++QUQ==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="ctl00…

    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 525, Column 205: entity was defined here
    …psS&ghbvf97fd=Jqb79gwjoGybFWGwiY5gXw==&hcbd=Jr843ndmkf8HFfGSsk037hdSGH" name="…
  • Error Line 587, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <div align="right" style="text-align: justify">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 596, Column 57: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<td colspan="3"><font color="Black"><table border="0">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 798, Column 77: there is no attribute "height"
    …<td><table cellpadding="0" cellspacing="0" border="0" width="100%" height="18">

    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 800, Column 206: there is no attribute "valign"
    …><td width="0"><img src="Images\PopOutMenu.png" alt="»" valign="middle" /></td>

    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 897, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 909, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 921, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 933, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 953, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 965, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 977, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 997, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1009, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1021, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1033, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1045, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1065, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1077, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1089, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1101, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1113, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1125, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1137, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1149, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1161, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1173, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1185, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1205, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1217, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1237, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1249, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1261, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1281, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1293, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1305, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1317, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1329, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1341, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1353, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1365, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1377, Column 107: duplicate specification of attribute "width"
    …spacing="0" border="0" width="100%" bgcolor="#B9DEBC" height="18" width="100%">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1489, Column 76: there is no attribute "background"
    …                       <td background="Images/dottedline.gif" style="width: 10…

    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 1577, Column 58: character "&" is the first character of a delimiter but occurred as data
    …     <span id="ctl00_Label9">Designed & Developed by : Behvar Design & Enginee…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1577, Column 89: character "&" is the first character of a delimiter but occurred as data
    …"ctl00_Label9">Designed & Developed by : Behvar Design & Engineering Co.</span>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 1.902 visits