Announcement

Collapse
No announcement yet.

Jon00 Event Viewer & Documenter for Homeseer 4

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

  • avpman
    replied
    Originally posted by jon00 View Post
    I would also recommend you update to Mono 6 first.
    Thanks! Mono JIT compiler version 6.12.0.122 fixed it.

    Leave a comment:


  • jon00
    replied
    I would also recommend you update to Mono 6 first.

    Leave a comment:


  • zwolfpack
    replied
    To verify you've made the vbnc patch correctly,
    at the Linux command line run command: vbnc

    Look for a line starting with 'Copyright'. If it indicates "Copyright (C) Microsoft Corporation" you've done it correctly. If it says something like "Copyright (C) 2004-2010 Rolf Bjarne Kvinge" ... you haven't.

    My recommendation for implementing the patch is the following command
    Code:
    cd /usr/bin && sudo install -p vbc vbnc
    As it seems less prone to fat-finger than opening up a text editor in a potentially unfamiliar environment...

    Leave a comment:


  • avpman
    replied
    Originally posted by jon00 View Post
    You will probably need to upgrade your Linux PC to use vbc rather than vbnc. See post 11.
    I made the change:

    #!/bin/sh
    exec /usr/bin/mono --debug $MONO_OPTIONS /usr/lib/mono/4.5/vbc.exe "$@"

    Then rebooted and I still get the error below (which is weird because it's still referring to VBNC) :
    (FWIW MONO Version is: Mono JIT compiler version 5.18.0.240 (Debian 5.18.0.240+dfsg-3 Sat Apr 20 05:16:08 UTC 2019)



    Click image for larger version

Name:	jonEvents2.JPG
Views:	140
Size:	31.4 KB
ID:	1474688

    Leave a comment:


  • jon00
    replied
    You will probably need to upgrade your Linux PC to use vbc rather than vbnc. See post 11.

    Leave a comment:


  • avpman
    replied
    Errors on HS4 Linux using the HS4 version of the script. Please see below:
    Thanks!

    Click image for larger version  Name:	jonEvents.JPG Views:	0 Size:	34.4 KB ID:	1474670

    Leave a comment:


  • jon00
    replied
    V1.0.1 has been released for HS4.

    Changes since 1.0.0:

    Corrected bug in ‘Do Not Log – Ascending’ filter.
    Added method to find corrupt events which cannot be processed by the viewer.

    Leave a comment:


  • jon00
    replied
    You can still access the Global Variables via the old HS3 legacy pages. Just type /globals in your HS web browser. For easy access to Legacy links etc, you can download Jon00 Links for HS4.

    Leave a comment:


  • flaplante
    replied
    It seems I am missing something. I can see all the events and their properties, but I cannot seem to get a list of global variables with their current values, or for that matter just see the current value of a single global. Was easy to see in HS3 as there was a tab for counters, timers and globals.

    Is there an other utility somewhere that wil do what I am looking for? Surely I am not the only HS4 user that want to see that information.

    Leave a comment:


  • flaplante
    replied
    That seems to have done the trick! Thanks for the help.

    Leave a comment:


  • jon00
    replied
    You need to SSH/WinSCP into your SEL and navigate to the usr/bin folder. In that folder is the file vbnc. Open vbnc in an editor and change vnbc.exe to vbc.exe

    Leave a comment:


  • flaplante
    replied
    I am having same problem. Installed Event Viewer in hopes of seeing globals values. After completing install on my Hometroller SEL (linux), both EventViewer.html and test.aspx yielded much the same result - failure. Error report for eventviewer.html:

    System.Web.Compilation.CompilationException

    VBNC99999: Unexpected error: Failed to resolve assembly: 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
    at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name, Mono.Cecil.ReaderParameters parameters) [0x00148] in <c0698b6ec8e1496688e9794985d298d3>:0 at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00008] in <c0698b6ec8e1496688e9794985d298d3>:0 at Mono.Cecil.DefaultAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00031] in <c0698b6ec8e1496688e9794985d298d3>:0 at vbnc.CecilHelper.FindDefinition (Mono.Cecil.AssemblyNameReference name) [0x0000b] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.CecilHelper.FindDefinition (Mono.Cecil.TypeReference type) [0x00089] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.Helper.CompareType (Mono.Cecil.TypeReference t1, Mono.Cecil.TypeReference t2) [0x006e8] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.CecilHelper.IsDefined (Mono.Collections.Generic.Collection`1[T] CustomAttributes, Mono.Cecil.TypeReference Type) [0x00043] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.Helper.IsModule (vbnc.Compiler Compiler, Mono.Cecil.TypeReference type) [0x00096] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.TypeManager.LoadType (Mono.Cecil.TypeDefinition Type) [0x0003a] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.TypeManager.LoadReferencedTypes () [0x00092] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.TypeManager.LoadReferenced () [0x000ec] in <57c73136269a4cb1a41c733d61a169cf>:0 at vbnc.Compiler.Compile () [0x00258] in <57c73136269a4cb1a41c733d61a169cf>:0
    Compilation took 00:00:01.1558960


    I have searched the homeseer folder and its subfolders but cannot find vbnc.

    Leave a comment:


  • akkie71
    replied
    Thanks!
    test.aspx didn't work either. I searched through the board with your tip and changed my vbnc file. Now it points to vbc.exe. Issue solved.
    I'm gonna try your Viewer & Documenter for HS4 now.

    Leave a comment:


  • jon00
    replied
    What happens if you call /test.aspx on your web browser?

    Leave a comment:


  • akkie71
    replied
    The complete error report is below. Any clues in here, or maybe the error is in HS4 itself?
    Thanks,
    Arjan

    ​​​​​​Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error.

    Details: VBNC99999: Unexpected error: Failed to resolve assembly: 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
    at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name, Mono.Cecil.ReaderParameters parameters) [0x00148] in <d09141d3f5fa48279a3587e2a3dc5812>:0 at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00008] in <d09141d3f5fa48279a3587e2a3dc5812>:0 at Mono.Cecil.DefaultAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00031] in <d09141d3f5fa48279a3587e2a3dc5812>:0 at vbnc.CecilHelper.FindDefinition (Mono.Cecil.AssemblyNameReference name) [0x0000b] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.CecilHelper.FindDefinition (Mono.Cecil.TypeReference type) [0x00089] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.Helper.CompareType (Mono.Cecil.TypeReference t1, Mono.Cecil.TypeReference t2) [0x006e8] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.CecilHelper.IsDefined (Mono.Collections.Generic.Collection`1[T] CustomAttributes, Mono.Cecil.TypeReference Type) [0x00043] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.Helper.IsModule (vbnc.Compiler Compiler, Mono.Cecil.TypeReference type) [0x00096] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.TypeManager.LoadType (Mono.Cecil.TypeDefinition Type) [0x0003a] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.TypeManager.LoadReferencedTypes () [0x00092] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.TypeManager.LoadReferenced () [0x000ec] in <c13ea2849dd446369a48bc0f51e3a64b>:0 at vbnc.Compiler.Compile () [0x00258] in <c13ea2849dd446369a48bc0f51e3a64b>:0
    Compilation took 00:00:01.1148590

    Error origin: Compiler

    Error source file: ~/Global.asax

    Leave a comment:

Working...
X