Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.
Access Event Viewer running in a CyberStation other than the primary access server works initially but after some period of time stops displaying access events.
Product support has identified several scenarios that can result in Workstations other than the primary not showing events in the Live Event Viewer. The commonality with all these cases is that the Primary Access Server will always show the events, so before using any of the solutions specified here make sure that is ONLY workstations other than the PAS that are not displaying events in their Live Event Viewer
NOTE also, that we are referring strictly to the Live Event Viewer in this article so it is assumed events are showing in a list view including the Access Events tab that shows events in the door's editor.
CAUSE #1 (Primary failed over to Secondary then back to Primary)
In systems configured with a Primary (PAS) and secondary (SAS) Access Server, it has been found that after a fail over to the SAS due for instance to the PAS going offline, event viewers in other workstations continue to show events UNTIL the PAS WS returns online and resumes its role of PAS at which point all workstations (other than the PAS) stop displaying events in their Live Event Viewers.
CAUSE #2 (MSMQ issue reported and fixed by Microsoft)
Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2)
Access event viewers at workstations other than the primary access server do not show events.
Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.
Please see MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.
MSMQ CleanupInterval setting too short.
- First make sure the ControllerStatus notification object is configured to send the offline alarm to all the Workstations in question.
- Second, put a PE program in the SAS to serve as a monitor to let the Live Event Viewer know when the PAS has returned online, this is accomplished by referencing an object from the PAS
SAMPLE PE POGRAM
SOLUTION #2 (MSMQ issue reported and fixed by Microsoft)
Click MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.
In the Windows registry add the \SOFTWARE\Microsoft\MSMQ\Parameters\CleanupInterval key.
Recommended setting is 3600000 which is the number of milliseconds in an hour
See more information from Microsoft