Invalid Login Credentials

Possible Solution: Try using basic authentication, credentials of admin/admin, and verify that the host address is the IP address of the base server.

The server does not appear to be an ocularis server

Possible Solution: Please check the IP address entered in the host address box, it should that of the Base server.

Possible Solution: If you have the base server and the recording component on the same machine, check the “local port” in the Management Application under server access. If it is set to port 80, change it to something else (e.g. 82 or 8080). Open a command prompt, and type in “iisreset” and hit Enter. Try logging into Administrator again after IIS successfully restarts.

Unable to connect to remote server

Possible Solution: If you have the base server and the recording component on the same machine, check the “local port” in the Management Application under server access. If it is set to port 80, change it to something else (e.g. 82 or 8080). Open a command prompt, and type in “iisreset” and hit Enter. Try logging into Administrator again after IIS successfully restarts.

License for Ocularis Server has not been activated

Possible Solution: Open Ocularis License Activation. Go through the steps to license the Base software.

The remote server returned an error: (401) Unauthorized.

Possible Solution: Verify credentials match that of a user in the Management Application.

Unable to connect to remote server (Ocularis Client)

Possible Solution: Make sure the address you enter is the valid IP address of the recorder/base (a port number may need to be included if recorder is on the same machine as the base (e.g. 192.168.7.189:8080))

MessageSecurityExceptionAn unsecured or incorrectly secured fault was fault was received from the other party. See the inner

Possible Solution: Check the date and time settings on both the client machine and the server you are logging into are within 5 minutes of each other and that the time zone, am/pm, and daylight savings settings are the same as well. You may have to lower UAC settings to ‘Never Notify’ in order to change the time and date.

Heimdall x.x.x.xxx

Possible Solution: You may see this message on a white screen: “Heimdall x.x.x.xxx” either in Ocularis Administrator when trying to edit Maps, or trying to view live video streams in Ocularis Client. This message occurs when the computer does not have enough video memory, and will often happen on remote desktop connections.

The System is low on memory. You should close some feeds to prevent instability.

Possible Solution: If you are running multiple views, try decreasing the number of live views open. For example, if you have a dual monitor setup both running 8x8 views, try running 3x3 views on both. You can also try lowering the resolution and frames per second settings on a camera by camera basis. Please contact support for further assistance.

Error Logging in to NVR: The remote server returned an error: (401) Unauthorized.

Possible Solution: Verify credentials match that of a user in the Management Application.

Unable to auto-detect any known NVRs at the specified host.

Possible Solution: Verify correct IP address and port of the recording server.

All sources for this server have been detected. Server not added. Check Master/Slave configurations

Possible Solution: There must be a minimum of one hardware device added into the Management Application (recorder) in order to add the recorder into Administrator.

Event Coordinator Service is not running

Possible Solution: Click on the Start Menu, then click Run, and type in: services.msc . Locate the service called OnSSI Event Coordinator Service. Right-click on the service and click Restart. After the service restarts successfully, try adding your recorder again.

Unable to update server: an item with the same key has already been added

Possible Solution: In the Management Application, you will need to verify that the Microphone or Speaker listed as the Audio device is not duplicated with another camera. Right click on the heading 'Cameras and Storage Information' heading under Advanced Configuration, then click Properties. In here select 'Audio Selection' on the left side and check the Default Microphone and Default Speaker column. If you find a duplicated name anywhere, set the value to '' in the drop-down menu, click OK, then go File> Save Changes and Restart Services. After the recorder starts back up, when you go to refresh/update the server in Administrator, the server will now update successfully.

Warning: Please restart recording server service before replacing the device." - RC-C/I/P 8.0

Possible Problem: There may be some commands the recording server is trying to run on that particular hardware device (renaming a folder, deleting an old archive, etc..) but for one reason or another are "hanging". This will not allow you to "replace" that device until the hung commands are purged.

Possible Solution: 1) First stop the recording server service. 2) In My Computer go to: C:\Documents and Settings\All Users\Application Data\OnSSI\RC-C/I/P\dbcommands (server 2003) or C:\Program Files (x86)\OnSSI\RC-C/I/P\dbcommands (server 2008, win 7) 3) Make a copy of this "dbcommands" folder, and place it somewhere (desktop, onssi directory, wherever for safe keeping...) Select any and all files in this folder, and delete them. Once all commands are deleted, start the recording server service again. 4) Open the Management Application, and try the "replace hardware" wizard again. You should be able to use the wizard now.

Nothing happens when updating Base License

Possible Solution: Open a web browser, type in address box: http://localhost:1947 hit Apply/Update tab on left side, browse to .v2c file, click Apply. It should apply successfully and the camera count updated in the license activation window.

Error while importing V2C

Possible Solution: Make sure you are logged into your computer with an account that has administrative privileges, and User Account Control is set to “Never Notify” (if on a Win7 or Server 2008 operating system)

Error updating Server License Key. KeyIdNotFound

Possible Solution: Generate a new c2v in license activation program. Submit it to us. Keep your license activation window open and do not restart and/or shutdown your computer while waiting for us to send you an updated v2c file. Try updating the license now.

Error updating Server License Key. UpdateTooNew

Possible Solution: There was a v2c file sent to you previously that needs to be attached before the one you are trying to update now.