Aveva License Server 2020 issue

The issue I am having has to do with the service "license server core service" stopping and not able to start.

There have been no user or policy changes.  It is not possible to start the service manually, (start button greyed out)

I am wondering if there Is a way to get this service to start again without restarting the machine?

The issue I am having has to do with the service "license server core service" stopping and not able to start.

There have been no user or policy changes.  It is not possible to start the service manually, (start button greyed out)

I am wondering if there Is a way to get this service to start again without restarting the machine?

That's odd. It seems the service is stuck in the "Stopping" state.

Perhaps you can find the process in Windows Task Manager and kill it, then try to start it again?

My guess is that your FNE server cache somehow got corrupted. To resolve it, please attempt the following:

1. Stop the License Server Core Service in windows via the following CMD command: 
net stop "License Server Core Service"

2. Once fully stopped, navigate to C:\Program Data\FNE Server

3. Take a backup of the 3 files in that location, and then delete them. 

4. Start the service via the following CMD command:
net start "License Server Core Service"
This should then recreate the 3 files we deleted before

5. Return back to your Enterprise License Manager and run a Sync

Hi Rickard and Adam, killing the service was surprisingly hard.... but it did the trick and I was able to start the license server again.

Adam Rego  out of curiousity what purpose does the fne cache have?

Thank you for your help!

There seems to be no official documentation for the FNEServer files, but from my knowledge, they are part of the License Server Trusted Storage system. This means that these files securely store and manage the general information for your license server. When you go to perform actions on the license server, such as starting it, stopping it, adding/removing licenses, ect., the license server goes and validates that the FNEServer files are 'correct'. One of the more common errors seen when the FNEServer files are bad is "The FNE Server encountered an error: Response is out of order with previous responses". They are essentially validation files.