Announcement

Collapse
No announcement yet.

ASP.Net page: Could not load file or assembly Errors

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

    ASP.Net page: Could not load file or assembly Errors

    Can someone explain these errors and possible remediation to resolve?
    Code:
     
    Sep-16 06:57:12 Error ASP.Net page: Could not load file or assembly 'HomeSeerUtil, Version=3.0.0.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
    Sep-16 06:57:11 Error ASP.Net page: Could not load file or assembly 'HomeSeerUtil, Version=3.0.0.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
    Sep-16 06:57:11 Error ASP.Net page: Could not load file or assembly 'HomeSeerUtil, Version=3.0.0.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
    Current Date/Time: 2020-09-16 07:01:27
    HomeSeer Version: HS3 Standard Edition 3.0.0.548
    Operating System: Microsoft Windows 10 Home - Work Station
    System Uptime: 0 Days 0 Hours 4 Minutes 16 Seconds
    IP Address: 192.168.x.x
    Number of Devices: 204
    Number of Events: 29
    Available Threads: 1023
    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
    3.0.0.20: EnvCan
    1.2019.211.1740: MyQ
    1.0.0.7: Restart
    3.0.2.0: Z-Wave

    #2
    Either:

    https://forums.homeseer.com/forum/ho...ervice-or-task

    Or:

    Use startup delayer from R2 Studios (free) to start HS3.
    Jon

    Comment


      #3
      Thanks for the link but had already investigated but reread and did go back and tested Run as Admin and the error is not there.

      I have used UAC Pass for years instead of startup delayer to autostart. These errors recently appeared so something in one of the Microsoft updates has changed something or a permission. I will investigate startup delayer to see if it changes the behavior. Thanks.

      Comment

      Working...
      X