On a working system, valid access events no longer show in the active event view and are no longer visible in the accessevent table within the Database. However, invalid events continue to work normally.
- Access Events
An incomplete object may have been added to the Continuum Database recently that is interfering with queries running against that database.
Try the following steps to troubleshoot the issue
- Does the issue happen on multiple CyberStations?
- Ensure all the event types are selected in the active event view that is being used on the door(s).
- Perform a CyberStation Teach
It is best to contact PSS and work with them at this point with the following procedures.
- Verify that access events are being sent from the controller to the CyberStation using Wireshark.
- Verify that the issue follows the Database by loading the database in a test environment to see if the issue still happens.
- On the TEST database, use SQL Management Studio:
- SQL Query: set acdbversion=0 (execute the query)
- Update database: launch Database Initialization Server/Stand Alone
- Enter sa password and update database
- Restore database or locate incomplete object
- The quickest fix would be to revert to a known good database. Once restored, the events in the controllers would be downloaded to the database.
- Finding the object in the database that has caused the issue can be very challenging. Check to see if there was a controller recently added and if the issue began to happen after that. If for some reason a controller had been added and it wasn't completed normally then it could cause this issue.
- Check to see if there is a controller in the InfinityController table with an objectidhi or objectidlo with a zero value. If so, delete that controller and see if the valid access events start coming in.
It may also be necessary to use the SQL profiler to view the entries that are being made into the database. See the following link below for more information. http://msdn.microsoft.com/en-us/library/ms181091.aspx
Turning off the Primary and Secondary Access Server will cause the access events to buffer in the controllers, so that these events will be inserted into the database once valid access event logging has been restored. After turning off the primary and secondary, check the Access Log infinity system variable on the controllers. If they are non zero values, then events are buffering. There is a limited amount of access events that can be stored in the controllers before loss of data occurs.