I've been running the Windows Server version as a service for a while now on three different systems. Generally all has been good.
Yesterday one of the guys here removed the service to update to the latest version and now it wont start.
On install it installs the service and then fails with a "timeout" message, if the service is started manually it starts and then stops immediately.
There is nothing in the event log to point to the issue.
Rebooted etc, makes no difference.
Can run VH server as application fine, it's just the service that's not working.
OS is Windows Server 2012 R2
Any ideas??
.
Sounds like it might be a crash, i tried installing the service on win2012r2 here and it was fine so im not sure.. if it did crash, windows will write an entry in the Event Viewer -> Windows Logs -> Application. With an Error icon. Can you take a look if it shows something there. Nothing much has changed in the windows server for a few months...
When starting the message is.
When starting the message is..... "Timeout waiting the VirtualHere USB Server service to start"
The VirtualHere USB Server Application Log has....
The description for Event ID 1 from source VirtualHere USB Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
>>> Starting VirtualHere USB Server v3.3.2 (Built: May 14 2017, 13:15:14)<<<
The Application Event Log has....
Event ID 1000
Faulting application name: vhusbdwin64.exe, version: 3.3.2.0, time stamp: 0x5917cbcb
Faulting module name: ntdll.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000374
Fault offset: 0x00000000000f1b70
Faulting process id: 0xde4
Faulting application start time: 0x01d2d4e98df64719
Faulting application path: C:\Program Files\VirtualHere\vhusbdwin64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: cbc43564-40dc-11e7-80da-b083fe34f803
Faulting package full name:
Faulting package-relative application ID:
There seems to be no reason why this has started to happen
.
Try this
vhusbdwin64.exe -bto remove the service then try
vhusbdwin64.exe -uto remove any server drivers then try
vhusbdwin64.exe -bto install the service again
Still get the application crash
Removing the drivers and reinstalling hasn't made a change.
Tried a reboot after the -u, didnt help.
Running in application mode works ok, it's just the service mode where it's not running - crashes on startup.
Any other ideas? I'd reinstall the OS, but it's running another critical application which is a real pain to install. I guess I could move it to another box, but this would create other issues.
.
I think you will have to use it as an application for the time being...
looking on the internet people say to try
sfc.exe /scannow.
The work around for this is