# dateTime format: Missing or invalid XML node; element="Value"

**URL:** <https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014>\
**Category:** Uncategorized\
**Created:** [September 12, 2021, 7:03pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014 "2021-09-12T19:03:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![mtarifa](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/mtarifa/32/848_2.png) [@mtarifa](https://forum.genieacs.com/u/mtarifa)\
**Post date:** [September 12, 2021, 7:03pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/1 "2021-09-12T19:03:52Z")

</div>

Hello.

Im havig the message 'Missing or invalid XML node; element=“Value” ’ for some responses of a value of datetime, but other does not. I dont know if this is some bad manage of CPE or it is some bug for different format:

GOT the error over response:  
soap-enc:arrayType=“xsd:string[1]”\>Device.IP.Interface.1.IPv6Address.1.ValidLifetime\</cwmp:GetParameterValues\>\</soap-env:Body\>\</soap-env:Envelope\>  
body: “\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>\n\<SOAP-ENV:Envelope xmlns:SOAP-ENV=“[http://schemas.xmlsoap.org/soap/envelope/](http://schemas.xmlsoap.org/soap/envelope/)” xmlns:SOAP-ENC=“[http://schemas.xmlsoap.org/soap/encoding/](http://schemas.xmlsoap.org/soap/encoding/)” xmlns:xsi=“[http://www.w3.org/2001/XMLSchema-instance](http://www.w3.org/2001/XMLSchema-instance)” xmlns:xsd=“[XML Schema](http://www.w3.org/2001/XMLSchema)” xmlns:cwmp=“urn:dslforum-org:cwmp-1-0”\>\n\tSOAP-ENV:Header\n\t\t\<cwmp:ID SOAP-ENV:mustUnderstand=“1”\>17bd77dd6240000\</cwmp:ID\>\n\t\</SOAP-ENV:Header\>\n\tSOAP-ENV:Body\n\t\tcwmp:GetParameterValuesResponse\n\t\t\t\<ParameterList xsi:type=“SOAP-ENC:Array” SOAP-ENC:arrayType=“cwmp:ParameterValueStruct[1]”\>\n\t\t\t\t\n\t\t\t\t\tDevice.IP.Interface.1.IPv6Address.1.ValidLifetime\n\t\t\t\t\t\<Value xsi:type=“xsd:dateTime”\>0-12-31T23:59:59\n\t\t\t\t\n\t\t\t\n\t\t\</cwmp:GetParameterValuesResponse\>\n\t\</SOAP-ENV:Body\>\n\</SOAP-ENV:Envelope\>\r\n”

I do NOT have error on this one:  
root@GenieACS:/mnt/usb-drive/log/genieacs# tail -f genieacs-debug.yaml | grep “Device.Time.CurrentLocalTime”  
soap-enc:arrayType=“xsd:string[1]”\>Device.Time.CurrentLocalTime\</cwmp:GetParameterValues\>\</soap-env:Body\>\</soap-env:Envelope\>  
body: “\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>\n\<SOAP-ENV:Envelope xmlns:SOAP-ENV=“[http://schemas.xmlsoap.org/soap/envelope/](http://schemas.xmlsoap.org/soap/envelope/)” xmlns:SOAP-ENC=“[http://schemas.xmlsoap.org/soap/encoding/](http://schemas.xmlsoap.org/soap/encoding/)” xmlns:xsi=“[http://www.w3.org/2001/XMLSchema-instance](http://www.w3.org/2001/XMLSchema-instance)” xmlns:xsd=“[XML Schema](http://www.w3.org/2001/XMLSchema)” xmlns:cwmp=“urn:dslforum-org:cwmp-1-0”\>\n\tSOAP-ENV:Header\n\t\t\<cwmp:ID SOAP-ENV:mustUnderstand=“1”\>17bd777c51c0000\</cwmp:ID\>\n\t\</SOAP-ENV:Header\>\n\tSOAP-ENV:Body\n\t\tcwmp:GetParameterValuesResponse\n\t\t\t\<ParameterList xsi:type=“SOAP-ENC:Array” SOAP-ENC:arrayType=“cwmp:ParameterValueStruct[1]”\>\n\t\t\t\t\n\t\t\t\t\tDevice.Time.CurrentLocalTime\n\t\t\t\t\t\<Value xsi:type=“xsd:dateTime”\>2021-09-12T00:45:55.980000Z\n\t\t\t\t\n\t\t\t\n\t\t\</cwmp:GetParameterValuesResponse\>\n\t\</SOAP-ENV:Body\>\n\</SOAP-ENV:Envelope\>\r\n”

This are the difference (another example)  
OK: “xsd:dateTime”\>2021-09-12T00:45:55.980000Z\n\t\t\t\t  
NOK: “xsd:dateTime”\>1-01-01T00:00:50\n\t\t\t\t

Thank you

---

<div class="post-metadata">

**Author:** ![zaidka](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/zaidka/32/9_2.png) [@zaidka](https://forum.genieacs.com/u/zaidka)\
**Post date:** [September 14, 2021, 10:35pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/2 "2021-09-14T22:35:21Z")

</div>

This `1-01-01T00:00:50` is not a ISO-8601 string. The year part must be at least 4 digits.

---

<div class="post-metadata">

**Author:** ![mtarifa](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/mtarifa/32/848_2.png) [@mtarifa](https://forum.genieacs.com/u/mtarifa)\
**Post date:** [September 15, 2021, 7:41pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/3 "2021-09-15T19:41:16Z")

</div>

Thank you Zaidka, will check with the vendor. It seems that the responses have a mixed format for some nodes

again thank you for the quick precise technical information

---

<div class="post-metadata">

**Author:** ![mtarifa](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/mtarifa/32/848_2.png) [@mtarifa](https://forum.genieacs.com/u/mtarifa)\
**Post date:** [September 29, 2022, 3:39am UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/4 "2022-09-29T03:39:10Z")

</div>

Hello Zadika, i do some resarch about this point about zero value

TR-69 Amendment: [https://www.broadband-forum.org/technical/download/TR-106\_Amendment-2.pdf](https://www.broadband-forum.org/technical/download/TR-106_Amendment-2.pdf), Table 1 from section 3.2 Data Types, page 20, dateTime row. Unknown time syntax is described as 0001-01-01T00:00:00.

And, from RFC:  
[https://www.rfc-editor.org/rfc/rfc5905](https://www.rfc-editor.org/rfc/rfc5905)  
Timestamps are unsigned values, and operations on them produce a result in the same or adjacent eras. Era 0 includes dates from the prime epoch to some time in 2036, when the timestamp field wraps around and the base date for era 1 is established. In either format, a value of zero is a special case representing unknown or unsynchronized time.

So, 0 may shall be used. However, may be ACS should translates 0001-01-01T00:00:00 …? since 0 must be expected.  
But if the CPE express other than “0” , like 1-01-01T00:00:00 , it shoud do a fix to correct to 0001-01-01T00:00:00, right?

let me know what you think, and thanks to had time to read this.

Best regards!,  
MT

---

<div class="post-metadata">

**Author:** ![zaidka](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/zaidka/32/9_2.png) [@zaidka](https://forum.genieacs.com/u/zaidka)\
**Post date:** [September 29, 2022, 3:41pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/5 "2022-09-29T15:41:11Z")

</div>

Sorry, I don’t understand. How is RFC 5905 relevant here?

---

<div class="post-metadata">

**Author:** ![mtarifa](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/mtarifa/32/848_2.png) [@mtarifa](https://forum.genieacs.com/u/mtarifa)\
**Post date:** [September 29, 2022, 4:33pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/6 "2022-09-29T16:33:10Z")

</div>

I take RCF for ntp timing protocol, may be is not relevant but i hardly try to found what “If the time is unknown or not applicable” (unnkow value) is defined to be interpreted as “0001-01-01T00:00:00” when returned value is not proper defined (like 1-01-01T00:00:00, garbage or “0”).  
NTP time protocol refeers for 0 as a valid value for unkow or unsynchronized… thats why i come up with this rfc.

May be the any unknow value should be expresed right as 0001-01-01T00:00:00 or 0001-01-01T00:00:00Z, and thats it… i just want to confirm with you if im in the right way.

thank you.

---

<div class="post-metadata">

**Author:** ![zaidka](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/zaidka/32/9_2.png) [@zaidka](https://forum.genieacs.com/u/zaidka)\
**Post date:** [September 29, 2022, 4:56pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/7 "2022-09-29T16:56:02Z")

</div>

Yeah, this has no bearing whatsoever on the question of whether the CPE’s datetime string is valid.

---

<div class="post-metadata">

**Author:** ![mtarifa](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/mtarifa/32/848_2.png) [@mtarifa](https://forum.genieacs.com/u/mtarifa)\
**Post date:** [September 29, 2022, 5:06pm UTC](https://forum.genieacs.com/t/datetime-format-missing-or-invalid-xml-node-element-value/2014/8 "2022-09-29T17:06:27Z")

</div>

understood, thanks.

BR