I have this error when I try to Manage REST API
'CommunityServer/Rest�' has an invalid token. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Xml.XPath.XPathException: 'CommunityServer/Rest�' has an invalid token.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [XPathException: 'CommunityServer/Rest�' has an invalid token.]MS.Internal.Xml.XPath.XPathScanner.NextLex() +644MS.Internal.Xml.XPath.XPathParser.ParseNodeTest(AstNode qyInput, AxisType axisType, XPathNodeType nodeType) +59MS.Internal.Xml.XPath.XPathParser.ParseStep(AstNode qyInput) +188MS.Internal.Xml.XPath.XPathParser.ParseRelativeLocationPath(AstNode qyInput) +11MS.Internal.Xml.XPath.XPathParser.ParseRelativeLocationPath(AstNode qyInput) +126MS.Internal.Xml.XPath.XPathParser.ParseLocationPath(AstNode qyInput) +121MS.Internal.Xml.XPath.XPathParser.ParsePathExpr(AstNode qyInput) +70MS.Internal.Xml.XPath.XPathParser.ParseUnionExpr(AstNode qyInput) +21MS.Internal.Xml.XPath.XPathParser.ParseUnaryExpr(AstNode qyInput) +30MS.Internal.Xml.XPath.XPathParser.ParseMultiplicativeExpr(AstNode qyInput) +17MS.Internal.Xml.XPath.XPathParser.ParseAdditiveExpr(AstNode qyInput) +17MS.Internal.Xml.XPath.XPathParser.ParseRelationalExpr(AstNode qyInput) +17MS.Internal.Xml.XPath.XPathParser.ParseEqualityExpr(AstNode qyInput) +17MS.Internal.Xml.XPath.XPathParser.ParseAndExpr(AstNode qyInput) +16MS.Internal.Xml.XPath.XPathParser.ParseOrExpr(AstNode qyInput) +16MS.Internal.Xml.XPath.XPathParser.ParseXPathExpresion(String xpathExpresion) +51System.Xml.XPath.XPathExpression.Compile(String xpath, IXmlNamespaceResolver nsResolver) +44System.Xml.XPath.XPathNavigator.Select(String xpath) +11System.Xml.XmlNode.SelectSingleNode(String xpath) +29CommunityServer.Components.ApplicationConfiguration.Instance(Type type, Boolean useCache) +106CommunityServer.WebServices.Services.Common.RestConfiguration.Instance(Boolean useCache) +15CommunityServer.ControlPanel.Tools.ManageRest.Page_Load(Object sender, EventArgs e) +40System.Web.UI.Control.OnLoad(EventArgs e) +99CommunityServer.ControlPanel.UI.PanelPage.OnLoad(EventArgs e) +4System.Web.UI.Control.LoadRecursive() +47System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
We determined the problem to be an issue with our obfuscation tool. The problem has been corrected and the download packages have been updated, so grab them for the fix.
Hi Guys,
I encountered the same probem. Upgraded comunity server 2007 to 2007.1 and from their to 2008. I am using ASP.NET version 2.0 on Windows 2003 Standard. Everything else seems to work fine.
Just found this out. CS 2008 SP1 seems to have totally broken the REST API. http://dev.communityserver.com/forums/t/500302.aspx
Nick - nb development
We've verified the problem and are investigating. We'll post back with a response soon.
I think I found something:
In the SP1 you ship CommunityServer.WebServices.Services.dll and CommunityServer.WebServices.dll.
CommunityServer.WebServices.Services.dll has a referecnce to CommunityServer.WebServices.dll Version 4.0.30610.20608, but you are shipping Version 4.0.30610.27608.
I hope you can fix this issue asap, because I get stuck with my project which has to go online next week!!
Dave Donaldson: We determined the problem to be an issue with our obfuscation tool. The problem has been corrected and the download packages have been updated, so grab them for the fix.
Could you tell me which file or folder I have to replace to fix this issue? Or I have to replace all?
Replacing the dlls seems to have fixed it
Ok, the issue solved.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com