Nodelink Wont' run after 0.10.4 update

[apostolakisl]

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
 

[io_guy]

Working fine here with OTA update on a Pi.  How are you trying to run it?

[apostolakisl]

16 minutes ago, io_guy said:

Working fine here with OTA update on a Pi.  How are you trying to run it?

On a win10 pc.  Same one running the previous version.

[apostolakisl]

19 minutes ago, io_guy said:

Working fine here with OTA update on a Pi.  How are you trying to run it?

tried to put .3 version back on.  It won't run either.  It starts to run, then when it seems like it is done booting up, I get a similar error.  The window closes so fast I can't get it.

[apostolakisl]

@io_guy

But the 0.9.36 runs.

[io_guy]

Dunno what to say, doesn't seem to be a NodeLink issue if .3 won't work either.  I can run it here fine on Win10.

0.9.36 uses .NET Framework.  Completely different.  0.10.X uses .NET Core 3.

Try moving your config file to see if a fresh start dies too.

[apostolakisl]

2 minutes ago, io_guy said:

Dunno what to say, doesn't seem to be a NodeLink issue if .3 won't work either.  I can run it here fine on Win10.

0.9.36 uses .NET Framework.  Completely different.  0.10.X uses .NET Core 3.

Try moving your config file to see if a fresh start dies too.

I did move the config file to a freshly unzipped .3 version.  That is what almost runs and then crashes once it seems like it is up.

[io_guy]

For .3 to just start crashing all of a sudden is a Windows problem, not NodeLink. 

Are you running the dll or using the .exe from the original zip?

[apostolakisl]

.exe file

Tried uninstalling .net core and reinstalling, still won't run

Be odd to start having a windows problem precisely at the same time as I update nodelink.  Everything else is ok.  Tried rebooting too.

[io_guy]

Try dotnet NodeLink.dll from a command line.

[apostolakisl]

1 minute ago, io_guy said:

Try dotnet NodeLink.dll from a command line.

Not sure what you mean.  Tried this.

 

C:\Users\Lou>dotnet NodeLink.dll
  It was not possible to find any installed .NET Core SDKs
  Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:
      https://aka.ms/dotnet-download

[io_guy]

I don't know what you have going on.  I do it here without issue. 

You need the .NET Core 3 runtime installed.  After that your ENV should allow calling dotnet from a command line.  

And you'll have to execute it from the NodeLink folder or it won't find NodeLink.dll

[apostolakisl]

11 minutes ago, io_guy said:

I don't know what you have going on.  I do it here without issue. 

You need the .NET Core 3 runtime installed.  After that your ENV should allow calling dotnet from a command line.  

I tried putting on another win10 computer and I get the same problem.

[apostolakisl]

14 minutes ago, io_guy said:

I don't know what you have going on.  I do it here without issue. 

You need the .NET Core 3 runtime installed.  After that your ENV should allow calling dotnet from a command line.  

https://dotnet.microsoft.com/download/dotnet-core/3.0

From that webpage, I installed .net core runtime 3.0.1 windows x64     

It is on the right of the page scrolled down just a bit.

[io_guy]

Try 3.0.0 to see if it makes a difference.  That's what I build against.  

It's supposed to be backwards compatible but you never know. 

[apostolakisl]

5 minutes ago, io_guy said:

Try 3.0.0 to see if it makes a difference.  That's what I build against.  

It's supposed to be backwards compatible but you never know. 

Nope.  Same problem.  Uninstalled the 3.0.1 then downloaded and installed 3.0.0.  This is on a second PC.  So two PC's giving same error.

[io_guy]

Just installed 3.0.1 Runtime on a clean Win10 laptop.  Downloaded NodeLink.zip.

Ran dotnet NodeLink.dll without issue and ran the .exe directly without issue.  

Don't know what to tell you.

[apostolakisl]

2 hours ago, io_guy said:

Just installed 3.0.1 Runtime on a clean Win10 laptop.  Downloaded NodeLink.zip.

Ran dotnet NodeLink.dll without issue and ran the .exe directly without issue.  

Don't know what to tell you.'

This appears to have something to do with windows firewall.  I was able to open by opening a power shell in the folder and executing "dotnet NodeLink.dll"

Windows then gave me a popup warning about blocking access.  I turned the filter off and it runs.

I don't know what has changed here for this to happen, perhaps my computer has a security update that yours does not.  Below is the power shell.  The first attempt you see didn't work.  The second time I turned "controlled folder access" off from windows security/virus and threat prevention.  It appears that this feature is now shut off for the whole computer, not just this application, so I don't plan on leaving it this way.

Also, it is not updating to 0.10.4    

2019-11-20 00:39:20 - Auto-Update: Checking for program update...
2019-11-20 00:39:21 - Auto-Update: New version found (0.10.4), downloading...
2019-11-20 00:39:21 - Auto-Update: Error updating file: An exception occurred during a WebClient request.

As it turns out, all the time I thought I was running 0.10.4, I was actually running .3.  Not sure if the download resulted in some mixing and matching of files that didn't go together?  I did a download from your website of a fresh version.

PS C:\Users\apostolakisl\Desktop\NodeLink (1)> dotnet NodeLink.dll
Unhandled exception. System.UnauthorizedAccessException: Access to the path 'C:\Users\apostolakisl\Desktop\NodeLink (1)\config.xml' is denied.
   at System.IO.FileSystem.CopyFile(String sourceFullPath, String destFullPath, Boolean overwrite)
   at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite)
   at NodeLink.xmlConfig.LoadXML()
   at NodeLink.MainModule.Main()
