Genetec Patroller™ 7.0.1 includes the following known limitations.
| Issue | Description |
|---|---|
| 3514932 | The Patroller database server name cannot contain characters with accents, for example, é. |
| 3066593 | If a user is present in an Active Directory group that is mapped to a Security
Center group, and the same user is also present as a local Security Center user,
there might be ambiguity as to which user is chosen during the login. In such cases,
Patroller arbitrarily picks either the local user (and its password) or the Active
Directory user (and its password). Workaround: Remove
the duplicate entry in the Patroller database.
|
| 2964908 | When a patrol vehicle moves into a new overtime zone, it can take up to 10 seconds for the auxiliary camera resolution to be updated. License plate reads during this time use the auxiliary camera image resolution settings from the previous overtime zone. |
| 2506954 | If the in-vehicle computer's clock is not in sync with Curb Sense™, it is not
possible to log in to Curb Sense. Workaround: In the
Windows Date & time settings page, enable the setting Set
time automatically.
|
| 2489688 | Context images taken while the patrol vehicle is traveling faster than 40 km/h (25 mph) might be slightly distorted. For example, vehicle tires might appear slightly oval in shape. |
| 2478659 | If you disable FILESTREAM manually on the SQL Server Express server, you must either manually reactivate FILESTREAM or reinstall Patroller for the system to operate. |
| 2101419 | When you view a license plate read in Security Desk that includes additional images from context cameras or wheel imaging cameras, these images are displayed in a certain order in the plate read overview image. If any of the cameras are disconnected at the time of the plate read, the overview image will have an empty tile in the bottom-right corner. For example, if the vehicle includes context cameras A, B, C, and D, and camera B is offline, the plate read overview image might display A, C, D, empty. |
| 1870065 | When registering a patrol vehicle with Plate link, if you enter an email
address that is not associated with an authorized users account, the registration
fails and the login window is not displayed again. NOTE: Only
authorized users can manage patrol vehicles in the AutoVu™ Portal. For more
information, contact your Genetec Inc. representative.
Workaround: Restart the Genetec Patroller™ Config Tool and restart the
Plate link vehicle registration.
|
| 472102 | In SharpX mobile installations where the SharpXS ALPR Processing Unit includes the Navigation option, the ALPR Processing Unit must not be installed with the face plate pointing down or up. For more information on hardware orientation, refer to the AutoVu Hardware Guide for SharpX Mobile Installation. |
| 511791 | When upgrading Patroller, the installer incorrectly offers the option to modify database settings. If the user changes the database credentials during the upgrade, the installer applies the changes to the database but not to the Patroller configuration. The user must then update the configuration manually. |
| 506319 | After upgrading from 7.0.0 build 7.0.115.0 to build 7.0.1135.0, Patroller is no longer registered in Security Center. |
| 341784 | When viewing the live feed from the SharpZ3 LPR camera, Patroller displays images from both of the SharpZ3 camera unit's LPR cameras, which may cause a flickering effect. |
| 341612 | When installing Patroller using mixed mode authentication, an issue occurs if you enter a SQL Server password that does not respect the password strength guidelines stated in the installer. In this case, Patroller is installed, but SQL Server uses Windows authentication instead of the expected mixed mode. For more information, see [KBA-79168] Patroller installation in mixed mode authentication changes to Windows authentication. |
| 341199 | User connected to Patroller is not automatically logged out when a session expires, or logon hours expires. |
| 341179 | If an Active Directory user tries to change their password in Patroller, Patroller does not update the Active Directory and the password is not changed. Only a user logged on with a Windows account can change their Patroller password. |
| 341166 | If a user's GUID is changed due to a modification of the user group in Active
Directory, it results in a duplicate entry in the Patroller database. Workaround: Create a new Patroller database and
resync.
|
| 340927 | In an area where GPS satellite reception is blocked by nearby buildings, if the GPS location is not accurate when the patrol vehicle enters a covered parking facility and loses GPS reception, the positions of the vehicles in the parking facility will also not be accurate. |
| 340841 | For SharpZ3 systems using 2.4 mm AutoVu auxiliary PoE cameras for additional context images, the context images displayed in Patroller are sometimes pixelated. |
| 340321 | If the Patroller mode is changed from Law to Curb Sense, the Patroller log out
window still includes an option to "Offload and exit". This message should not be
displayed in Curb Sense mode. Workaround: Uninstall
Patroller, delete all content from the MobileClient folder except for BeNomad,
delete the Data folder, then reinstall Patroller in Curb Sense
mode.
|
| 340159 | As a patrol vehicle moves and the map is redrawn, the blue line indicating the vehicle path can sometimes extend a short distance beyond the vehicle location. |
| 296429 | Time limited parking: If the configured "Duplicate hit delay" period is greater
than the Overtime rule, duplicate hits are raised during that period. Workaround: Always configure the Overtime rule to be
longer than the duplicate hit delay period.
|
| 227487 | To use overtime enforcement over a period of 24 hours or more, the Overtime rule regulation Applicable hours must be set to All Day. If Applicable hours is set to a time range, then an overtime hit is not raised on the second day. For example, if you have a 1 hour overtime rule that is configured with a specific time of day of 8:00-18:00 and is applicable all week long, a plate read on Monday at 17:00 will not raise a hit on Tuesday if it is read at any time between 8:00-18:00. |
| 225947 | When creating a New Wanted without entering an expiry date, the entry will expire based on the Store Hits setting (default is 120 hours). You can edit the expiry date but once it is edited, you cannot edit it again to set the value back to undefined. |
| 213853 | When using the Plate Copy plugin with Copy plate number to Windows clipboard setting enabled, the plate number copied to the XML file does not correspond to the plate number that was selected in Patroller for overtime and shared permit hits. |
| 134674 | If multiple plates have the same plate number but different issuing states,
provinces, or countries (for example, ABC123 from NY and ABC123 from NJ), hotlist or
permit list changes transferred to Patroller may not be accurate. NOTE: This issue occurs with live hotlist or permit list transfers
only; USB transfer is not affected.
Workaround: To avoid this issue, make sure you are running the latest
versions of both Security Center and Patroller.
|
| 76798 | Patroller raises permit and shared permit hits for the same vehicles that
already have similar hits pending acknowledgment. For example, if Patroller raises a
permit hit for license plate ABC123, it should not raise another permit hit for that
plate (for the same violation) until you either accept or reject the first permit
hit. Workaround: Whenever possible, accept or
reject hits as they occur. Try not to leave many hits pending.
|
| 59320 | After you acknowledge (accept or reject) a hit in Patroller, the hit icon on
the map turns grey, which is the same color as a read. As a result, you cannot
differentiate between reads and acknowledged hits by looking at the map. This
applies to all types of hits (hotlists, permits, overtime, etc). Workaround: To view acknowledged hits in Patroller, tap
Hits, and then tap
Review.
|
| 55620 | Patroller switches from live reading to the list of unacknowledged hits, even
when new hits are automatically rejected. For example, when you set an
acknowledgment buffer, you specify a limit to how many hits can remain
unacknowledged before Patroller rejects all subsequent hits. After this limit is
reached, a hit causes Patroller to switch from live plate reading to the list of
unacknowledged hits, even though the new hit is automatically rejected and does not
require user interaction. Workaround: You need to
switch back to live reading every time you receive a new hit, or clear the list of
unacknowledged hits.
|