Posted by Tom Fulton on February 16, 2011 at 06:07:31:
I encountered a problem this morning updating my Vancouver client. They use XAP and get new licenses every quarter with the new XAP expiration date. They are running CometServices 11.1, although CometSecurityServer shows version 11.0 I transferred their license, renamed out the existing license, renamed in the new license and tried to do a license update. Security Server said it could not process the new license. I reversed both renames and tried doing an update on the license that was in and working, same failure message. I exited the only two Comet users connected ( VM machines ) and did a Restart of Comet services and that worked fine. I stopped services, did my renames to get the new license in place and started services, that worked fine and they now have the new expiration date of 6/15 for XAP. There appears to be a bug in the license update function with 11.0 They did not have this issue under the same procedures with 10.4 CometServices. They have been running on 11.1 for 3-4 weeks.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.