Upgraded from 3.9.2 to 4.0.4 now web server broken

[itm2]

I upgraded from v3.9.2 to v4.0.4 (after first closing NPVR service), and now I can't access the NPVR web server - I get a timeout when attempting to access it on the localhost. I've tried rebooting, then renaming config-web.xml and restarting the NPVR recording service, but neither helped. I can open the NPVR application and see the WEPG etc, but have no web access. I attach my log files.

Any ideas??

[itm2]

I should have said - it's running on Windows 10

[HunsakerEastIdaho]

(Your log files are about as useful as mine, as in they are failing to capture the actual error.)

I'm not sure if we are having the same problem. I also am on Windows 10. I kept getting a runtime error (I have the browser's "debug" feature enabled) stating the GetIP4Address function wasn't defined. The definition for this routine actually was missing from my "web\App_Code\Classes\Settings.cs" file. After comparing the new settings.cs file with the older version in the standard NEWA zip file, I found the missing section in the old file and copied it to the appropriate location in the new file. After this, all my NPVR web pages are back to working. (FYI, this particular fix also takes without having to stop then restart the service.)

Specifically, right before the section that begins with:
public string[] ParseAutologinNetworks()

Insert the following:

Code:

public string GetIP4Address()
        {
            string strIP4Address = String.Empty;

            foreach (IPAddress objIP in Dns.GetHostAddresses(Dns.GetHostName()))
            {
                if (objIP.AddressFamily.ToString() == "InterNetwork")
                {
                    strIP4Address = objIP.ToString();
                    break;
                }
            }
            return strIP4Address;
        }

[HunsakerEastIdaho]

P.S. The "Post Quick Reply" stripped out all the leading space characters from the above code. It still will work, but isn't quite as easy to read. Sorry about that.

[sub]

I'm not sure if we are having the same problem. I also am on Windows 10. I kept getting a runtime error (I have the browser's "debug" feature enabled) stating the GetIP4Address function wasn't defined. The definition for this routine actually was missing from my "web\App_Code\Classes\Settings.cs" file. After comparing the new settings.cs file with the older version in the standard NEWA zip file, I found the missing section in the old file and copied it to the appropriate location in the new file. After this, all my NPVR web pages are back to working. (FYI, this particular fix also takes without having to stop then restart the service.)

Did you notice what page or cs file needed this function to exist?

I just had a check of the code, and looks like everything is depending on Global.GetIP4Address() (from Global.cs). ie, you shouldnt need to define this in Settings.cs. I'm wondering if one of your other files failed to update during the upgrade?

[mvallevand]

Web server errors are often logged in the event viewer.

Martin

[HunsakerEastIdaho]

The specific cs file that calls the GetIP4Address function is web\App_Code\Classes\VerifyInernalNetworkJSON.cs ("Inernal", not "Internal")

[mvallevand]

Yes that is a normal error typically because you have obsolete file left over and you don't have NextPVR installed in the normal c:\users\public\npvr folder.

The correct solution is to delete web\App_Code\Classes\VerifyInernalNetworkJSON.cs

Martin

[HunsakerEastIdaho]

I just verified that deleting VerifyInernalNetworkJSON.cs also solves my problem. Thanks!

(For reasons I feel are inappropriate to discuss in a public forum, I use ProgramData instead of Users\Public, but I also added a 2nd complication by naming the next folder NextPVR instead of NPVR. The latter definitely is my bad.)

itm2, have you been able to follow through on mvallevand's advice to check the Event Viewer for web server errors? My particular problem shows up in the Application event log, with a source of "ASP.NET.4.0.30319.0". Your particular error should also show up in the Application event log, but it may show up coming from a different source...