Hi Carlos,

I haven't seen that issue with MNTP before.  It could be to do with content being unpublished, but not sure at this stage.

Next time it happens, could you try viewing the full "TreeDataService.ashx" URL, (with all the querystring data), to see if you find any other error messages. If so, could you copy-n-paste the full stack/trace exception on here? (It might give me a pointer to where the issue lies.)

Thanks, Lee.

Lee, 

Thanks for the response. I can actually get it to do it everytime on certain nodes.  

The nodes are published though.  I will try to look in the TreeDataService.ashx and let you know what I find.

Thanks again for the response.

@Lee,

This is the StackTrace I got back:

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.ArgumentException: The query didn't return a value.

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.

[ArgumentException: The query didn't return a value.]
   umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, P[] parameters) +136
   umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters) +86

[SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteXmlReader]
   umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters) +141
   umbraco.cms.businesslogic.web.Document.importXml() +135
   umbraco.cms.businesslogic.web.Document.ToXml(XmlDocument xd, Boolean Deep) +46
   uComponents.Core.DataTypes.MultiNodeTreePicker.FilteredContentTree.OnRenderNode(XmlTreeNode& xNode, Document doc) +238
   umbraco.cms.presentation.Trees.BaseContentTree.Render(XmlTree& Tree) +166
   umbraco.presentation.webservices.TreeDataService.LoadTree(TreeRequestParams treeParams) +75
   umbraco.presentation.webservices.TreeDataService.GetXmlTree() +140
   umbraco.presentation.webservices.TreeDataService.ProcessRequest(HttpContext context) +55
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Below are screen shots of my process.  There are child nodes in the tree that are unpublished that I am trying to open to view their children , but I can't get to them to chose them because I can not open the some of the trees in the Multi Tree Node Picker. But other nodes with unpublished children, I am able to get inside those trees. So I am not sure what the issue is.  Again, some work and others don't.  But specific ones are having the issues, it is not very random.  Certain nodes I try to view the children of are having the issue.

Hi Carlos,

I've taken a look at the source-code for MNTP (and Umbraco core) to see where it might be failing. From how I understand it, when each tree node is rendered by MNTP the XML for that document/content node is called.  But for some reason the nodes that are failing must be in some *dirty* state, where they are marked as published, but don't have any XML generated for them. (Not sure how that situation could happen!)

It might be worth re-publishing those content nodes to make sure that the XML is generated for them.

Cheers, Lee.

@Lee,

That totally worked.  I republished the trees that were having issues and they work now. Do you think it could be the huge amount of nodes the the size of the XML we have?  Either way, republishing worked.

Thanks again.

Not sure how it might have happened, it does seem that certain content nodes were marked as Published but didn't have any XML. Wondering if there is any custom code (or 3rd party package) that might be interferring with the publishing?

Glad that you've got this immediate problem sorted.

Cheers, Lee.

is working on a reply...