Announcement

Collapse
No announcement yet.

Error Crashing HS3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error Crashing HS3

    I'm not entirely sure where the error lies on this but I'm trying to get to the bottom of the problem as it's bugging me as well as causing a problem if Im not about to restart HS.

    Initially problem reported here:

    https://forums.homeseer.com/showthread.php?t=189890

    Error report there but for the sake of completeness:

    EventData

    HS3.exe
    3.0.0.318
    58e6a9d9
    ntdll.dll
    10.0.14393.479
    58256ca0
    c0000005
    00058833
    10c0
    01d2f675c47eb0f6
    C:\Program Files (x86)\HomeSeer HS3\HS3.exe
    C:\WINDOWS\SYSTEM32\ntdll.dll
    24d9f18c-7233-477e-ba7c-b18611365661

    + System

    - Provider

    [ Name] .NET Runtime

    - EventID 1026

    [ Qualifiers] 0

    Level 2

    Task 0

    Keywords 0x80000000000000

    - TimeCreated

    [ SystemTime] 2017-07-07T12:42:29.891823600Z

    EventRecordID 41774

    Channel Application

    Computer HAPC-PC

    Security


    - EventData

    Application: HSPI_JowiHue.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(System.Runtime.Remoting.Messa ging.IMessage) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Syst em.Runtime.Remoting.Proxies.MessageData ByRef, Int32) at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String) at HSPI_JowiHue.utils.Log(System.String, LogLevel) at HSPI_JowiHue.UPNP.Bridgescan() at HSPI_JowiHue.UPNP+_Closure$__._Lambda$__R0-1(System.Object) at System.Threading.TimerQueueTimer.CallCallbackInContext(Syste m.Object) at System.Threading.ExecutionContext.RunInternal(System.Threadi ng.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers() at System.Threading.TimerQueue.AppDomainTimerCallback()


    + System

    - Provider

    [ Name] Application Error

    - EventID 1000

    [ Qualifiers] 0

    Level 2

    Task 100

    Keywords 0x80000000000000

    - TimeCreated

    [ SystemTime] 2017-07-07T12:42:29.969949000Z

    EventRecordID 41775

    Channel Application

    Computer HAPC-PC

    Security


    - EventData

    HSPI_JowiHue.exe
    1.1.2.9
    593e6de1
    mscorlib.ni.dll
    4.6.1648.0
    58e3fad3
    c0000005
    003d0ea2
    154c
    01d2f703a7da75d7
    C:\Program Files (x86)\HomeSeer HS3\HSPI_JowiHue.exe
    C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\a8ad 9c1eb84ee05773b04b298573fa35\mscorlib.ni.dll
    dbd2dbdc-5664-477e-b5b8-7ff62430b491


    I can't work out if it's a problem with HS3 or with the Hue plugin.

    K.

  • #2
    Have you tried disabling the HUE plugin and restarting Homeseer?
    HomeSeer Version: HS3 Pro Edition 3.0.0.500
    Operating System: Microsoft Windows 10 Pro - Work Station

    Enabled Plug-Ins:
    2.1.0.119: AmbientWeather | 3.0.21.0: BLLock | 2.0.24.0: BLUPS | 1.3.6.0: Device History | 3.0.0.56: EasyTrigger | 3.1.0.7: MeiHarmonyHub | 3.0.6681.34300: UltraCID3 | 3.0.6644.26753: UltraLog3 | 3.0.6554.33094: UltraMon3 | 3.0.0.91: weatherXML | 3.0.1.245: Z-Wave | 3.0.51: HS Touch Designer | 3.0.0.40 Z-Seer+

    Comment


    • #3
      I've tried restarting the PC, HS and the plugin to see if there's any effect and as yet not anything I can see.

      Strangely it seems to happen once every 24 hours or so when there's nothing really happening at all other than normal repetitive tasks. But it seems fairly random really.

      Most of the time it all looks and acts completely as normal.

      K.

      Comment


      • #4
        K.

        Your issue seems to be more or less the same as posted in this thread https://forums.homeseer.com/showthread.php?t=189887. HS3 closes for some reason and the plugin gets the signal to close also, but somehow it does not handle all open processes. It should just close, but it throws an error. It happens only when disabled on the manage plugins place, or HS3 is closed.

        It seems to me that you and facke02 have a similar issue, HS3 just stops. Maybe, like I asked in the other thread you have the latest update on Win10 and are using HSEntry?

        Wim
        -- Wim

        Plugins:RFXCOM, HSTouch Server, Squeezebox, BLGData, Restart, Jon00's Perfmon and Network monitor, WeatherXML, BLBackup, TenScripting, BC4, Pushover, PHLocation, JowiHue, Zwave, Sonos
        650 devices ---- 336 events ----- 40 scripts

        Comment


        • #5
          It's on a more or less dedicated Win10 Pro box that auto-updates so it should be on the latest Win10 public release, no betas or anything like that as since it runs HS I want it as stable as possible.

          And it runs very little aside from HS, bare minimum really.

          I am not aware of HSEntry being there, I don't even know what that is so I'd guess it's not there if it's a plugin.

          K.

          Comment


          • #6
            K.

            If you are running HS3 Pro, HsEntry is part of the homeseer system, not a separate plugin. You can find if it is active in the settings page of HS3?

            Wim
            -- Wim

            Plugins:RFXCOM, HSTouch Server, Squeezebox, BLGData, Restart, Jon00's Perfmon and Network monitor, WeatherXML, BLBackup, TenScripting, BC4, Pushover, PHLocation, JowiHue, Zwave, Sonos
            650 devices ---- 336 events ----- 40 scripts

            Comment


            • #7
              No, it is inactive and has been for at least a year or so I imagine since I've not looked at that page in an age.

              K.

              Comment


              • #8
                Ok, I will try to find the reason why the plugin errors on exit. But this is triggered by HS3. I don't know why HS3 is going down in this case though.

                Thanks,

                Wim
                -- Wim

                Plugins:RFXCOM, HSTouch Server, Squeezebox, BLGData, Restart, Jon00's Perfmon and Network monitor, WeatherXML, BLBackup, TenScripting, BC4, Pushover, PHLocation, JowiHue, Zwave, Sonos
                650 devices ---- 336 events ----- 40 scripts

                Comment


                • #9
                  Hi Wim,

                  Sorry was away last night but, it happened yesterday after a full restart of pretty much anything I could restart.

                  Also happened tonight also.

                  I can't explain it as it seems to be happening on a cycle but for the life of me I cannot see what could be causing it.

                  K.

                  Comment


                  • #10
                    Hi Wim,

                    On a hunch I've reinstalled.net as I have a weird feeling about it, will let you know if it fixes it.

                    K.

                    Comment


                    • #11
                      Ok, I hope this helps?

                      Wim
                      -- Wim

                      Plugins:RFXCOM, HSTouch Server, Squeezebox, BLGData, Restart, Jon00's Perfmon and Network monitor, WeatherXML, BLBackup, TenScripting, BC4, Pushover, PHLocation, JowiHue, Zwave, Sonos
                      650 devices ---- 336 events ----- 40 scripts

                      Comment


                      • #12
                        Nope.

                        Although I have gathered more info on the reported errors as follows:

                        Error 1:

                        Faulting application name: HS3.exe, version: 3.0.0.318, time stamp: 0x58e6a9d9
                        Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x58256ca0
                        Exception code: 0xc0000005
                        Fault offset: 0x00058833
                        Faulting process id: 0x1a28
                        Faulting application start time: 0x01d2f9aa9d089c41
                        Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HS3.exe
                        Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
                        Report Id: 58be0193-b2af-4746-a88f-97fdd8d7eebd
                        Faulting package full name:
                        Faulting package-relative application ID:

                        Error 2:

                        Application: HSPI_JowiHue.exe
                        Framework Version: v4.0.30319
                        Description: The process was terminated due to an unhandled exception.
                        Exception Info: System.NullReferenceException
                        at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(System.Runtime.Remoting.Messa ging.IMessage)
                        at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Syst em.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
                        at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String)
                        at HSPI_JowiHue.utils.Log(System.String, LogLevel)
                        at HSPI_JowiHue.UPNP.Bridgescan()
                        at HSPI_JowiHue.UPNP+_Closure$__._Lambda$__R0-1(System.Object)
                        at System.Threading.TimerQueueTimer.CallCallbackInContext(Syste m.Object)
                        at System.Threading.ExecutionContext.RunInternal(System.Threadi ng.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
                        at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object, Boolean)
                        at System.Threading.TimerQueueTimer.CallCallback()
                        at System.Threading.TimerQueueTimer.Fire()
                        at System.Threading.TimerQueue.FireNextTimers()
                        at System.Threading.TimerQueue.AppDomainTimerCallback()

                        Error 3:

                        Faulting application name: HSPI_JowiHue.exe, version: 1.1.2.9, time stamp: 0x593e6de1
                        Faulting module name: mscorlib.ni.dll, version: 4.7.2053.0, time stamp: 0x58fa6bd6
                        Exception code: 0xc0000005
                        Fault offset: 0x003ede22
                        Faulting process id: 0x2958
                        Faulting application start time: 0x01d2fa39a0c0a34a
                        Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_JowiHue.exe
                        Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\c638 57e47a917e45ff227d52324d08a1\mscorlib.ni.dll
                        Report Id: d0f643bf-3659-4433-b6f5-a17982be51c3
                        Faulting package full name:
                        Faulting package-relative application ID:

                        Error 4:

                        Faulting application name: HSPI_Arduino.exe, version: 1.0.0.142, time stamp: 0x590b8cce
                        Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327ae2
                        Exception code: 0xe0434352
                        Fault offset: 0x000da9f2
                        Faulting process id: 0x1a50
                        Faulting application start time: 0x01d2fa2247ea7573
                        Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_Arduino.exe
                        Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
                        Report Id: d3bf6e9b-1e5c-4d9e-b804-bca25ed54efc
                        Faulting package full name:
                        Faulting package-relative application ID:

                        It makes no sense to me at all but hope it helps.

                        K.

                        Comment


                        • #13
                          Same again today, HS fell over with the errors below.

                          K.

                          Error 1:

                          Faulting application name: HS3.exe, version: 3.0.0.318, time stamp: 0x58e6a9d9
                          Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x58256ca0
                          Exception code: 0xc0000005
                          Fault offset: 0x00058833
                          Faulting process id: 0x30dc
                          Faulting application start time: 0x01d2fb36eecd28c4
                          Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HS3.exe
                          Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
                          Report Id: 364618d5-7b1b-4151-b1a7-55426d364166
                          Faulting package full name:
                          Faulting package-relative application ID

                          Error 2:

                          Application: HSPI_JowiHue.exe
                          Framework Version: v4.0.30319
                          Description: The process was terminated due to an unhandled exception.
                          Exception Info: System.NullReferenceException
                          at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(System.Runtime.Remoting.Messa ging.IMessage)
                          at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Syst em.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
                          at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String)
                          at HSPI_JowiHue.utils.Log(System.String, LogLevel)
                          at HSPI_JowiHue.UPNP.Bridgescan()
                          at HSPI_JowiHue.UPNP+_Closure$__._Lambda$__R0-1(System.Object)
                          at System.Threading.TimerQueueTimer.CallCallbackInContext(Syste m.Object)
                          at System.Threading.ExecutionContext.RunInternal(System.Threadi ng.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
                          at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object, Boolean)
                          at System.Threading.TimerQueueTimer.CallCallback()
                          at System.Threading.TimerQueueTimer.Fire()
                          at System.Threading.TimerQueue.FireNextTimers()
                          at System.Threading.TimerQueue.AppDomainTimerCallback()

                          Error 3:

                          Faulting application name: HSPI_JowiHue.exe, version: 1.1.2.9, time stamp: 0x593e6de1
                          Faulting module name: mscorlib.ni.dll, version: 4.7.2053.0, time stamp: 0x58fa6bd6
                          Exception code: 0xc0000005
                          Fault offset: 0x003ede22
                          Faulting process id: 0x1c3c
                          Faulting application start time: 0x01d2fbc1e705f664
                          Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_JowiHue.exe
                          Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\c638 57e47a917e45ff227d52324d08a1\mscorlib.ni.dll
                          Report Id: 31578f8c-0152-43a8-b6c2-fb992033db34
                          Faulting package full name:
                          Faulting package-relative application ID:

                          Comment


                          • #14
                            Have you disabled the Hue plugin and then run Homeseer for a few days to confirm it is actually the plugin?
                            Jon

                            Comment


                            • #15
                              Nope I haven't done that.

                              I'll give it a go though as if I do that it'll either fall over or not about the same time as it's been the same time every day +/- 3-5 hours.

                              And I thought it might be a routine or something but nothing runs in the period it crashes out. I have checked that, several times.

                              The only thing that it might be and I've not any way to tell is the Hue bridge looking to update round that time and doing something odd. A long shot, I know but I'm clutching at straws.

                              It's weird s I can't see any errors at all.

                              K.

                              Comment

                              Working...
                              X