ID 465364 - Sometimes the frame server can fail to license, which happens more frequently with Nuke Indie

Problem summary
Sometimes the frame server can fail to license, which happens more frequently with Nuke Indie

It looks like the frame server can't access the license file, and from using ProcessMonitor to check the active processes, this seems to be the case: 

Customer reported version

Nuke Indie 12.2v4

Customer reported platform

Windows 10

Steps to reproduce

1) Install a Nuke Indie license Via Nuke's licensing dialog, so your license file gets a umsid:

2) Open Nuke Indie

3) Wait a few seconds, sometimes the frame server will crash with this error:

NukeIndie 12.2v4, 64 bit, built Dec 3 2020.
Copyright (c) 2020 The Foundry Visionmongers Ltd. All Rights Reserved.
A license for 'nukeindie' was not found.
FOUNDRY LICENSE ERROR REPORT
----------------------------
Timestamp: Thu Jan 21 16:37:37 2021
License(s) Requested:
nukeindie 2020.1203 interactive with options all
Extended Info: None Provided
Host : Pete-PC
System ID(s) : 902b3435aee8 , e894f627cfb6 , 1a94f627cfb6 , c2155dbd26a0
RLM Environment Info: C:\Users\Pete\FoundryLicensing;C:\Program Files\The Foundry\RLM;C:\ProgramData\The Foundry\RLM;C:\Program Files (x86)\The Foundry\RLMReason for failure: A suitable license does not exist.RLM LICENSE DIAGNOSTICS
---------------------------
nukeindie_i : No license for product (-1)
License Path:
C:\Users\Pete\FoundryLicensing;C:\Program Files\The Foundry\RLM;C:\ProgramData\The Foundry\RLM;C:\Program Files (x86)\The Foundry\RLM;C:\Users\Pete\FoundryLicensing

* Running Nuke Indie in the background, so that it is opening behind another application seems to make it happen more frequently

Expected behaviour
For the frame server to launch

Actual behaviour
The frame server encountered an error

Workaround
To workaround the issue, if you change you license file name from the umsid name (for example 07dfb396-7bf1-437d-9a2d-347b8268a461.lic), to indie.lic, then the issue should stop. Information about where to find your login based Indie license can be found here: Q100523: Where are Foundry Licenses installed on my machine?
Adding an exception for Nuke in your firewall/security can also prevent the issue

Reproduced by support
This bug has been reproduced in:

Nuke 12.2v4 Indie - Windows 10*

*sometimes, has been able to reproduce across multiple machines, but only rarely so can't confirm if this is OS specific due to the rarity of the bug

Earliest version tested

Nuke 12.2v4 Indie - previous versions have expired, so can create umsid licenses for them