This KB article applies to PC Based DVRs utilizing analog capture cards.
Issue:
I see a Data Compress Error in the Server log.
Cause:
The DSP chip(s) on the capture card is experiencing issues with compressing the video streams.
Solution:
Replace the capture card.

This KB article applies to running the Client Application on Windows Vista/7 and Windows XP.
Issue:
I input all the proper configuration information into the Client Setup. I Exit the Client Application and open it back up again by using the Client shortcut icon on the Windows Desktop. All of the configuration information is now gone.
Cause:
1) Even though the current Windows User is part of the Administrator Group, the current Windows User is not the Administrator. (Windows Vista/7)
2) The current Windows User does not have write access to the Config Files folder. Each time the Client Application is configured the data is stored in a memory overlay that is flushed when the Client.exe process is ended. (Windows XP)
3) A different Windows User installed the Client application. (Windows XP)
Solution:
1) Right-click the Client shortcut icon on the Windows Desktop and select Properties. Move to the Compatibility tab. Check the 'Run this program as an administrator' check box. Click Apply and Ok.
2) Have the network administrator install the Client application for you.
3) Uninstall and than re-install the Client application.

This KB article applies to DVR Server application startup.
Issue:
When the DVR Server application starts up I see a 'System Registration Failed' message or a Notice window.
Cause:
The DVR Server application has scanned the REG folder for all *.dat files and was unable to decrypt a matching serial number. Pre x.8.0616 versions utilize a 128bit encryption registration system and will have a separate registration file for Standard, Professional, and Enterprise. Versions after x.8.0616 utilize a 512bit encryption registration system and has a single registration file for all three platforms.
Solution:
Update the registration file to the latest version available. If 'System Registration Failed' persists, re-registration may be necessary.

This KB article applies to both the DVR Client and DVR Server applications. You will need to be at the DVR Server for proper troubleshooting.
Issue:
I cannot connect with the DVR Client application. I get various message boxes.
Cause:
Various causes.
Solution:
You must have the same version Client as the DVR Server is running. Use the Extra button to determine what version you are running.
Start by unlocking the DVR Server application with the Supervisor username. This will verify that the correct Supervisor password is used for the following tests.
Loopback Test:
Open the DVR Client application on the DVR Server itself. Go into Setup -> Connection tab -> Server Setup. Configure Server(01) with 127.0.0.1 as the IP address. Use Supervisor for the username. Save the changes. Connect to all channels. If the connection is successful move to LAN Test. This tells us that the settings on the DVR Server are acceptable for Client connection. If the connection fails there is a setting in the DVR Server application that is preventing you from connecting. Hide the DVR Client application and restore the DVR Server application. Go into Setup and verify the following: Connection tab -> Allow Network Access check box is checked for each camera. Schedule tab -> Allow Network Access tab -> Activate Schedule check box is checked and 00:00 - 23:59 for the Time Period column is displayed for all days. Environment tab -> Enable Client Connection check box is checked. Environment tab -> Network Ports button -> Server Message should be 8000. Disable firewall, disable anti-virus. Retry Loopback Test.
LAN Test:
Open the DVR Client application on the DVR Server itself. Go into Setup -> Connection tab -> Server Setup. Configure Server(01) with the LAN IP address of the DVR Server. Use Supervisor for the username. Save the changes. Connect to all channels. If the connection is successful move to WAN Test. This tells us that the local network are acceptable for Client connection. If the connection fails there is a local network setting in the DVR Server that is preventing you from connecting. Check TCP/IP configuration, disable firewall, disable anti-virus, check network cabling. Retry LAN Test.
WAN Test:
Note - Some ISPs block recursive traffic. This means that you are unable to use the WAN IP inside the same network. In this case please test offsite. Open the DVR Client application on the DVR Server itself. Go into Setup -> Connection tab -> Server Setup. Configure Server(01) with the WAN IP address of the ISP's modem. Use Supervisor for the username. Save the changes. Connect to all channels. If the connection is successful everything is working. If the connection fails there is a device that is blocking the packets. Verify that you have forwarded port 8000 through any router(s) to the DVR Server's IP address. Verify that you have the correct WAN IP address. Verify that the DVR Server has internet access by googling TNZ Technologies. Change the Server Message port in the DVR Server application, DVR Client application, and any router(s). Disable firewall, disable anti-virus. Retry WAN Test.

