hi I have renewed my unlimited license today and received a confirmation email today. Rechecking the license does not remove the warning at the top of the page. Is this a manual proces? Just a heads up anyway as it expires in 6 days.
thanks ronald
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 01/11/2010 - 13:46 Comment #1
There is a manual step needed by us in some cases. I have applied your upgrade now though, so if you click the "re-check license" link, you should see the new date.
Submitted by Issues on Tue, 01/26/2010 - 19:20 Comment #2
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by ceup on Wed, 01/27/2010 - 09:55 Comment #3
My License expired and since then I have renewed my license, however the license still shows as expired. I have repeatedly checked the "re-check license status". It does look to be updating correctly. Is there something that needs done manually?
Submitted by andreychek on Wed, 01/27/2010 - 10:01 Comment #4
For future reference, it's probably a little simpler for us if you open a new request :-)
However, it sounds like the license manager wasn't able to automatically upgrade it, so Joe or Jamie may need to manually process something on our end here.
I'll pass this along to Jamie for further comment.
Submitted by JamieCameron on Wed, 01/27/2010 - 12:45 Comment #5
Ok, I have applied your renewal ..
Submitted by Issues on Wed, 02/10/2010 - 14:19 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Wed, 02/10/2010 - 16:19 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Wed, 02/10/2010 - 18:18 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Wed, 02/10/2010 - 20:20 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Wed, 02/10/2010 - 22:19 Comment #10
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 02:20 Comment #11
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 04:22 Comment #12
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 06:20 Comment #13
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 08:19 Comment #14
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 10:18 Comment #15
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 12:18 Comment #16
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 14:19 Comment #17
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 16:19 Comment #18
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 21:19 Comment #19
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 02/11/2010 - 23:18 Comment #20
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 01:20 Comment #21
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 03:22 Comment #22
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 05:19 Comment #23
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 07:19 Comment #24
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 09:19 Comment #25
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 11:19 Comment #26
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 13:20 Comment #27
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 15:18 Comment #28
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 17:18 Comment #29
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 19:20 Comment #30
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 21:19 Comment #31
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Fri, 02/12/2010 - 23:18 Comment #32
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 04:22 Comment #33
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 06:19 Comment #34
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 08:19 Comment #35
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 10:19 Comment #36
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 12:19 Comment #37
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 14:19 Comment #38
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 16:18 Comment #39
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 18:19 Comment #40
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 20:19 Comment #41
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sat, 02/13/2010 - 22:20 Comment #42
Automatically closed -- issue fixed for 2 weeks with no activity.