I have been fighting this for a week. I have a perfectly functional system running under windows 10 on a stand alone SuperMicro server
I was going to do some maintenance on the server so I moved HS# back to a VM running Windows 10. I move HS3 by shutting it down and copying the entire directory structure to the backup machine. This VM is running under Hyper-v on a Windows Server 2012r2 machine. I have used this same VM in the past and was able to freely move the HS system back and forth between the physical machine and VM. I have done this between these same two machines dozens of times in the past, without issue. The last time I did this was about June last year.
Now when I try to bring up HS3 on the VM, I get 1-3 plug-ins that fail to initialize. It is not always the same plug-ins, but at least 1 fails to initialize. In developer mode I captured this for the Arduino plug-in
I checked permissions, disabled UAC and disabled the firewall, always with the same results.
I built a fresh VM, reinstalled HS3 and all of the plug-ins and tried again with the same result.
I decided I would try to run it under FireDaemon Pro on the Windows Server 2012r2 and the results are the same. Again I installed HS3, all plug-ins, double checked UAC settings, permissions, etc. Then I started HS bare, without my data, configurations and scripts. All plug-ins loaded fine.
As a last resort I tried to bring it up on the Server 2012 while logged in as a user - same results.
I restored my original machine from the same files as I was trying to run on the VMs and server and it runs fine on it (Windows 10 stand alone).
I am running fine on the original server, but have exhausted everything I can think of.
Any ideas?
I was going to do some maintenance on the server so I moved HS# back to a VM running Windows 10. I move HS3 by shutting it down and copying the entire directory structure to the backup machine. This VM is running under Hyper-v on a Windows Server 2012r2 machine. I have used this same VM in the past and was able to freely move the HS system back and forth between the physical machine and VM. I have done this between these same two machines dozens of times in the past, without issue. The last time I did this was about June last year.
Now when I try to bring up HS3 on the VM, I get 1-3 plug-ins that fail to initialize. It is not always the same plug-ins, but at least 1 fails to initialize. In developer mode I captured this for the Arduino plug-in
Code:
Unhandled Exception: System.TypeInitializationException: The type initializer fo r 'HSPI_Arduino.Util' threw an exception. ---> System.Net.Sockets.SocketExceptio n: Only one usage of each socket address (protocol/network address/port) is norm ally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.UdpClient..ctor(Int32 port, AddressFamily family) at HSPI_Arduino.UDPboard..ctor() at HSPI_Arduino.Util..cctor() --- End of inner exception stack trace --- at HSPI_Arduino.Main.Main()
I built a fresh VM, reinstalled HS3 and all of the plug-ins and tried again with the same result.
I decided I would try to run it under FireDaemon Pro on the Windows Server 2012r2 and the results are the same. Again I installed HS3, all plug-ins, double checked UAC settings, permissions, etc. Then I started HS bare, without my data, configurations and scripts. All plug-ins loaded fine.
As a last resort I tried to bring it up on the Server 2012 while logged in as a user - same results.
I restored my original machine from the same files as I was trying to run on the VMs and server and it runs fine on it (Windows 10 stand alone).
I am running fine on the original server, but have exhausted everything I can think of.
Any ideas?
Comment