Posted by Tom Fulton on June 16, 2017 at 09:25:40:
End-User upgraded to current over this past weekend. Today they've had their CometAnywhere Host crash and a user have her PC lock up. CA host was replaced with a different PC, process probably took 30-45 minutes. Had to restart Comet Services to free up the CA licensing that was orphaned. User restart can't connect due to security violation, duplicate profile name. Is the current Security Server supposed to kill orphaned connections? If so, what's the time frame? For the user reboot I'm going to have to give them another profile name as they have 40 local users, no way I can get them to restart services again.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.