ORBNET Access Control Module Log Locations
The ORBNET Access Control Module (ACM) runs as part of the Milestone XProtect Event Server environment. If you are troubleshooting an ORBNET access control integration, the relevant log files should therefore be collected from the XProtect Event Server.
Log Locations
| Log Type | Default Location | Purpose |
|---|---|---|
| XProtect Event Server Logs | C:\ProgramData\Milestone\XProtect Event Server\logs\ |
General XProtect Event Server logging. Useful when investigating Event Server startup, service or integration-related issues. |
| MIP Logs | C:\ProgramData\Milestone\XProtect Event Server\logs\MIPLogs\ |
Logs generated by components using the Milestone Integration Platform (MIP). |
| Access Control Logs | C:\ProgramData\Milestone\XProtect Event Server\logs\AccessControl\ |
Access control-specific logging and normally the first location to check when troubleshooting an ACM integration. |
Depending on the XProtect version and configuration, log filenames may contain the date on which the log was created.
Collecting Logs for Troubleshooting
Where possible, reproduce the issue immediately before collecting the logs. This makes it significantly easier to correlate the reported problem with the corresponding log entries.
When sending logs to ORBNET Support, please include:
- The approximate date and time the issue occurred, including the local timezone.
- The ORBNET integration being used, for example Brivo, Paxton Net2, TDSi GARDiS or LenelS2 NetBox.
- The ORBNET software version.
- The Milestone XProtect version.
- A short description of what was expected to happen and what actually happened.
- Whether the issue is continuous or intermittent.
Unless ORBNET Support requests otherwise, include the relevant Event Server, MIP and Access Control logs covering the period in which the issue occurred.
Quickly Create a Log Archive
The following PowerShell command can be run on the XProtect Event Server to create a ZIP file containing the current Event Server logs:
$Source = "C:\ProgramData\Milestone\XProtect Event Server\logs"
$Timestamp = Get-Date -Format "yyyyMMdd-HHmmss"
$Destination = "$env:USERPROFILE\Desktop\XProtect-EventServer-Logs-$Timestamp.zip"
Compress-Archive -Path "$Source\*" -DestinationPath $Destination -Force
Write-Host "Log archive created:"
Write-Host $Destination
The ZIP file will be created on the current user's Desktop and can then be attached to an ORBNET support ticket.
Note: Log files may contain system names, IP addresses, usernames and other environment information. Review your organisation's security policies before sharing diagnostic information externally.
Still Having Problems?
If the logs do not clearly identify the problem, raise a support request with ORBNET and attach the relevant log files together with the approximate time of the incident.
Providing the incident time is particularly useful, as it allows the support team to concentrate on the relevant section of the logs rather than conducting digital archaeology across several days of Event Server activity.