TreeView no longer working in Advanced Search

[wtg]

I just upgraded to 2.4.3 and found TreeView no longer works on the Advanced Search screen. I search, get the results in a Table view mode, click the Tree View radio button and then get a "Problem loading page" error. I then upgraded NEWA to the 1.25 release and applied the patches and tried it again, same result. I tried it with both FireFox, IE 9 and my phone - all fail.

By the way, is there anyway to default the results to TreeView output? If not, could this be configurable or at least selectable from the Search screen *before* clicking the Search button? I often use a search that shows me all the upcoming movie channels listings for the next two weeks and with lots of search results, the table format is impractical. The Treeview is perfect since it aggregates all the showings of a movie into one entry and all the times lists below it, making it much easier to sort through the results and pick the movies I want to record.

Thanks,
Tim

[UncleJohnsBand]

My guess is that it is data related.......can you stop your npvr service.....then start it.....do the search and switch to tree view and then post your web.log file found in the NPVR logs directory.

As for the default......your selection should stay for next use.....so if you selected tree view (and it works) the next time you search it should be in tree view as well.

[wtg]

This is the error shown in the log

2012-04-26 08:00:33.738 [ERROR][3] System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.Web.HttpException: Maximum request length exceeded.
at System.Web.HttpRequest.GetEntireRawContent()
at System.Web.HttpRequest.FillInFormCollection()
at System.Web.HttpRequest.get_Form()
at System.Web.HttpRequest.get_HasForm()
at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
at System.Web.UI.Page.DeterminePostBackMode()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace ---
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.searchresults2_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\0a635572\38fd2de4\App_Web_s96nejaa.12.cs:line 0
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

[wtg]

I learned a little more I think you'll be interested in.

The listing my search generates is for all shows on 12 HD movie channels over the next 2 weeks. It's a long listing but it doesn't seem unreasonably so, and I've not had trouble with it and have used it for a year or more routinely. But wondering what would happen if I reduced the number of channels, I removed two from the list, retrieved the results, clicked TreeView and it worked - with less volume it was able to convert from Table View to TreeView.

I did some more playing around with it and as you mentioned above, once I viewed a result in TreeView mode the choice stuck and my searches all returned result in TreeView mode. With one successful TreeView search under my belt, I then went back and did my normal 12 channel search and lo and behold, it worked! All listing for those 12 channels are returned in a TreeView fine. I then clicked Table View and the listing changed into a Table View format ok, but clicking TreeView once more I received the dreaded "Problem loading page" error. So the problem appears to only be found when converting from Table View -> TreeView, and only with a large volume of data.

Additionally, I thought perhaps the error could be related to converting a specific listing the results and the 2 channels I removed from my original 12 channe listing had the bad records. So I returned all results for just those two channels and found I could convert from Table View -> TreeView fine. It really does appear to be simply volume related with the Table View -> TreeView conversion.

If there's anything else you need from me, let me know.

Thanks,
Tim

[UncleJohnsBand]

Stop npvr service.......replace the current web.config file in npvr\web with the attached. Restart the service and let me know if it is fixed.

[wtg]

That seemed to take care of it... thanks!

However I did notice that the Table View/TreeView preference is lost with the server restart. It would be nice if the preference could be saved or the default specified somehow.

Thanks again,
Tim

[UncleJohnsBand]

That seemed to take care of it... thanks!

However I did notice that the Table View/TreeView preference is lost with the server restart. It would be nice if the preference could be saved or the default specified somehow.

Thanks again,
Tim

That setting is stored in a client cookie.....so perhaps your client machine is blocking cookies or cleaning them up.