[Solved] Free License Error with One Worker

We are using free-license with only one worker but there is a license error about “limited number of workers”.
As I can see only the one worker, I can’t find any other instances to remove them.

Any help will be appreciated.
Thanks

What version of Deadline are you using? Can you post the full licensing error you are receiving? In the Worker panel there is only a single Worker entry?

Regards,

Charles

I am using version 10.1.7.1. There is only one entry in worker panel (please see the attachment).
Here are last lines of worker log:

2020-10-07 17:38:49: Skipping pending job scan because it is not required at this time
2020-10-07 17:38:49: Skipping repository repair because it is not required at this time
2020-10-07 17:38:49: Another house cleaning process is already in progress
2020-10-07 17:38:50: Could not obtain license because:
2020-10-07 17:38:50: The Worker cannot run in TRIAL MODE because there are more than two Workers in the Deadline Repository. For more information, please email thinkbox-sales@amazon.com.
2020-10-07 17:38:50: Scheduler Thread - >>> LICENSE CHECK OUT FAILED, SKIPPING TASK DEQUEUING
2020-10-07 17:38:56: Skipping pending job scan because it is not required at this time
2020-10-07 17:38:56: Skipping repository repair because it is not required at this time
2020-10-07 17:38:56: Another house cleaning process is already in progress
2020-10-07 17:38:56: Could not obtain license because:
2020-10-07 17:38:56: The Worker cannot run in TRIAL MODE because there are more than two Workers in the Deadline Repository. For more information, please email thinkbox-sales@amazon.com.
2020-10-07 17:38:56: Scheduler Thread - >>> LICENSE CHECK OUT FAILED, SKIPPING TASK DEQUEUING

Thanks

Open admin cmd prompt, and run the following commands:

“C:\DeadlineDatabase10\mongo\application\bin\deadline_mongo.bat”

db.SlaveInfo.count({})

That should return a number, if it is greater than one, the database has left over entries that are counting against the license trial mode.

If that is the case, you can run:

db.SlaveInfo.remove({})

To remove all of the Worker entries. Once you have done that reload your Worker and Monitor to see if that resolves the issue.

If the issues remain, I’d upgrade to the latest version as I’m not running into the same issue with that version.

1 Like

I ran the count command and it returned 1; I removed it and the error gone.
Thanks for your support.