Browser Forms

Re: Unexpected end of file while parsing Name has occurred.

maxlisi — Mon, 25 Jan 2010 09:01:21 GMT

Hi all, I had the same error. I looked for a solution in google, but no one solved my problem and finally I found the solution! One Custom List of the application had the char "à" with the accent. A dropdown was linked to that data source, so when another dropdown configured to call a webservice or when the form was submitted, this error occured. Changing the Custom List name, the problem disappeared. Hope this helps!

Re: Unexpected end of file while parsing Name has occurred.

Bernhard Gelderblom — Mon, 12 Oct 2009 12:22:03 GMT

I have a browser enabled info path form which uses two SharePoint lists as primary data source. A MOSS document library is the submit data source. Later, the MOSS document library became a secondary data source as well in order to do some validations. Then, the error "Unexpected end of file while parsing Name has occurred. Line 1, position XXX" occurred.

After installing Windows SharePoint Services SP2 (http://www.microsoft.com/downloads/details.aspx?FamilyID=79bada82-c13f-44c1-bdc1-d0447337051b&displaylang=en) and Office Server 2007, SP2 (http://www.microsoft.com/downloads/details.aspx?FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082&displaylang=en), the problem disappeared. It was possible to have a secondary data source which was not used when opening the form, but later, when it was necessary to do some validations.

Hope it helps in other, similar cases as well.

Re: Unexpected end of file while parsing Name has occurred.

CraigW — Tue, 24 Mar 2009 15:56:28 GMT

I am getting the same problem, and have also checked my data sources and they are all used. Did you ever get to the bottom of this?

Craig

Re: Unexpected end of file while parsing Name has occurred.

Mierk — Mon, 05 Jan 2009 14:49:22 GMT

I am experiencing the same behavior and I have evaluated all of my secondary data sources. All of them are used. Is there any other reason why this error would occur?

Thanks!

Re: Unexpected end of file while parsing Name has occurred.

arosoccer — Fri, 07 Nov 2008 15:00:08 GMT

I found this at

http://blogs.msdn.com/infopath/archive/2006/11/22/workflow-user-experience-in-infopath.aspxThe error "Unexpected end of file while parsing name" is not isolated to workflow forms - this is a known issue with InfoPath browser forms. The cause of this error is having secondary data connections in your InfoPath form template (the XSN) that are not being used anywhere in your main data source (DOM.)You can either remove any data connections that are not being used or if you would prefer to keep those connections then simply add a "dummy" node in your data source for each one that is not being used and set the default value for that new node to some field from that data source.

Hope it helps

Andrew

Unexpected end of file while parsing Name has occurred.

poonam.banthia — Wed, 30 Jul 2008 15:25:40 GMT

I have a simple infopath 2007 form that has two "Receive Data" connections from a Sharepoint List. The form works perfectly fine in infopath but gives the following error after publishing to Infopath Forms Services:Unexpected end of file while parsing Name has occurred. Line 1, position 301. System.Xml.XmlException: Unexpected end of file while parsing Name has occurred. Line 1, position 301.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String arg)
at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos)
at System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag)
at System.Xml.XmlTextReaderImpl.ParseEndElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at Microsoft.Office.InfoPath.Server.Xml.InfoPathXmlDocument.Load(XmlReader reader)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataObject.<>c__DisplayClass3.<.ctor>b__0()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)
at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(ULSTagID tagID, ULSCat categoryID, String output, Boolean fRethrowException, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataObject..ctor(EnhancedBinaryReader reader, Solution solution)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataObjects.<>c__DisplayClass2.<.ctor>b__0(EnhancedBinaryReader innerReader, DataObject& newObject)
at Microsoft.Office.InfoPath.Server.Serialization.EnhancedBinaryReader.ReadObjectMap[KeyT,ValueT](Dictionary`2 map, ItemReaderDelegate`1 readKey, ItemReaderDelegate`1 readValue)
at Microsoft.Office.InfoPath.Server.Serialization.EnhancedBinaryReader.ReadObjectMap[ValueT](Dictionary`2 map, ItemReaderDelegate`1 readValue)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataObjects..ctor(EnhancedBinaryReader reader, Solution solution)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DocumentSessionState.DesterilizeVersion1(EnhancedBinaryReader reader, Solution solution)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DocumentSessionState..ctor(EnhancedBinaryReader reader, Solution solution)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DocumentSessionState.CreateFromByteArray(Byte[] serializedSessionState, Byte[] serializedVersionState, Solution solution)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.DocumentSessionStateManager.GetSessionState(HttpContext context, String editingSessionID, Solution solution)
at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.LoadFromSession(HttpContext context, SPSite contextSite, EventLogStart eventLogStart, Solution solution)
at Microsoft.Office.InfoPath.Server.Controls.PostbackPage.<>c__DisplayClass1.<ProcessRequest>b__0()

I have checked the following things:

a) I have no unused data connections in my formb) The forms loads perfectly & the error occurs only when I click on the default "Close" button in the toolbar. The error also occurs when I click on any other button in the form (that simply applies certain rules or switches to a different view) Can someone pls help me with this issue? Thanks!!