Link to home
Start Free TrialLog in
Avatar of Nolan Gustavo
Nolan GustavoFlag for United Kingdom of Great Britain and Northern Ireland

asked on

VMWARE ESXi 5 error: unable to apply DRS resource settings on host not allowed in current state. DRS is not licensed and disabled

Hello All,

We have a problem with one of the hosts in the cluster showing a DRS error. The customer is not licensed for DRS and the feature is disabled anyway, I am not sure why all of the sudden it started showing DRS related errors?
I have included some screenshots, if any knows how to resolve this please let me know.
DRS1.PNG
DRS2.PNG
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

I think the first thing we would do is the following:-

1. Restart Network Management Agents on this host that has issues.

2. Restart vCenter Server service ?
ASKER CERTIFIED SOLUTION
Avatar of Jo_Wickerman
Jo_Wickerman
Flag of South Africa image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Nolan Gustavo

ASKER

I have already restarted the management agents however this did not make any difference. I will try restarting the vCenter service first, if service restart doesn't resolve this I will follow the rest of the suggestions. Will let you know how I get on shortly.
Thanks!
Yes ESXi 5.0 3 host cluster
Okay, DRS is not been configured by accident, it only takes a tick in the box ?
The setting in the picture supplied is for vCenter, not the host.

As far as I can see, the host is the actual problem. Let me know when you have tried my recommendations.
Ok guys looks like POOLS.XML file was corrupt, I called VMWARE support in the end as this was production environment and they recreated the config file to resolve the issue.
Jo_Wickerman your solution is correct if I followed your steps by removing the host from vCenter rebooting and then re-adding back would have recreated this file anyway which would have resolved the problem.
VMware managed to recreate the file without having to reboot the server which helped.

Thanks!