AWS Thinkbox Discussion Forums

UBL Licensing Credit / Feature Error (10.1.16.9/10.1.22.4 Redshift 3.0.31)

I’m getting this issue, can’t figure it out, I have 2 different servers running License Forwarders to different accounts, if I use one it works fine, if I switch to the other one it gives a similar error.

I’m not sure if it’s related to having 99% used up credit, or is an issue with the account, have a ticket open about this, doesn’t seem like set-up error if 1 of the accounts works.

Is there a cut off point for the credits (eg. 99.5%) or does it wait till it gets to 100%?

Is there anyway to reset the credit scale? 99% used, but it hasn’t touched the new credit, it’s based off the 1000’s of hours previously used last year

2022-06-30 07:44:25:  Licensing Error: Not enough credit for deadline-redshift
2022-06-30 07:44:25:  Feature not found in trusted storage
2022-06-30 07:44:25:  Could not checkout UBL credits for "redshift".
2022-06-30 07:44:29:  Licensing Error: Desired features ignored.
2022-06-30 07:44:29:  [1,7e3,4,0[70000001,0,120b028c]] One of the input parameters is bad.
2022-06-30 07:44:29:  Licensing Error: Not enough credit for deadline-redshift
2022-06-30 07:44:29:  Feature not found in trusted storage
2022-06-30 07:44:29:  Could not checkout UBL credits for "redshift".
...
2022-06-30 07:44:40:  Licensing Error: Desired features ignored.
2022-06-30 07:44:40:  [1,7e3,4,0[70000001,0,120b028c]] One of the input parameters is bad.
2022-06-30 07:44:40:  Licensing Error: Not enough credit for deadline-redshift
2022-06-30 07:44:40:  Feature not found in trusted storage
2022-06-30 07:44:40:  Could not checkout UBL credits for "redshift".
2022-06-30 07:44:43:  Licensing Error: Not enough credit for deadline-redshift
2022-06-30 07:44:43:  Could not checkout UBL credits for "redshift".

There is a similar ticket here, but this seems like a set-up issue

I had Justin look into this issue and he figured out that the nodes were using an older version of Deadline 10.1.9 (didn’t notice that) and this is possibly related to the incompatibility changes with RCS. Updated and it’s all working well :smiley:

Privacy | Site terms | Cookie preferences