PS C:\Users\apostolakisl\Desktop\NodeLink (1)> dotnet NodeLink.dll
2019-11-20 00:20:10 - ISY NodeLink Server v0.10.3 started
2019-11-20 00:20:10 - OS: Microsoft Windows NT 10.0.18362.0
2019-11-20 00:20:10 - Windows Auth Error: Permission denied opening port (8090)
2019-11-20 00:20:10 - Windows Auth Error: Either run as Administrator or from elevated command prompt run "netsh http add urlacl url=http://+:8090/ user=Everyone"
2019-11-20 00:20:12 - ISY resolved to 192.168.1.9 (5.0.16)
2019-11-20 00:20:12 - ISY Node Server config detected (profile 1)
2019-11-20 00:20:13 - ISY Warning: Duplicate node names exist on the ISY (Ellens S8)
2019-11-20 00:20:13 - ISY Warning: Duplicate node names exist on the ISY (Lous S8)
2019-11-20 00:20:14 - DSC: Repeater started on port 4025 [dsc1]
2019-11-20 00:20:14 - DSC: Connected to 192.168.2.141 [dsc1]
2019-11-20 00:20:14 - DSC Error: Data Arrival Init - An existing connection was forcibly closed by the remote host. [dsc1]
2019-11-20 00:20:17 - Auto-Update: Error updating file: An exception occurred during a WebClient request.
2019-11-20 00:20:44 - DSC: Reconnecting To Server [dsc1]
2019-11-20 00:20:44 - DSC: Connected to 192.168.2.141 [dsc1]
2019-11-20 00:20:44 - DSC Error: Data Arrival Init - An existing connection was forcibly closed by the remote host. [dsc1]
2019-11-20 00:21:14 - DSC: Reconnecting To Server [dsc1]
2019-11-20 00:21:14 - DSC: Connected to 192.168.2.141 [dsc1]
2019-11-20 00:21:14 - DSC Error: Data Arrival Init - An existing connection was forcibly closed by the remote host. [dsc1]
2019-11-20 00:21:44 - DSC: Reconnecting To Server [dsc1]
2019-11-20 00:21:44 - DSC: Connected to 192.168.2.141 [dsc1]
2019-11-20 00:21:44 - DSC Error: Data Arrival Init - An existing connection was forcibly closed by the remote host. [dsc1]
2019-11-20 00:22:14 - DSC: Reconnecting To Server [dsc1]
2019-11-20 00:22:14 - DSC: Connected to 192.168.2.141 [dsc1]
2019-11-20 00:22:14 - DSC Error: Data Arrival Init - An existing connection was forcibly closed by the remote host. [dsc1]

 

[io_guy]

The auth error:

Windows Auth Error: Either run as Administrator or from elevated command prompt run "netsh http add urlacl url=http://+:8090/ user=Everyone"

Is nothing new and has been there for about 20 NodeLink versions including older 0.9.x versions.  You do as it asks, either run the command or run NodeLink as admin.  

Running as admin would likely also resolve your file permission error, maybe that's what's changed in your setup (no longer running it as admin).  

[apostolakisl]

2 hours ago, io_guy said:

The auth error:

Windows Auth Error: Either run as Administrator or from elevated command prompt run "netsh http add urlacl url=http://+:8090/ user=Everyone"

Is nothing new and has been there for about 20 NodeLink versions including older 0.9.x versions.  You do as it asks, either run the command or run NodeLink as admin.  

Running as admin would likely also resolve your file permission error, maybe that's what's changed in your setup (no longer running it as admin).  

That error wasn't an issue.  I have been running as admin.  However, running it in a power shell from within a folder . . . well I don't know how to make that run as admin, so I got that error.

The problem appears to be related to failed downloading via auto-update.  It looks like there was a mismatch of the dll and exe file after the auto-update.  After getting it to run in a power shell window, I discovered that despite having auto-updated, it was still .3 version.  And the .3 version running at that time reported a failed auto-update at boot.  What fixed it was completely emptying the nodelink folder and unzipping a fresh copy from your website, then moving the config file into that folder.  I have not had any of the 0.10.x versions do an auto-update and succeed.  

[io_guy]

That's why I asked you if you were running the exe.  It doesn't update, you'd need a new zip.  

I'll likely remove the zip and exe all together since it adds confusion.  

[apostolakisl]

46 minutes ago, io_guy said:

That's why I asked you if you were running the exe.  It doesn't update, you'd need a new zip.  

I'll likely remove the zip and exe all together since it adds confusion.  

I'm confused.  How the heck does this work?  Is the .exe not needed?  If there were no .exe file, then how do you run the program?  From command line only?  I have it set to run on boot, and, I suppose, that would require some sort of script to execute a command line.  Never done it.

[io_guy]

The exe is Net Core is just a wrapper to "dotnet NodeLink.dll".  It's not used in other OS'.

http://automationshack.com/Files/NodeLink.cmd

Just put that in your NodeLink dir and use it to start.  I'll release a new version tonight that should fix restarts in Windows.

[apostolakisl]

34 minutes ago, io_guy said:

The exe is Net Core is just a wrapper to "dotnet NodeLink.dll".  It's not used in other OS'.

http://automationshack.com/Files/NodeLink.cmd

Just put that in your NodeLink dir and use it to start.  I'll release a new version tonight that should fix restarts in Windows.

I just created a bat file to execute nodelink.  But I don't know how to make it run as administrator.  Running the bat file as admin I don't think does that.

[io_guy]