This KB article applies to DVR Server application startup.
Issue:
When the DVR Server application starts up I see a 'System Initialization Failed' message. I click Ok and the DVR Server application closes.
Cause:
The DVR Server application is not detecting any and/or detecting a faulty encoding device. An encoding device includes capture cards, IP cameras, and standalone DVRs.
Solution:
Re-install capture card drivers and reboot Windows. Check the Video Device Definitions (VideoDeviceDEF.exe) for accurate configuration information. If using multiple capture cards try each capture card one at a time in a known good PCI slot to find the bad capture card.

This KB article applies to DVR Server application startup.
Issue:
When the DVR Server application starts up I see a 'Disk Group(01) Does Not Have Enough Free Space' message. I click Ok and the DVR Server applications loads just fine but the Recording Status Indicator Lights are all red.
Cause:
The DVR Server application did not detect any available basic NTFS partitions other than C:\. The C:\ partition (OS partition) is not suitable for storing video and has been locked out.
Solution:
Create and format a basic NTFS partition and restart the DVR Server application. You may also map a location to a drive letter on the DVR and record to that drive.

This KB article applies to the DVR Client application.
Issue:
I can connect, as indicated by the green connection indicator light, but instead of displaying the Live Video all I see is solid black.
Cause:
You have outdated video drivers or have not selected the correct Device Type to install during the Client installation.
Solution:
Update the video drivers to the latest released version according to the manufacturers instructions. Reinstall the Client application and ensure that you have selected the Device Type that corresponds to your video encoding device, you may also select all Device Types.

This KB article applies to PTZ camera cruising on the DVR Server.
Issue:
When I activate the Cruise on a PTZ camera it seems to skip PTZ Cruise Points.
Cause:
The number of seconds set for the PTZ Cruise Point is an insufficient amount of time for the PTZ camera to pan/tilt/zoom to the PTZ Cruise Point before the command is sent from the DVR Server to the PTZ camera to move to the next PTZ Cruise Point.
Solution:
Increase the Staying Time for the PTZ Cruise Point(s).

This KB article applies to inserting a Backup CD into another Windows based PC.
Issue:
I inserted a Backup CD into another Windows based PC and nothing happens. Isn't it supposed to Autoplay?
Cause:
1) Autoplay has been disabled.
2) You are not on a Windows based PC with a supported optical drive.
Solution:
1) Run the AutoFix.exe provided by Microsoft to re-enable Autoplay.
2) Insert the Backup CD into a Windows (Windows 2000, Windows XP, Windows Vista) based PC with a supported optical drive.

This KB article applies to Windows operating systems with the latest Service Pack installed.
Issue:
Windows does not automatically login even though Auto Administrator Login When Windows Is Started is checked.
Cause:
The latest Service Packs have additional changes to the way Windows operating systems login. Never check or uncheck the Auto Administrator Login When Windows Is Started check box in the DVR Server application.
Solution:
Never check or uncheck the Auto Administrator Login When Windows Is Started check box in the DVR Server application. Always configure the automatic Windows login before the DVR Server software is installed. Uninstall all DVR Server installations. If in Windows XP run 'user controlpasswords2'. Go to the Advanced tab and ensure Require Users To Press Ctrl+Alt+Del is unchecked. Go to the Users tab and check the only check box. Highlight the desired user under the User Name column. Uncheck the only check box and select Apply. Another window asking for a password will popup. If you have a password type it in here, if you do not have a password leave the field blank and select Ok. If Windows XP still does not automatically login re-install Windows XP and be sure never to check or uncheck the Auto Administrator Login When Windows Is Started check box in the DVR Server application.

