Error expanding one folder in multi node tree picker
Hello,
We have an implementation of the multi tree node picker that's worked fine for weeks, but one specific instance of the picker just recently stopped working. There's one folder which, when expanded in the picker field, doesn't show any child data and throws a .Net exception behind the scenes. Expanding this same folder in the content tree shows its child data and works fine. I'm assuming there's some strange content issue that recently caused this one folder to break when shown in the multi tree node picker but everything looks ok and I'm not sure why this would cause it to break.
Checking the event viewer I see the following exception when the ajax call is made to expand that folder (http://www.mydomain.com/umbraco/webservices/TreeDataService.ashx?rnd=39d4a5c6b18d40e1a11077d24cb83c4a&id=1072&treeType=FilteredContentTree&contextMenu=false&isDialog=true&dialogMode=id&nodeKey=1461&rnd2=20.3)
Server Error in '/' Application.
The query didn't return a value.
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.
Stack Trace:
[ArgumentException: The query didn't return a value.] umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, P[] parameters) +168 umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters) +140
If at all possible, could you download the umbraco source code from Codeplex, attach visual studio to the w3wp process and see if you get asked for the umbraco source, just point it to the correct file from the codeplex download and then you might be able to see what's wrong. Just add a breakpoint before the exception and see what is going on in the actual source.
Looks like the issue was related to an item having a 'remove at' unpublish date. That date had passed, the item had been unpublished, and from that point on the multi node tree picker stopped working.
Our client entered another remove at date for an item in the multi tree node picker which, after that date had passed, resulted in the picker no longer displaying anything. Is there a plan to fix this so I can communicate that to the client?
This just came up again--does anyone have any updates on why this happens when content within the multi node tree picker has a remove at date set? Or better yet, a fix?
In my test, I set the "Remove At" date for a content node, (to expire in 10 mins time), added that node to a MNTP and saved & published it. I went away for 10 mins (made a cup of tea), then came back. The content node was now unpublished (as expected), then when I viewed the MNTP, there was no error/exception.
I had Visual Studio attached to the worker process, with a breakpoint on the "uComponents.Core.DataTypes.MultiNodeTreePicker.FilteredContentTree.OnRenderNode" call ... but no exceptions.
Which version of Umbraco and uComponents are you using? (I tested with Umbraco 4.7.0 and uComponents v2.2-beta)
Thanks for taking a look at this for me! We are running slightly older versions on this particular site--Umbraco 4.5.2 and uComponents 2.0.1.
Do you know if uComponents 2.2 is compatible with Umbraco 4.5.2, and if so, would there be any breaking changes in the upgrade? I'd need to do some more legwork to determine the impacts of upgrading Umbraco to 4.7 as this site is running on .Net 3.5, etc.
FYI - there was a bug with the "Remove At" functionality in 4.5.2, where the document didn't get "fully" unpublished - it was removed from the cache but its Published flag was still set to true. This was causing some exceptions with the Sorting functionality - and could possibly be related to this issue (?). Perhaps MNTP is seeing the node as published but it doesn't exist in the cache/xml.
I am getting this error (Same stack trace) with uComponentsv 2.2Beta3 and umbraco v4.6.1 (old schema) but only on one node in my tree (that I've noticed)
I don't think it's related to 'remove at' or anything like that.
I was having the exact same problem. In my case it was due to the presence of corrupts nodes at the branch of the content tree. I located the nodes and then republished them, that fixed the problem and the MNTP was able to open the branch. I used the following SQL to find the corrupt nodes, they have NULL at the xml column:
select * from umbraconode u full outer join cmscontentxml c on u.id = c.nodeid where u.parentid = nnn
I still had this issue even after upgrading to the latest version of Umbraco 4.11.9 from 4.7.0. This seems to confirm my fears - that Umbraco just doesn't work well with the larger number of nodes. Small-to-Medium-Enterprises (SME's) websites are usually fine. This has happened on two other websites of ours, and in the end we've had to replace the data nodes with custom usercontrols and their own secondary databases, instead of using the Umbraco framework.
Error expanding one folder in multi node tree picker
Hello,
We have an implementation of the multi tree node picker that's worked fine for weeks, but one specific instance of the picker just recently stopped working. There's one folder which, when expanded in the picker field, doesn't show any child data and throws a .Net exception behind the scenes. Expanding this same folder in the content tree shows its child data and works fine. I'm assuming there's some strange content issue that recently caused this one folder to break when shown in the multi tree node picker but everything looks ok and I'm not sure why this would cause it to break.
Checking the event viewer I see the following exception when the ajax call is made to expand that folder (http://www.mydomain.com/umbraco/webservices/TreeDataService.ashx?rnd=39d4a5c6b18d40e1a11077d24cb83c4a&id=1072&treeType=FilteredContentTree&contextMenu=false&isDialog=true&dialogMode=id&nodeKey=1461&rnd2=20.3)
Server Error in '/' Application.
The query didn't return a value.
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.Stack Trace:
Version Information: Microsoft .NET Framework Version:2.0.50727.4206; ASP.NET Version:2.0.50727.4205
If at all possible, could you download the umbraco source code from Codeplex, attach visual studio to the w3wp process and see if you get asked for the umbraco source, just point it to the correct file from the codeplex download and then you might be able to see what's wrong. Just add a breakpoint before the exception and see what is going on in the actual source.
Looks like the issue was related to an item having a 'remove at' unpublish date. That date had passed, the item had been unpublished, and from that point on the multi node tree picker stopped working.
Our client entered another remove at date for an item in the multi tree node picker which, after that date had passed, resulted in the picker no longer displaying anything. Is there a plan to fix this so I can communicate that to the client?
This just came up again--does anyone have any updates on why this happens when content within the multi node tree picker has a remove at date set? Or better yet, a fix?
Hi Matt,
I have tried to reproduce this error, but no joy.
In my test, I set the "Remove At" date for a content node, (to expire in 10 mins time), added that node to a MNTP and saved & published it. I went away for 10 mins (made a cup of tea), then came back. The content node was now unpublished (as expected), then when I viewed the MNTP, there was no error/exception.
I had Visual Studio attached to the worker process, with a breakpoint on the "uComponents.Core.DataTypes.MultiNodeTreePicker.FilteredContentTree.OnRenderNode" call ... but no exceptions.
Which version of Umbraco and uComponents are you using? (I tested with Umbraco 4.7.0 and uComponents v2.2-beta)
Thanks, Lee.
Hi, Lee,
Thanks for taking a look at this for me! We are running slightly older versions on this particular site--Umbraco 4.5.2 and uComponents 2.0.1.
Do you know if uComponents 2.2 is compatible with Umbraco 4.5.2, and if so, would there be any breaking changes in the upgrade? I'd need to do some more legwork to determine the impacts of upgrading Umbraco to 4.7 as this site is running on .Net 3.5, etc.
Thanks again!
Matt
Hi Matt,
We still support Umbraco 4.5.2 with uComponents 2.2 (currently beta) ... and we still compile against .NET 3.5 ... so you'll be fine with upgrading.
If I get time, I'll try to test this with Umbraco 4.5.2, see if I can reproduce the issue.
Cheers, Lee.
Hi,
FYI - there was a bug with the "Remove At" functionality in 4.5.2, where the document didn't get "fully" unpublished - it was removed from the cache but its Published flag was still set to true. This was causing some exceptions with the Sorting functionality - and could possibly be related to this issue (?). Perhaps MNTP is seeing the node as published but it doesn't exist in the cache/xml.
The bug was fixed in 4.6.1.
Hope this might help :)
-Tom
I am getting this error (Same stack trace) with uComponentsv 2.2Beta3 and umbraco v4.6.1 (old schema) but only on one node in my tree (that I've noticed)
I don't think it's related to 'remove at' or anything like that.
Hi
I was having the exact same problem. In my case it was due to the presence of corrupts nodes at the branch of the content tree. I located the nodes and then republished them, that fixed the problem and the MNTP was able to open the branch. I used the following SQL to find the corrupt nodes, they have NULL at the xml column:
Hope this helps
Jorge
I still had this issue even after upgrading to the latest version of Umbraco 4.11.9 from 4.7.0. This seems to confirm my fears - that Umbraco just doesn't work well with the larger number of nodes. Small-to-Medium-Enterprises (SME's) websites are usually fine. This has happened on two other websites of ours, and in the end we've had to replace the data nodes with custom usercontrols and their own secondary databases, instead of using the Umbraco framework.
is working on a reply...