After the agent file system filled up completely, the agent is no longer communicating with the scheduler. Even though the service is up and running, the scheduler reflects the agent as Inactive.
As a result of the agent file system filling up, the agent database has potentially become corrupt.
In order to resolve this issue, you will need to perform a COLD start of the agent. Follow this process in the exact order documented below to resolve your issue:
Was this information helpful?