Bug: Network connection issue (restore?)

[wazerstar]

Hi I have a little gift for you :=)

I removed the rj45 cable from the machine server running hdhr software and plugged it in again, then checked the hd gui from my own machine, seeing it say no devices found, and then it crashed.

Se slutningen af denne meddelelse, hvis du vil have detaljer om,
hvordan du starter JIT-fejlfinding i stedet for denne dialogboks.

************** Undtagelsestekst **************
System.NullReferenceException: Objektreferencen er ikke indstillet til en forekomst af et objekt.
   ved zuki.hdhomeruntray.MainApplication.<OnPopupUnpinned>b__11_0(Object o)


************** Indlæste assemblies **************
mscorlib
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9075.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
hdhomeruntray
    Assemblyversion: 1.1.0.0
    Win32-version: 1.1.0.8237
    CodeBase: file:///C:/stuff/hdhomerunstatusmonitor-1.1.0.8237-x64/hdhomeruntray.exe
----------------------------------------
System.Windows.Forms
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9075.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9065.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
hdhomeruntray.discovery
    Assemblyversion: 1.1.0.0
    Win32-version: 1.1.0.8237
    CodeBase: file:///C:/stuff/hdhomerunstatusmonitor-1.1.0.8237-x64/hdhomeruntray.discovery.DLL
----------------------------------------
System.Configuration
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9065.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Newtonsoft.Json
    Assemblyversion: 13.0.0.0
    Win32-version: 13.0.1.25517
    CodeBase: file:///C:/stuff/hdhomerunstatusmonitor-1.1.0.8237-x64/Newtonsoft.Json.DLL
----------------------------------------
System.Net.Http
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
----------------------------------------
System.Numerics
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9065.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
mscorlib.resources
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_da_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
    Assemblyversion: 4.0.0.0
    Win32-version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_da_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------

************** JIT-fejlfinding **************
Hvis du vil aktivere JIT-fejlfinding, skal værdien jitDebugging indstilles
i afsnittet system.windows.forms i konfigurationsfilen
for programmet eller computeren.
Programmet skal desuden kompileres med fejlfinding
aktiveret.

Eksempel:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Når JIT-fejlfinding er aktiveret, bliver alle ikke-afviklede
undtagelser sendt til det JIT-fejlfindingsprogram, der er registreret på computeren, i stedet for
at blive afviklet af denne dialogboks.

[djp952]

Ouch, that's ungood. Will replicate and fix for you ASAP.

[wazerstar]

Ouch, that's ungood. Will replicate and fix for you ASAP.

Oh another thing I noted which has nothing to do with this issue but thought it would be kinda silly to create a topic for it?

After all these firmware updates recently, while having your program running in the background (tray) and updating my different devices, only the HDHomeRun CONNECT QUATRO would show up in your program after they where all finished updating and rebooting, to get my HDHomeRun EXPAND devices to show up I would have to restart your program, thought you might wanted to know about this, maybe its a detection error or the Quatro is working differently during reboot?

[djp952]

I am thankful for the heads-up, bit I fear that I am not going to be able to adapt to the changes as I do not have any HDHomeRun devices that were affected by the IPv6 update. I have to assume at this point that SD's changes were "breaking" in nature, which was not publicized. My "bandwidth" has been and will continue to be limited for the recent future, but I am confident that when I can spend enough free time on this we will figure something out?