This KB article applies to a DVR Server with an MD card.
Issue:
I have configured the MD card by first selecting the Public View square (where I want to show) and then by selecting the video channel (what I want to show) but I see a blue square instead of a video channel on one/multiple Public View squares.
Cause:
You are trying to display the same channel twice at the same time. The MD card is a hardware decoder that can process a single stream per video channel.
Solution:
By default each Public View square is configured to display the corresponding video channel number, ex: Public View 01 will display CH-01. When switching Public View 01 to display CH-02 you must also switch Public View 02 to display a different video channel since by default Public View 02 is also displaying CH-02. It is recommended to set Public View 02 to CH-01 since we just reassigned Public View 01 that by default shows CH-01 which was just reassigned. Simply reverse the two video channels that the corresponding Public View squares are showing.

This KB article applies to DVR Server verions x.9.0716 or higher.
Issue:
Each time I run Server.exe nothing happens. If I look at the Windows Task Manager I see that Server.exe opens for a few seconds and then closes. There are no error messages.
Cause:
You have selected a card type other than the currently installed capture card. The DVR Server application supports many different types of capture cards and can even run as a DVS.
Solution:
Open up DVSDef.exe. Select the Card Type Define button. Select appropriate supported capture card type from the list. Save these changes and restart Server.exe.

This KB article applies to DVR Servers.
Issue:
Various issues including but not limited to scheduling issues, recording issues and Client issues.
Cause:
The configuration file has errant data embedded into it and therefore cannot properly assign DVR Setup parameters.
Solution:
To identify a corrupt configuration file go to the Color/Motion tab and select the Time Schedule button. Select Scheme1. You will see all zeros (00) for all Time Period drop down boxes. To fix simply delete the Config Files folder in the DVR Server installation directory and import your saved config file and user file.

This KB article applies to the remote control that comes packaged with the 16ch Embedded DVR Servers.
Issue:
The remote control that came with this 16ch Embedded DVR Server doesn't seem to work at all.
Cause:
The remote control has not been paired with the 16ch Embedded DVR Server.
Solution:
Ensure that you have charged batteries in the remote control. Point the remote control directly at the 16ch Embedded DVR Server. Press the DEV button on the top right of the remote control. Then press the 8 button twice. If successful the Status LED on the front of the16ch Embedded DVR Server will turn green. After the Status LED has turned green the remote control has been paired.

This KB article applies to all PC based DVR Servers.
Issue:
After the last power outtage/power fluctuation the DVR Server no longer powers on.
Cause:
Most modern PSUs have integrated safety features. When the PSU senses a voltage issue (ie: voltage fluctuation) the PSU will disable itself to prevent damage to itself and any device powered by the PSU. The PSU, if unprotected by a properly sized APC unit, may be fried.
Solution:
To reset the integrated safety features you must remove the PSU grounding circuit. Unplug the power cable from the PSU for several minutes and plug it back in. If the PSU has been fried, replace the PSU.

This KB article applies to DVR Server Live Preview.
Issue:
When watching the Live Preview in Single Screen mode the video is solid green.
Cause:
The graphics system is unable to properly render the video overlay used for the Single Screen Live Preview.
Solution:
Update to the video card manufacturer's latest driver version. Your video card may not support video overlays on the primary or secondary monitor - check video card driver settings or change hardware.

This KB article applies to all PC based DVR Servers.
Issue:
I receive an error message that says 'Server.exe has encountered a problem and must close'. After I click OK or Do Not Send I see the Windows Desktop.
Cause:
You have a software conflict or bad hardware.
Solution:
Preface: always be sure to run the latest version of the Unisight software.
Un-install and re-install the Unisight software, this will eliminate the possibility of a configuration setting causing the issue. To resolve a software conflict format the Operating System drive and re-install Windows along with any drivers and the Unisight software. Do not use any recovery partitions to re-install Windows, these recovery partitions are customized by the PC manufacturer and may have incompatible settings/software that is restored with the OS. If the issue continues troubleshoot PC hardware. Start with examniing the Windows Event Viewer System and Application logs for hardware issues, then move on to swapping the hardware components with known working components.

