penDirector displays following message in the support log: Failed to update pen information, Exception message: Function call failed because pen is already in progress by other instance. Try again later.
This message can be ignored. It may appear even if everything is all right, for example when synch is in progress and some dialog wants to update pen info. It will occur if you have Pen Settings tab open and dock pen with strokes and synchronization is started.
'Get strokes' operation takes a long time and other pen operations cannot be performed during it so all methods fail with error " Function call failed because pen is already in progress by other instance. " the getting strokes operation. It's normal and indicates that the pen is busy performing synchronization and the operation should be called later when synchronization is finished.
pen Director log displays following message: CommonLogging: ERROR: Failed to update pen information, Exception message: Thread was being aborted.
It doesn't cause any problem. The message is shown when user opens pen settings tab(or other) and later closes the tab or window before all the information has been received so software cancels operations since software doesn't need the results. The methods fail with exception "Thread was being aborted. " because software canceled them.
penDirector log shows following error: Exception message: Proxy/Channel error has occurred
This message indicates that the issue is in PAF (Pen Access Framework) based on WCF (Windows Communication Framework that PAF is built on). This might be caused by a conflict between penDirector and Windows after an update of Windows.
This message can also be shown when the user upgrades FW of the pen and PenDirector cannot read data from it (pen becomes disconnected and after FW is upgraded successfully reconnected automatically again). In other words, this is 'normal error' when an app tries to get information from the pen when pen is disconnected.