LicensingPolicy Synchronize and pcA Synchronize entries followed by a message from active machine are normal and expected. Typically, these normal and expected logging events are triggered under the following conditions:
1. Starting/re-starting pcAnywhere host service on a managed endpoint. 2. Making / Terminating connection with host. 3. pcAnywhere policy updates applied to a host machine.
The symptoms are excessive events logged, pcAnywhere host services restarted unnecessarily and item replication reports showing abnormaly high number of items replicated.
Entries like the following will be seen in the notification server logs.
2/8/2013 11:36:50 AM pcAnywhere :: Calling LicensingPolicy Synchronize()
2/8/2013 11:36:49 AM pcAnywhere :: Calling pcA Synchronize()
2/8/2013 11:36:49 AM pcAnywhere :: Message from Active machine <clientguid> is processed
When pcAnywhere solution is installed in an environment set up with hierarchy, pcAnywhere settings policies are getting flagged as 'New' (which can also mean changed) after the NS.Daily schedule is ran. When a differential replication tasks runs these settings policies are incorrectly registered as 'New' and therefore replicated unnecessarily. The policies are then deployed to the pcAnywhere hosts which process the policy as noted above.
Attached to this tech article is an update that resolves the issue with pcAnywhere Settings policies getting marked as 'New' during replication. Applying this update will reduce the amount of items replicated and the amount of NSE's sent to the server which will also reduce the number of log entries in the server logs.
Additionally, the log type of these pcAnywhere log message have been changed from Informational to Verbose/Trace log type. This optimization should help viewing normal, non-verbose, log information.
This update can be applied to pcAnywhere Solution 12.6.7 build 8096 and pcAnywhere Solution 12.6.7 Hotfix1 build 8209.
pcAnywhere solution 12.6.7 installed in an hierarchical environment.