AnsweredAssumed Answered

Application Error  - Faulting application name: PINotifications.exe

Question asked by richardf on Mar 2, 2017
Latest reply on Jun 9, 2017 by dlp

PiNotifications doesnt work anymore now. In the Event Viewer if found these logfiles. I don't know how to fix it. Restarting the services isnt the options. It tryed it a couple of time. It start but then automaticly it stops after a few seconds. 

Does anyone have any suggestions or better the answer to this problem?



Faulting application name: PINotifications.exe, version:, time stamp: 0x57ed4955


Faulting module name: KERNELBASE.dll, version: 6.1.7601.23543, time stamp: 0x57d2fe27


Exception code: 0xe0434352


Fault offset: 0x000000000001a06d


Faulting process id: 0x2ad4


Faulting application start time: 0x01d2931fd03a2f6d


Faulting application path: D:\PIPC64\Notifications\PINotifications.exe


Faulting module path: C:\Windows\system32\KERNELBASE.dll


Report Id: 16de9ae4-ff13-11e6-b925-005056b04fbf



Application: PINotifications.exe


Framework Version: v4.0.30319


Description: The process was terminated due to an unhandled exception.


Exception Info: Microsoft.Isam.Esent.Interop.EsentVersionStoreOutOfMemoryException




   at OSIsoft.PINotifications.Core.Scheduling.SchedulerOperation.Invoke(OSIsoft.PINotifications.Core.IScheduler)


   at OSIsoft.PINotifications.Core.Scheduling.SingleThreadedScheduler.ThreadMethod()


   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)


   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)


   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)


   at System.Threading.ThreadHelper.ThreadStart()




PINotifications (10964) PersistentDictionary: The version store for this instance (1) has reached its maximum size of 32Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.


Possible long-running transaction:


SessionId: 0x000000001A950B60


Session-context: 0x00000000


Session-context ThreadId: 0x00000000000022BC


Cleanup: 1