VM Pro 9.0 service keeps getting stuck on stopping

[MightyMrMatt]

Just set up a new IPO 500 9.0 system for a client, but we have run into an issue where the VM Pro service will terminate unexpectedly and get stuck in the Stopping state. In this state, Windows Server 2012 R2 can't restart the service. Power settings are set to never turn off, NIC is set to not power off, HDD never spins down, and no firewalls are present. Debug simply shows the service stops and starts again and there is no detailed event in the Event Viewer to point me in the right direction. Anyone have any ideas?

 

[rdoubrava]

It's in the R10 release notes.
I put a ticket in with Avaya 9.1.5 with VM Pro on a windows 2012 server hosted on VSphere 6.0.
Avaya said not supported and closed the ticket. (Long story shortened)

 

[janni78]

Of course they say that, the want the easy way out.
Wouldn't mention which ESXi it's on since it's irrelevant.
People ran applications on Hyper-V and VMware long before Avaya supported it, just because they haven't tested that specific version doesn't mean it won't work.

"Trying is the first step to failure..." - Homer

 

[MightyMrMatt]

The issue is not VMware as the service is now failing on the standalone desktop as well. Still getting stuck on 'Stopping'. I guess I will recomb the network to see if something is occasionally spamming ports.

 

[amriddle01]

Are you 100% sure it's licenced?

 

[MightyMrMatt]

Double-checked it. R8+ Preferred Edition License is valid as is the Advanced Edition license.

 

[MightyMrMatt]

Well, it certainly seems more stable on the standalone. The service is only crashing maybe once or twice a day and I have a batch program setup to force stop the service then restart it, which works occasionally. However, it is still getting stuck in a stopping state and never quite gets to a point for the system to use the batch file to restart the service. Combing the network for random traffic to the VM ports has revealed nothing.

Any other ideas?

 

[MightyMrMatt]

After fighting with this thing for months, looks like I finally found the culprit. I adjusted the WOL Speed setting on the NIC from "Lowest Speed Available" to "100 Mb" and Wake Up Capabilities to "None". Now the service has been up for days without incident. You can find these settings under the Advanced tab of your NIC properties.