Problem with AutoSearch when connecting into NEWA

[bgowland]

If I understand correctly, when <autoShowSearch> is set to true then whenever I connect into NEWA for the first time in a given day, it runs auto-search.

Earlier I was simply trying to connect in to view the /API details and kept getting an asp error response which seemed to indicate a problem when searching for QI on BBC TWO. When I checked the web.log I saw the following...

Code:

2014-01-02 20:17:18.062    [INFO][14]    NEWA Auto-Record Setting: True
2014-01-02 20:17:18.062    [INFO][14]    Search Auto-Record Setting:True
2014-01-02 20:17:18.062    [INFO][14]    
2014-01-02 20:17:18.062    [INFO][14]    NEWA Auto-Search Setting:True
2014-01-02 20:17:18.062    [INFO][14]    Search Auto-Search Setting: False
2014-01-02 20:17:18.062    [INFO][14]    
2014-01-02 20:17:18.062    [INFO][14]    Where command for search:  where EPG_EVENT.start_time >= datetime('2014-01-02T01:01:00Z') and EPG_EVENT.end_time <= datetime('2014-02-01T01:01:00Z')
2014-01-02 20:17:18.203    [INFO][14]    Where command for search:  where EPG_EVENT.start_time >= datetime('2014-01-02T01:01:00Z') and EPG_EVENT.end_time <= datetime('2014-02-01T01:01:00Z')
2014-01-02 20:17:18.203    [INFO][14]    Search day filtering found.....
2014-01-02 20:17:18.203    [INFO][14]    *** Total events to process = 3
2014-01-02 20:17:18.218    [INFO][14]    .....Processing title for days: QI on channel/date/time: BBC TWO   09/01/2014 21:30:00 Thursday  ==> 09/01/2014 22:00:00 Thursday
2014-01-02 20:17:18.843    [ERROR][14]    System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidCastException: Specified cast is not valid.
   at N_EWA.classes.SearchEngine.filterSearchResults(Int32 minLength, Int32 maxLength, ArrayList selectedDays) in c:\Documents and Settings\All Users\Application Data\NPVR\web\App_Code\Classes\SearchEngine.cs:line 875
   at N_EWA.classes.SearchEngine.SelectEPGEvents(Array channels, Array selectedGenre, Boolean checkTitle, Boolean checkDesc, Boolean checkSubtitle, Boolean matchTitle, Boolean matchDesc, Boolean matchSubtitle, Boolean startTitle, Boolean startDesc, Boolean startSubtitle, Boolean matchUniqueID, String searchFor, Boolean caseSensitive, Schedule scheduleHelper, Int32 EPG_EVENTMinLength, Int32 EPG_EVENTMaxLength, ArrayList selectedDays) in c:\Documents and Settings\All Users\Application Data\NPVR\web\App_Code\Classes\SearchEngine.cs:line 543
   at N_EWA.classes.SavedSearchUtils.autoSearch(ArrayList Searches) in c:\Documents and Settings\All Users\Application Data\NPVR\web\App_Code\Classes\SavedSearch.cs:line 1061
   at N_EWA.Logon.CompleteLogin() in c:\Documents and Settings\All Users\Application Data\NPVR\web\Logon.aspx.cs:line 392
   at N_EWA.Logon.Page_Load(Object sender, EventArgs e) in c:\Documents and Settings\All Users\Application Data\NPVR\web\Logon.aspx.cs:line 119
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   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.logon_aspx.ProcessRequest(HttpContext context) in c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\98d3b820\6de0daa9\App_Web_cb5tder4.4.cs:line 0
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

I had something similar a couple of days ago (possibly exactly the same, I can't remember) but it mysteriously fixed itself somehow (possibly as a result of restarting nrecord). This time around I even rebooted but got the same each time I tried to connect. Eventually I tried setting <autoShowSearch> to false and it fixed the problem, i.e., the auto-search was no longer being performed on connection.

One weird thing is this in web-config.xml...

Code:

<lastAutoSearchDate>02/11/2013</lastAutoSearchDate>

...I normally manually run the NEWA_AutoSearch CLI once a week and I know I've done that since 2nd Nov - also I've successfully connected in to NEWA with a browser several times over the past couple of days and know that auto-search must have run successfully as the "Pending" recordings show a ton of Agatha Christie Poirot and Marple episodes and they only get scheduled via auto-search.

Just wondering what would cause that exception to be thrown and why the last search date is two months out.

Cheers,
Brian

[mvallevand]

If I understand correctly, when <autoShowSearch> is set to true then whenever I connect into NEWA for the first time in a given day, it runs auto-search.

Can you upload you web-saved-searches.xml

Martin

[bgowland]

Attached

[mvallevand]

Odd it does run through here and updates the config-web.xml It return give the 204 code the vlc heartbeats give. Do you have channel 1 and 2 configured?

Martin

[UncleJohnsBand]

Which API method were you trying to execute?

[UncleJohnsBand]

I may have found the problem.... try the attached... put it in wep\app_code\classes

Let m know.

[bgowland]

Odd it does run through here and updates the config-web.xml It return give the 204 code the vlc heartbeats give. Do you have channel 1 and 2 configured?

Yes, all channels relating to the saved searches are present and correct with a fully populated EPG.

Which API method were you trying to execute?

I was simply trying to access localhost:8866/API

I may have found the problem.... try the attached... put it in wep\app_code\classes

Let m know.

Now I'm getting a compilation error - Compiler Error Message: CS0101: The namespace 'N_EWA.classes' already contains a definition for 'SavedSearch'

Code:

Line 18: {
Line 19:     #region Object used to save and load searches
[color=#FF0000]Line 20:     public class SavedSearch[/color]
Line 21:     {
Line 22:         private string SearchName;

[UncleJohnsBand]

Now I'm getting a compilation error - Compiler Error Message: CS0101: The namespace 'N_EWA.classes' already contains a definition for 'SavedSearch'

Code:

Line 18: {
Line 19:     #region Object used to save and load searches
[color=#FF0000]Line 20:     public class SavedSearch[/color]
Line 21:     {
Line 22:         private string SearchName;

That tells me you did not put it in web\app_code\classes it should have overwritten the existing file.... if you have two savedsearch.cs files in the web directory you will get that error,

[bgowland]

That tells me you did not put it in web\app_code\classes it should have overwritten the existing file.... if you have two savedsearch.cs files in the web directory you will get that error,

Nope, I definitely put it where it was supposed to go but the problem was mine.

Instead of overwriting the original I renamed it to SavedSearch-2.1.0.cs in case I wanted to go back to it. It has just occurred to me that the fact it still had the .cs file extension meant it was included in the compilation (sorry, not good with this ASP.NET stuff). I've now renamed it to SavedSeach-2.1.0.cs.bgg and things are looking better. I'll do some more tests later (I've got some shelves to put up in the kitchen...sigh!).

Cheers,
Brian

[UncleJohnsBand]

Nope, I definitely put it where it was supposed to go but the problem was mine.

Instead of overwriting the original I renamed it to SavedSearch-2.1.0.cs in case I wanted to go back to it. It has just occurred to me that the fact it still had the .cs file extension meant it was included in the compilation (sorry, not good with this ASP.NET stuff). I've now renamed it to SavedSeach-2.1.0.cs.bgg and things are looking better. I'll do some more tests later (I've got some shelves to put up in the kitchen...sigh!).

Cheers,
Brian

Great....thanks.... keep me posted.