This KB article applies to all UNI-HK IP based devices including Embedded DVRs, IP Cameras, and DVS units.
Issue:
I cannot change the network configuration on my IP Device.
Cause:
All IP Devices come preconfigured for a single network configuration that is likely different than your network configuration.
Solution:
To determine/change the IP address of your device run the SADP program and select the Enter button. You will see another window popup that will display all IP Devices even if they are on a different subnet. Select the desired IP Device and click the Modify button. You can now set the subnet mask, IP address, and device port. You will also need to enter in '12345' for the password. After choosing the Save button you can now close the SADP software. Be sure to restart the IP Device if any changes were made.

This KB article applies to all UNI-HH IP based devices including Embedded DVRs, IP Cameras, and DVS units.
Issue:
I cannot change the network configuration on my IP Device.
Cause:
All IP Devices come preconfigured for a single network configuration that is likely different than your network configuration.
Solution:
To determine/change the IP address of your device run the SearchNVS program and select the Search button. After the progress bar fills in it will display all IP Devices even if they are on a different subnet. Select the desired IP Device and click the Set button. You can now set the subnet mask, IP address, DNS, and device port. You will also need to enter in 'admin' for the password. After choosing the OK button you can now close the SearchNVS software. Be sure to restart the IP Device if any changes were made.

This KB article applies to all PC based DVR Servers.
Issue:
I get a System Clock Not Logical error message followed by a System Initialization Failed error message. After I click OK the Server application closes.
Cause:
The System Time has been tampered with and has been changed outside of the DVR Server application.
Solution:
Do not change the System Time outside of the DVR Server application. Please note: This is sometimes unavoidable and you must change the System Time outside of the DVR Server application. The System Clock Not Logical error message only happens the first time the DVR Server application is started after the the time has changed. Simple start the DVR Server application again.

This KB article applies to all PC based DVR Servers.
Issue:
I get a Please Check Alarm or PTZ Device Setting! error message when the DVR Server application starts. The Server software does not load, and does not record, until I click OK.
Cause:
The DVR Server application has a configuration for a device that uses a COMM port but the device cannot be found.
Solution:
Check for correct settings for the Watchdog, Current Alarm Device, Matrix, PTZ Camera(s) and Short Message. If error message persists use the Reset.exe to clear all settings and re-configure DVR Server application.

This KB article applies to all PC based DVR Servers.
Issue:
I press Ctrl-Alt-Del to get to the Task Manager but it has been disabled. I right-click the Windows Task Bar and select Task Manager but it has been disabled. I go to Start->Run->taskmgr but it has been disabled.
Cause:
Leaving the Windows Task Manager enabled is a security risk that would allow unauthorized personnel to stop the DVR Server from recording. Task Manager is disabled by the Server.exe process.
Solution:
Go to Start -> Run -> gpedit.msc. Expand User Configuration -> Administrative Templates -> System -> Ctrl+Alt+Del Options. Double-click Remove Task Manager. Select the Enabled radio button, now select the Disabled radio button. Apply the changes.

This KB article applies to all PC based DVR Servers with a generation 1 Watchdog unit installed.
Issue:
I do not see a green 'Active' LED on the Watchdog.
Cause:
You have a faulty Watchdog cable or incorrectly connected Watchdog cable. You have an invalid configuration.
Solution:
Use a known working Watchdog cable. Connect the Watchdog cable to the top serial port on the Watchdog. Connect the other end of the Watchdog cable to the serial port on the motherboard. In the DVR Server application go to Setup -> Advanced. Set the Watchdog drop down box to Taichen. Select the Setup button next to Watchdog. Set the COMM to either COMM1 or COMM2. Set the Baud Rate to 9600. Set the Parity to none. Apply the settings.

