Event Linking Time Triggers using custom days of the week are activating on the wrong day. They are triggering 1 day earlier so events set for Saturday are triggering on Friday and so on.
Tested Version
exacqVision Server 22.12 – 22.03
Steps To Reproduce
Create a new Event Linking action
Set Event Type to Time Trigger
Under Event Source select New
Configure a time trigger
Give the trigger a name
Select a Start Time and End Time
Set Frequency to Custom
Select the current day of the week
Set Action Target to Notify
Expected Results
On the day and time specified in the Time Trigger
Event Links Status switches from off to on
An email is sent
Actual Results
Event links status stays off
An email is not received
Solution
Downgrade to exacqVision Server version 22.09
NOTE: Fix will be available in exacqVision Server version 23.06
When system reboots and boots up to recovery mode it selects “Factory Capture” by default leading the system to commit a full factory restore upon pressing “enter”.
Solution
Windows
Open CMD, using Run as Administrator
Enter mountvol z: /s
Enter z:
Enter dir
Enter cd EFI/BOOT
Enter notepad refind.conf
Search for the default_selection entry
Set the parameter to “1” instead of “factory restore”
Save your changes and reboot the NVR
<br>
Linux System
The file at ‘/boot/efi/EFI/BOOT/refind.conf’ will need to be edited in the same way it is for the Windows instructions. Instead we would follow these steps:
Open Terminal (CTRL+ALT+T)
Enter sudo -i
Enter caja (this should open a file explorer type window)
Navigate to /boot/efi/EFI/BOOT/refind.conf
Right-click and open file a text editor
Edit the text as shown in Step 6 of the Windows instructions above.
Save your changes, close the file, and restart the system
The client Software crashes once trying to create an even link for the security integration, especially when selecting the DSC security integration alarm input.
Solution:-
This issue has been fixed on ExacqVision Client Ver23.03.106 and above
ExacqVision Client version 23.03.106 can be downloaded Here
When connecting the web service to the EM server, The EM server can connect to the web service. However, it can’t push an update to it or remotely administrate the web service and keeps going back and force between “Remote Restriction” and “Running”
Solution
This issue has been fixed on Enterprise Manager Version 23.03.103 or above
Windows 7, Windows Embedded images have reported seeing drive as offline. This is a false negative.
Product
Server 23.03, 22.09, 22.06.
Steps to Reproduce
Go to Storage section in the client and select the Drive tab.
Drives show up as offline. Drives are mounted in OS and have data recording to them.
Expected Results
The drives should not show offline.
Actual Results
Drives will show up as offline, if you disable one, I found that most will correct but that another drive number might show up as offline. Another Indication is that the Hardware tab will show improper status as well.
Solution
Corrected in RC 23.03.2 or wait for next release in June 2023. AES-309
Some of the drives on the raid system are not working on the same raid array with the other drives even if it’s Identical, except the logical sectors showing 512b for the majority and 4K for the new drive or vice versa, so to convert this drive, you will need to use a unique tool provided by Western Digital called WDCKIT.
We have two tools. One can be working with the JBOD drive and another tool that can be working behind the Riad system
!!!!!!! WARNING Proceed With CAUTION !!!!!!!!!!! Multiple Drives IN a Virtual Drive (Actively Recording) = Works BUT deletes the Virtual Drive and data !!!Warning!!! Multiple Drives IN a Virtual Drive with Data (evServer Stoped) = Works BUT deletes the Virtual Drive and data !!!Warning!!! Multiple Drives IN a Virtual Drive with NO Data (evServer Stoped) = Works BUT deletes the Virtual Drive !!!Warning!!! Multiple Drives IN a Virtual Drive NOT formatted = Works BUT deletes the Virtual Drive !!!Warning!!!
Procedures:-
Identify the hard drive(s) that are set with a 4K or 512b logical sector size using one of the following methods: a. $>storcli /c0/e252/s? show all | findstr Logical b. Login to the RAID graphical utility --> Controler ID 0 --> Drives --> Unconfigured Drives c. $> smartctl -i /dev/sd? | findstr Sector
Once the drive(s) have been identified, copy the Serial Number and/or the Model Number. We suggest using the Serial Number if a small number of drives need to be changed. If there are many Drives to be changed, then We recommend using the Model Number.
You can either install the Western Digital “wdckit” utility or use an interactive command prompt window that runs the “wdckit” utility.
$> wdckit show == Shows all the drives in the system with Serial number and Model Number.
$> wdckit show -g == Shows the geometry of the drives. (ie 512 or 4096) $> wdckit format –serial (serial Number) -b 512 –fastformat $> wdckit format –model “(Model Number)” -b 512 –fastformat
Power cycle the drive or the system
5. Verify the Logical sector size has changed to 512b a. $>storcli /c0/e252/s? show all | findstr Logical b. Login to the RAID graphical utility --> Controler ID 0 --> Drives --> Unconfigured Drives.
Time synchronization is an often overlooked concept in computer networking. The Network Time Protocol, also just shortened to NTP, is a network protocol and standard that allows distributed computers to synchronize their time.
Why is this important? Keeping proper time on computers, particularly when dealing with several computers communicating with each other, is important for things such as logging data and tracing of activity. On an NVR, perhaps the most important aspect is that of file system accuracy. Knowing when files were written or read is important to verify the when the activities in recorded video took place, as well as to perform forensic searches. Computer systems also need to know which version of files are most current for syncing files and performing file recovery. Time is also used by operating systems for many security and management controls, such as when using Active Directory/LDAP.
NTP consists of different tiers, originating from extremely accurate atomic clocks. These tiers are referred to as “stratum,” and measure the distance between systems in each tier and the atomic clocks in the top-most tier, deemed to be officially accurate. As the stratum number increases, the confidence of being synched to the most official time decreases. Primary time servers, such as time.nist.gov, pool.ntp.org, time.windows.com, time.google.com, and many others, are in Stratum 1.
When enabled, an NTP client like the NVR running your ExacqVision Server, begins a request from the NTP server.
Your system then automatically calculates the delay in the network link and uses the offset time (the offset time is based on the time zone setting you choose) and adjusts its own clock to the correct time and date.
If your system time is much different from the NTP source when this begins, it may take 5-10 minutes and several of these exchanges with the NTP source to initially bring the system clock into alignment with the NTP source. Once your system is synchronized it will continue checking for updates about every 10 minutes.
If you are experiencing problems communicating with an NTP source on the internet, you may need to investigate your firewall or antivirus settings. The exchanges made by the NTP protocol utilize UDP on Port 123.
<br>
How to check the Stratum level used on Windows
Open a CMD window to reveal a CLI prompt.
Enter the following command: C:\Windows\System32\w32tm.exe /query /status
The stratum level can be seen on the second line of the results. The following example:
<br>
How to check the Stratum level used on Linux (Ubuntu)
Open a Terminal window to reveal a CLI prompt.
Enter the following command: ntpq -c rv
The stratum level can be seen on row three of the results, as pictured in the example below:
Before making a new article, perform a through search of Public, Level 2, and Internal articles to determine if an article already exists covering the desired topic. Use different search terms, including with and without hyphens, where applicable. A recent review found several examples of duplicate content.
Can an existing article be updated rather than making a new article? While keeping the lengthiness of articles in mind is wise, also consider that more articles make keeping them updated more difficult. <br>
Does the new article you wish to write provide value? If it only adds a tiny bit of new information, it may be better to update an existing article rather than creating an entirely new article, and/or linking to an existing article.
Do not create an article that simply links to another article, with no new information, as seen in this example: <br>
If you need to link to another article from the one you are writing, can you link to a search result for related terms rather than creating a hard link to an article?
Hard linking to a specific article could create a broken link in the future. This does not mean you cannot create a hard link, but it is a consideration to make. <br>
When creating links, enable the “Open in new tab” toggle. This will cause links to open in another browser tab so users do not lose the article they linked from. <br>
When possible, do not hard link to external blogs and articles. Again, this could create broken links in the future.
One such example found linked to an external product that was no longer a valid URL. Some others linked to Microsoft KBs that no longer existed. Instead, it is preferable to write the content into our own article, rewording carefully to avoid plagiarism or simplify the explanation. Users can still perform search engine queries outside the portal if they need more detail than we provide about a technical aspect of protocols or operating systems.
Also be sure to avoid linking directly to competitor content, such as an Axis whitepaper or a Hanwha user manual. <br>
Do not use unlicensed images from other sites to explain technical concepts. If you cannot create an image/diagram on your own, you may be able to find assistance from others within Support or from JCI resources. <br>
Try to create clear and legible screen captures. Avoid using a phone’s camera to capture a screen shot as this can appear unprofessional. If help is needed, inquire with other Support team members for help or for tools that can assist with this.
Greenshot is a recommended free tool for help in creating still image screen captures. <br>
Set Client to Light Mode, which is the default client appearance, when making Client screen shots and captures. <br>
Check the size of the images or screenshots as they appear in the published article on the portal. Are they too small or blurry to read? <br>
Do not include full article titles as Tags. This defeats the purpose of tags. Tags should be considered like keywords, usually just one or two words in length. A bad use of this can be seen below: In the article above, the entire title is listed as a Tag. A better option might be separate Tags for ‘license’, ‘licensing’, ‘how to’. <br>
Do not include a period at the end of an article title. <br>
Do not set Headings to ‘Bold’. As headings, they are already preformatted. <br>
Do not repeat the same instructions under different headings. As an example, one article found listed the exact same text as both the Issue and as the Solution. <br>
Try not to overuse Headings. Article Headings create entries in the Content fields, which can be useful in navigating lengthy articles. But are they necessary to navigate, particularly in very short articles? <br>
When listing the “Steps” involved in reproducing an issue or the solution… use an Ordered List. Simply change the block from the bullet point list (un-ordered) and select the icon with numbers for an ordered list. This is more logical when steps in a specific order are involved. <br>
Include version information of the affected Exacq software or camera firmware! Without version information there is no indication as to when a specific bug or issue affects the reader. Additionally, they would not know when a bug fix or enhancement resolved an issue or changed the configuration setup. <br>
Provide some kind of details on the issue. In the below example, there is nothing about versions of software, firmware, or the specific models and/or generation of cameras. This could imply to a customer that JCI’s own camera brand is a bad product. We want to avoid that where possible. Instead, indicate the specific models or generation this applies to, as well any exacqVision versions affected. <br>
When including information/steps regarding different versions of software or operating system in the same article, list these top-down from newest to oldest. This makes finding the latest version information on the top of the article the easiest to find. This is also an appropriate use of Headings so that readers may use the Contents section to quickly be taken to the steps for their version. <br>
Where necessary add tags that include alternate English spellings. i.e. – Color / Colour <br>
Do not add plugin tags or log level tags to standard articles as this will add them to the Log Reference. Log Reference posts require specific formatting. <br>
Special Tags
In addition to standard tagging the following specific tags control the exposure level of the post to various user groups on the support portal.
Guest = Anyone who visits the support portal can view
Level 2 = support techs, Internal and Admins
Internal = L3 and Admins
<br>
Standardized Spellings for Articles
exacqVision Web Service or Web Service – when referring to the product
web service – lowercase, when referring to the generic concept
exacqVision Desktop Client, exacqVision Client, or Client when referring to the product
client – lowercase, when referring a generic concept
Panelless – this always throws a spelling error, but Kantech materials are using two l’s
KT-1 – use dash in product name to match
exacqVision Mobile – new mobile app that replaced previous versions and uses direct server communication
Exacq Mobile 3 – old mobile app, requires web service
Exacq XXXX – use single word with capital E for hardware products
exacqVision XXXX – used when referring to software products
