Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

Error: 'Host' is an unexpected token. Expecting white space.
Last Post 08/19/2010 3:27 PM by Peter Donker. 7 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Roger Martin
New Member
New Member
Posts:6


--
08/04/2010 6:11 PM

I am evaluating Document Exchange by installing into a brand new DNN site running the latest version (05.04.04). The module installation went fine but when I add an instance to a page, it shows this error:

A critical error has occurred.
'Host' is an unexpected token. Expecting white space. Line 1, position 188.

The event log shows this:

AssemblyVersion: 5.4.4
PortalID: 0
PortalName: My Website
UserID: 1
UserName: host
ActiveTabID: 61
ActiveTabName: Doc Admin
RawURL: /dnnclocks/DocAdmin.aspx
AbsoluteURL: /dnnclocks/Default.aspx
AbsoluteURLReferrer: http://localhost/dnnclock...talid/0/Default.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 89e41863-b329-477c-a182-64f94e093793
InnerException: 'Host' is an unexpected token. Expecting white space. Line 1, position 188.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Xml.XmlTextReaderImpl.Throw
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: 'Host' is an unexpected token. Expecting white space. Line 1, position 188. ---> System.Xml.XmlException: 'Host' is an unexpected token. Expecting white space. Line 1, position 188. at System.Xml.XmlTextReaderImpl.Throw(String res, String arg) at System.Xml.XmlTextReaderImpl.ParseAttributes() at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XPath.XPathDocument.LoadFromReader(XmlReader reader, XmlSpace space) at System.Xml.Xsl.Runtime.XmlQueryContext.ConstructDocument(Object dataSource, String uriRelative, Uri uriResolved) at System.Xml.Xsl.Runtime.XmlQueryContext..ctor(XmlQueryRuntime runtime, Object defaultDataSource, XmlResolver dataSources, XsltArgumentList argList, WhitespaceRuleLookup wsRules) at System.Xml.Xsl.Runtime.XmlQueryRuntime..ctor(XmlQueryStaticData data, Object defaultDataSource, XmlResolver dataSources, XsltArgumentList argList, XmlSequenceWriter seqWrt) at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter writer) at System.Xml.Xsl.XslCompiledTransform.Transform(XmlReader input, XmlWriter results) at Bring2mind.DNN.Modules.DMX.Common.Globals.XslTransform(XslCompiledTransform transformation, String input, String defaultOutput) at Bring2mind.DNN.Modules.DMX.ViewCollection.ᜂ(Object A_0, EventArgs A_1) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: RDOG

I read the Installation and Getting Started Guides and searched this forum, but haven't found a solution.

The app is running under .NET 4.0, but I switched to a 3.5 app pool and got the same result. I also get the same result when logged in under a portal admin account (rather than a host account).

Any help is appreciated. Thanks!
Roger

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
08/04/2010 9:14 PM
Hi Roger,

Can you try to put your DMX into debug mode by logging in as host and selecting "debug" on the Main Options? Then verify that a LastRequestedMenu.Xml file under portals/[id]/DMX/Temp. Please send that to me by email (peter at bring2mind dot net) and I'll check it out.

Peter
Roger Martin
New Member
New Member
Posts:6


--
08/04/2010 9:26 PM

Where do I enable debug mode? The page only shows the error; there aren't any Doc Exchange options to modify. When I go into Module Definitions, I poked around but didn't see where to set it.

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
08/04/2010 10:36 PM
A yes, good one. Do you even see the module settings on the page if you go to layout mode? Then you can change to TemplateView for the control to load. Then you can get to the main options.

Peter
Roger Martin
New Member
New Member
Posts:6


--
08/04/2010 10:46 PM

Alas, I do not. Here is a link to a screen shot:

http://www.galleryserverpro.com/DocExchangeError.png

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
08/05/2010 10:51 AM
Have you tried removing the double quotes from your display name?

Peter
Roger Martin
New Member
New Member
Posts:6


--
08/05/2010 4:20 PM

You da man! Indeed, quotes cause it to blow up.

The obvious next question is: Is this considered a bug? As far as I can tell, DNN considers quotes valid in a name.

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
08/19/2010 3:27 PM
Bug? Yes. But it is indeed risky to use special characters in properties that reappear in other modules. Not that it's your fault ... it's mine and any other module vendor that doesn't pass the DisplayName property through a check before using it.

Peter
You are not authorized to post a reply.