Skip to main content
July 24, 2013
Question

There is an error in XML document - TimeStamp

  • July 24, 2013
  • 1 reply
  • 1949 views

Hi All,

Hope you can help. Captivate has been working great so far on our LMS. But since moving to Captivate 7 when submitting we get the below problem,

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---&gt; System.InvalidOperationException: There is an error in XML document (2, 1250). ---&gt; System.FormatException: The string '2013-07-24T16:30:41.0+02' is not a valid AllXsd value.

   at System.Xml.Schema.XsdDateTime..ctor(String text, XsdDateTimeFlags kinds)

   at System.Xml.XmlConvert.ToDateTime(String s, XmlDateTimeSerializationMode dateTimeOption)

   at System.Xml.Serialization.XmlCustomFormatter.ToDateTime(String value)

   at System.Xml.Serialization.XmlSerializationReader.ToDateTime(String value)

   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read19_interactionType(Boolean isNullable, Boolean checkType)

   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read20_interactionsType(Boolean isNullable, Boolean checkType)

   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read32_cocdType(Boolean isNullable, Boolean checkType)

   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read34_RteDataModelType(Boolean isNullable, Boolean checkType)

   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read36_Commit(Boolean isNullable, Boolean checkType)

   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read41_Commit()

   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer4.Deserialize(XmlSerializationReader reader)

   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

--- End of inner exception stack trace ---

   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)

   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()

--- End of inner exception stack trace ---

   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()

   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>

Is this a problem possibly between the editions of SCORM or is it something in the Captivate product? Perhaps the xml parser version?

This topic has been closed for replies.

1 reply

Participating Frequently
July 25, 2013

Hi,

Can you please upload your project to cloud.scorm.com and check if it works there.

Are you publishing as scorm1.2 or scorm2004.

Can you please mention which LMS are you using.

Regards,

Haridoss

July 25, 2013

Thanks,

I have tested on SCORM Cloud and it is working... The SCORM content has been published with 2004 3rd edition.

We are making use of the Icodeon SCORM player (integrate with Signify LMS), do you perhaps think it could be something on the SCORM player then?