This KB article applies to all PC based DVR Servers with a generation 2 Watchdog unit installed.
Issue:
I do not see a blue 'Active' LED on the Watchdog.
Cause:
The DIP switch is incorrectly configured. You have a faulty Watchdog cable or incorrectly connected Watchdog cable. You have an invalid configuration.
Solution:
Set the DIP so that switch 1 is on and the rest are off. Use a known working Watchdog cable. Connect the Watchdog cable to the bottom of the Watchdog. Connect the other end of the Watchdog cable to the serial port on the motherboard. In the DVR Server application go to Setup -> Advanced. Set the Watchdog drop down box to MyTech. Select the Setup button next to Watchdog. Set the COMM to either COMM1 or COMM2. Set the Baud Rate to 9600. Set the Parity to none. Apply the settings.

This KB article applies to all PC based DVR Servers.
Issue:
Even though I have unlocked the DVR Server using the Supervisor account the Playback button is grayed out and I cannot watch Playback.
Cause:
The DVR Server application is re-indexing the recording files.
Solution:
Ensure that you have Auto Re-index Recording Files unchecked in the DVR Server Setup under the the Environment tab. Exit the DVR Server application. Start the DVR Server application.

This KB article applies to all PC based DVR/NVR/HVR Servers.
Issue:
I see the system POST, I see the OS loading screen, but then the monitor goes black.
Cause:
The monitor does not support the current resolution and/or refresh rate.
Solution:
Enter the OS Boot Options by pressing F8 during startup. Select Enable VGA Mode. Once the system starts you can set your desired resolution and refresh rate according to your monitor's supported settings.

This KB article applies to all PC based DVR/NVR/HVR Servers.
Issue:
I see Not Enough Memory, Record Warning or Record Error entries in the Server Log.
Cause:
The Server.exe is not able to save the buffered video data to the HDD. This can be caused by many situations including a fragmented HDD, bad HDD, slow HDD, etc.
Solution:
Do not allow the HDD's file structure to become fragmented, replace any fualty HDDs, if writing to a network drive (such as a NAS or a SAN) increase the throughput to the network drive or use load balancing techniques, set SATA controller to AHCI mode.

This KB article applies to all PC based DVR/NVR/HVR Servers.
Issue:
I want to store the recorded video for extended periods of time, example: 6 months.
Cause:
The bitrate of the recorded video has increased expnentially due to MegaPixel cameras becoming standard, example: 16 MegaPixel cameras may take 20tb of space for 2 months of video.
Solution:
In order to store recorded video for that long you will need a high capacity NAS or SAN.

This KB article applies to all PC based DVR/NVR/HVR Servers.
Issue:
I get a No Remote Access Right message when connecting to Live View or Playback using the Client.
Cause:
Your system is not registered. Your username/password are incorrect or do not have the proper permissions. You have a version mismatch.
Solution:
Properly register the system. Input the correct username/password or use the Supervisor account. Ensure that the Client version matches the version that is running on the Server.

This KB article applies to all PC based DVR/NVR/HVR Servers.
Issue:
I get a Microsoft Visual C++ Error on the Server.
Cause:
There is a missing or corrupt file somewhere within the system. Possible causes for data corruption include a bad HDD, bad SATA cable, bad SATA controller, etc.
Solution:
Always be sure that there are no hardware issues with the system beore troubleshooting this error. Re-install vcredist.exe. Re-install the Server software. Re-install the OS.

This KB article applies to the SADP software.
Issue:
I set the IP address of the IP device using SADP and can ping it but I cannot to the IP device using the Unisight software.
Cause:
The SADP software does not support setting the default gateway.
Solution:
You will need to set the default gateway through the web configuration interface for UNI-HK devices.