This can occur if client has Kerberos Monitors and is running ipMonitor 10 1371 or earlier. The current workaround is to disable the Kerberos Monitors until the next service release. Here's how:
1. Click "Device" tab.
2. Within the search box at the top-left, type "kerberos".
3. To the right of the search box, click the small down-arrow.
4. Click "Monitors -> Search by Type".
This will list all of the Kerberos Monitors.
5. Select all and click "Disable".
Monitor the installation for a few hours to confirm this is the cause.
More info on this issue within Test Track 3060