×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
"Attempt made to change length of the license user, resulting code 1."
F1 shows:
Additional Message Information
Message ID . . . . . . : CPF9E1F
Date sent . . . . . . : 02/13/17 Time sent . . . . . . :
13:22:42
Message . . . . : Attempt made to change length of the license user,
resulting code 1.
Cause . . . . . : An attempt was made to change the length of the
license
user for product 5770WDS, license term V7R1M0, feature 5101. The
resulting
codes and their meanings follow:
01 -- Because there were not current users, length of license user was
changed and user was added.
02 -- Because there were current users, length of license user was not
changed and user was not added.
03 -- Length of license user did not match length of license user
specified on the request of this license.
Recovery . . . : Recovery for 2 - Use the QLZARLS API to release the
current users and try to change the length again. Recovery for 3 -
Specify
the correct length and try again.
They occurred at 6:35am when I opened RDI and again at 1:22pm because I
don't know why.
What is this telling me? I'm reading that it applied a license for 5770WDS
to me and was successful. I don't know why in the first instance since I'm
a 1-person shop and I don't know in the second instance if it was
successful the first instance.
The only thing that's changed since last week is the cume apply Friday
night.
Thanks.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.