This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- Foundation / CloudScape
- :
- Foundation/CloudScape Forum
- :
- Errors entering key code on RN150 appliance: "Error encountered when submitting key" and "This key i...
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 18, 2021
12:39 AM
Errors entering key code on RN150 appliance: "Error encountered when submitting key" and "This key is already in use by another appliance"
Hi Team,
Please help with the issue.
While provisioning the RN150 appliance and after entering the key code we were prompted to select between a FlexDeploy setup. At this step, the web-browser's tab closed (by mistake) and I wasn't able to perform that action afterwards with the following message:
> Error encountered when submitting key. Please try refreshing the page, or contact support if this persists.
Refreshing the page or opening it from another browser didn't make the trick, so I chose to re-create the RN150 appliance, which turned out the wrong thing to do, since now it seems that the key cannot be used anymore as the respective message implies:
> This key is already in use by another appliance.
> Error encountered when submitting key. Please try refreshing the page, or contact support if this persists.
Refreshing the page or opening it from another browser didn't make the trick, so I chose to re-create the RN150 appliance, which turned out the wrong thing to do, since now it seems that the key cannot be used anymore as the respective message implies:
> This key is already in use by another appliance.
Please help
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
0 Replies
