Announcement

Collapse
No announcement yet.

Windows Event Viewer Error with 1.3.7.3

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

    Windows Event Viewer Error with 1.3.7.3

    On 4/2/19 I started to get some errors listed in the Windows Event Viewer (see below). These errors cause HS3.exe to crash (I have it set to restart on errors). It has happened 12 times since 4/2/19 but I see no pattern of when it happens. I know that on some of the days it has crashed HS3 has been running for days with no one accessing the web interface or making any changes to any configuration or running any device history reports or graphs.

    Since it can be up to a week between crashes I have not turned on any debug logging yet but can if that is the next step. I'm glad to provide any additional information or testing, just point me in the right direction to help.

    Thanks
    John

    SYSTEM CONFIG:
    Current Date/Time: 6/13/2019 12:44:13 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.534
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 0 Days 19 Hours 7 Minutes 27 Seconds
    IP Address: 192.168.0.22
    Number of Devices: 401
    Number of Events: 44
    Available Threads: 400
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed: Windows Defender
    In Virtual Machine: No MFG: intel corporation
    Enabled Plug-Ins
    2.0.59.0: BLBackup
    2.0.24.0: BLUPS
    1.3.7.3: Device History
    3.0.0.65: EasyTrigger
    3.0.0.14: NetCAM
    3.0.1.15: weatherXML
    3.0.1.252: Z-Wave

    EVENT VIEWER ERRORS:
    Log Name: Application
    Source: .NET Runtime
    Date: 6/12/2019 5:32:11 PM
    Event ID: 1026
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: BlueRiver
    Description:
    Application: HSPI_SKWARE_DEVICE_HISTORY.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.ClearINISection(System.String, System.String)
    at HSPI_SKWARE_DEVICE_HISTORY.PluginSettings.Save()
    at HSPI_SKWARE_DEVICE_HISTORY.PluginSettings.Finalize()

    ———————————————————
    Log Name: Application
    Source: Application Error
    Date: 6/12/2019 5:32:12 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: BlueRiver
    Description:
    Faulting application name: HSPI_SKWARE_DEVICE_HISTORY.exe, version: 1.3.7.3, time stamp: 0x5ca546f8
    Faulting module name: mscorlib.ni.dll, version: 4.7.3416.0, time stamp: 0x5cabfb31
    Exception code: 0xc0000005
    Fault offset: 0x00435c72
    Faulting process id: 0x430
    Faulting application start time: 0x01d520abf4cf36d6
    Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_SKWARE_DEVICE_HISTORY.exe
    Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\a5a4 7e8e5e2880adecca43eb928673f1\mscorlib.ni.dll
    Report Id: f4261551-ee41-42b5-a1b0-e37fa38d7972
    Faulting package full name:
    Faulting package-relative application ID:


    HSPI_SKWARE_DEVICE_HISTORY.ini CONTENTS:
    [ChartParameters]
    331=1,True,3,2,2,*,*,,,1
    315=1,False,7,1,2,*,*,,,1
    212=2,False,7,1,2,*,*,,,1
    244=2,False,24,2,1,*,*,,,1
    325=2,True,7,2,2,*,*,,,1
    76=2,False,10,2,2,*,*,,,1
    182=1,False,6,2,1,*,*,,,1
    185=1,False,6,2,1,*,*,,,1
    108=2,False,7,2,2,*,*,,,1
    125=2,False,7,2,2,*,*,,,1
    228=2,False,7,2,2,*,*,,,1
    204=2,False,7,2,2,*,*,,,1
    75=2,False,7,2,3,*,*,,,1
    316=1,False,7,2,2,*,*,,,1
    61=2,False,30,2,2,*,*,,,1
    63=2,False,24,2,1,*,*,,,1
    [Favorites]
    dGVtcCAx={"PrimaryDevice":{"Ref":331,"Name":"Motion Temperature","Location1":"Bathroom","Location2":"1st Floor","HasRange":true,"Labels":{}},"Y1Devices":[{"Ref":331,"Name":"Motion Temperature","Location1":"Bathroom","Location2":"1st Floor","HasRange":true,"Labels":{}},{"Ref":212,"Name":"Tempe rature","Location1":"Family Room","Location2":"1st Floor","HasRange":true,"Labels":{}},{"Ref":39,"Name":"Motion Temperature","Location1":"Garage","Location2":"1st Floor","HasRange":true,"Labels":{}}],"Y2Devices":[],"StyleParameters":{"NameSuffix":"","DurationType":1,"Period Type":2,"Periods":1,"FromDate":"2019-03-22T00:00:00-06:00","ToDate":"2019-03-23T18:59:00.5409746-06:00","Style":1,"Style2":1,"ShowTitle":true,"UseMarkers":tr ue,"UseMarkers2":true,"Height":480,"Width":640,"DisplayHeigh t":480,"DisplayWidth":640,"RotateDegrees":0,"FontSize":10,"L ineWidth":1,"Title":"Motion Temperature Device Values Over Time","Y1Label":"Values","Y2Label":"","XLabel":"Date/Time","ShowLegend":true,"ValueType":1,"TransparentBG":false, "ImageBGColor":"White","ChartBGColor":"WhiteSmoke","AxisLine Color":"DimGray","TickMarkColor":"Gray","GridLineColor":"Gai nsboro","TextColor":"Black","Y1AxisMin":"Auto","Y1AxisMax":" Auto","Y2AxisMin":"Auto","Y2AxisMax":"Auto"}}
    [Options]
    MonitoredDevices=331,212,39,204,184,181,186,185,182,108,244, 125,236,325,323,228,373,168,377,220,78,75,76,177,174,175,63, 60,61,279,276,277,316,315,455
    LogLevelHS=4
    LogLevelFile=4
    Limit=365
    Version=1.3.7
    ValueTableHeight=0
    DefaultSortCol=CHANGE_DATE
    DefaultSortDir=1
    DefaultChartStyle=2
    ShowTitle=True
    ChartTitle=%DEVICENAME% Device Values Over Time
    DefaultMarkers=False
    DeviceCharts=True
    DefaultDurationType=2
    DefaultPeriods=7
    DefaultPeriodType=2
    ChartWidth=1280
    ChartHeight=960
    DisplayWidth=640
    DisplayHeight=480
    FontSize=10
    LineWidth=1
    DateVacuumed=12:00:00 AM

    #2
    I'll look into the fault info above, but I will probably need to catch this happening with TRACE logging enabled, unfortunately, so I can see what the faulting location and inputs were.

    Comment


      #3
      Using Microsoft's DebugDiag tool can also capture some good information about crashes that happen. This page has a great walkthrough; just substitute the plugin EXE for the "Cantabile" references. If you get a dump file, you can email to me at steve@skware.net.

      Comment


        #4
        Thanks Steve. I started getting some additional errors so I completely removed the plugin and data file and started fresh. Went fine for a week and then it crashed last night (same error). Trace file was not on. I turned it on today and will report back with the next crash.

        Do you have a link for the DebugDiag that you talked about? I have a look at it also.

        Edit: I searched and found the DebugDiag page you were talking about.

        Thanks
        John

        Comment

        Working...
        X