Month: February 2024

Categories
Knowledge Support Support exacqVision Client exacqVision Server exacqVision Webservice Categories

HTTP Response Code Reference

Code Description Definition Exacq Tips
Informational
100 Continue Server received request, client should continue.
101 Switching Protocols Response to upgrade header
102 Processing Server processing received request.
103 Early Hints Used with link header.
Allows browser to preload resources.
Successful
200 OK Standard response for successful request.
Meaning varies based on method (GET, POST, etc).
201 Created New resource successfully created.
Usually in response to PUT or POST request.
202 Accepted Request accepted but still in progress.
203 Non-Authoritative Info Data returned isn’t from the origin server.
Modified data from third-party.
204 No Content Request successful but there is no content.
205 Reset Content Request successful, server asked to reset doc.
206 Partial Content Server delivered part of the resource.
Used with range header.
207 Multi-Status Provides status of multiple resources with sub-requests.
208 Already Reported Members of element already reported.
226 IM Used Server completed GET request.
Redirection
300 Multiple Choices Request has more than one possible response.
User should choose one.
301 Moved Permanently Requested resource has permanently moved
to a new URL.
302 Found Requested resource temporarily moved to new URL.
303 See Other Server redirects user to requested resource
with GET request to another URL.
304 Not Modified Used for caching. Response unmodified so client can use cached version of resource.
307 Temporary Redirect Requested resource temporarily moved to new URL.
308 Permanent Redirect Requested resource permanently moved to new URL.
Client Error
400 Bad Request Server can’t or won’t process request due to client error.
401 Unauthorized User doesn’t have valid credentials to get requested
resource.		 Invalid username or password
403 Forbidden Client doesn’t have access rights to content.
Unlike 401, the server does know client’s identity.
404 Not Found Server can’t find requested resource. No redirection set. Request Not Found
The device didn’t understand the request.
May be caused by untested device or firmware.
405 Method Not Allowed Server supports request method, but target doesn’t.
406 Not Acceptable Server doesn’t find content satisfies criteria given by user.
407 Proxy Authentication Required Similar to 401, but proxy must authenticate to client.
408 Request Timeout Server times out because client didn’t issue request
in a timely manner.
409 Conflict Server can’t fulfill request due to conflict with resource.
410 Gone Requested content has been removed.
411 Length Required Server rejection becauce it requires defined
content-length header field.
412 Precondition Failed Client has precondition headers the server does not meet.
413 Payload Too Large Client request larger than server limits, so server
refuses to process request.
414 URI Too Long Requested URI is too long for server to process.
415 Unsupported Media Type Request uses media format unsupported by server.
416 Range Not Satisfiable Server can’t fulfill value in request’s range header.
417 Expectation Failed Server can’t meet requirements of expect header in request.
421 Misdirected Request Request made to server that can’t produce response.
422 Unprocessable Content Server unable to process request due to semantic errors.
423 Locked Requested resource method is locked to be inaccessible.
424 Failed Dependency Request failed because a previous request it is dependent on also failed.
425 Too Early Server is unwilling to process request that may be delayed.
426 Upgrade Required Server refuses request using current protocol version.
428 Precondition Required Server needs request to be conditional.
429 Too Many Requests User has sent too many requests within allotted time.
431 Request Header Fields Too Large Server can’t process request because headers are too large.
451 Unavailable For Legal Reasons Server can’t legally provide requested resource.
Server Error
500 Internal Server Error Server encountered unexpected error and cannot
complete the request.		 Device reporting an error.
The device has reported that it has encountered an error.
501 Not Implemented Server doesn’t recognize the request method.
502 Bad Gateway Server acts as a gateway and gets invalid response from inbound host.
503 Service Unavailable Server is unable to process request.
Often occurs if server is overloaded or down.		 Device Unavailable.
The device is currently unable to process this request.
504 Gateway Timeout Server acting as a gateway or proxy has timed out
waiting for response.
505 HTTP Version Unsupported Server doesn’t support the version of HTTP request.
506 Variant Also Negotiates Server has internal configuration error.
507 Insufficient Storage Server can’t process request because it doesn’t
have enough storage space.
508 Loop Detected Server detected infinite loop while processing request.
510 Not Extended Further extensions required for request.
511 Network Authentication Required Client needs to gain network access.

<br>

Categories
Knowledge Support Cloudvue Cloudvue Cameras Support Categories Products

Adding SCP to Illustra Essentials C2C Cameras

Description 

Illustra Essential cameras were manufactured by Topview and do not include scp (Secure Copy Protocol).  As a result, files cannot be easily transferred to or from the device.  The debug.sh script can be used to temporarily install scp onto the device enabling up/downloading of files.  While scp will not survive a reboot the debug script, debug.sh does and can be used to quickly add scp as needed.

Product 

  • Illustra Essential
  • Cloudvue C2C

Prerequisites

  • Confirm the device is a Topview manufactured camera
  • Verify that debug.sh does not already exist in /home/smartvue
  • Download the debug.sh script from the support portal HERE
  • Open the debug script in Notepad++ on your machine
  • Establish an ssh session via the Cloudvue Tunneling server to the camera

Solution

Identifying a Topview Camera

The  most common ways to identify Topview manufactured cameras are: 

  • In Cloudvue Manager (Device Details > Firmware Version) look for “Essentials”
  • Check the architecture, Topview  cameras use the MIPS architecture which can be found using the uname command on the device. 
  • </code># uname -a<br>Linux Essentials4-T10A212700003131 4.1.0 #6 PREEMPT Thu Nov 24 09:54:36 CST 2022 mips GNU/Linux</code>

Creating the Debug Script

Since there is no way to initially transfer the debug script to the device it will need to be manually created.  This is done by cutting and pasting the contents of the script from your machine to a new debug script file on the camera.  Please note the only text editor available on these devices is vi.

  • On the camera launch vi with the name of the script
  • <code># vi debug.sh</code>
  • Paste from Notepad++
    • Within vi
    • Press lowercase letter “o” to insert a line below the current line and go into edit mode
    • Press the up arrow key to move to the 1st line
    • Paste the entire contents of the debug.sh file from notepad++ on your machine to vi
    • Note: It will take some time for the paste to complete and it will occasionally pause.
  • Verify Accuracy
    • When the paste has completed verify that the last lines from Notepad++ match those pasted in vi
    • Failure – Last Line Does Not Match
      • Press the “esc” Escape key to exit “insert Mode”
      • Type “:q!” and press enter to force quit without saving any changes ‘
      • Attempt creating the debug script again
    • Success – Last Lines Match
      • Press the “esc” Escape key to exit “insert Mode”
      • Type “:wq” and press enter to open a vi command prompt, write the changes to file and quit vi

Running debug.sh

Before running the first time debug.sh must be made executable using the chmod command.

<code># chmod +x debug.sh</code>

  • Now Launch the script by proceeding the file name with “./”.  If all went well with the creation process debug.sh will run and a menu of choices will be displayed.
  • <code> # ./debug.sh <br>CHOICES:<br>0. print [h]elp<br>1. debug <br>[m]essaging<br>2. debug [r]ecorder<br>3. [R]estart camera or services<br>4. [i]nstall scp on Essentials<br>5. [q]uery iAPI<br>6. print/update [e]nvironment<br>7. [o]pen firmware logs<br>8. run [v]ideo sync<br>9. pretty-print [j]son<br>10. query camera re[b]oots<br>11. query local [d]atabase<br>12. bundle [l]ogs<br>Please select an option: 4<br>#</code>
  • Select option 4 and press enter to install scp on Essentials.
  • When successful no message is returned and debug.sh will terminate.
  • If scp is already installed the message “”scp already exists in path. Cancelling scp install…”” will be displayed and debug.sh will terminate.
  • Installation of scp can be confirmed using the which command.
  • <code># which scp<br>/bin/scp</code>

scp has now been successfully installed and files can be transferred using scp or other tools such as MobaXterm.

Categories
User Guides Documentation Categories exacqVision Hardware Products

ASRock Industrial IMB-X1314 System Beep Codes

Beep SequenceDescriptionTroubleshooting
1 short constant beepError with RAM refresh1. Check RAM for physical damage.
2. Try another stick of RAM.
3. BIOS update
2 short beepsRAM parity error1. If adding new memory, try removing to see if this fixes issue.
2. Check for conflicts in memory types.
3. Check power supply for unstable voltages.
3 short beepsRAM read/write test failed1. Repair corrupted files.
2. Perform memory tests
4 short beepsSystem clock errorTry synchronizing system time with an internet (NTP) time source.
5 short beepsCPU errorCheck that CPU is properly seated.
6 short beepsKeyboard not detected/
keyboard controller error		Check keyboard is properly connected or try a different keyboard.
7 short beepsGeneral CPU or RAM error1. Check that CPU is properly seated and connected.
2. Check that RAM is properly seated and connected.
3.Inspect connections for dirt or corrosion.
8 short beepsGraphics controller errorCheck for proper connections to any graphics cards installed and that enough power is provided to the card.
9 short beepsROM errorCheck if system is attempting to boot from an external device.
10 short beepsROM read/write error1. Run a memory diagnostic, such as mdsched.exe in Windows.
2. Clear CMOS
11 short beepsCPU cache check failure1. Check CPU temperature.
2. Inspect CPU fan for proper function.
3. Clear dust or dirt from CPU fan.
4. Check for faulty CPU heatsink.

<br>

Categories
User Guides Documentation Categories exacqVision Hardware Products

ASRock Industrial IMB-X1313 System Beep Codes

Beep SequenceDescriptionTroubleshooting
1 short constant beepError with RAM refresh1. Check RAM for physical damage.
2. Try another stick of RAM.
3. BIOS update
2 short beepsRAM parity error1. If adding new memory, try removing to see if this fixes issue.
2. Check for conflicts in memory types.
3. Check power supply for unstable voltages.
3 short beepsRAM read/write test failed1. Repair corrupted files.
2. Perform memory tests
4 short beepsSystem clock errorTry synchronizing system time with an internet (NTP) time source.
5 short beepsCPU errorCheck that CPU is properly seated.
6 short beepsKeyboard not detected/
keyboard controller error		Check keyboard is properly connected or try a different keyboard.
7 short beepsGeneral CPU or RAM error1. Check that CPU is properly seated and connected.
2. Check that RAM is properly seated and connected.
3.Inspect connections for dirt or corrosion.
8 short beepsGraphics controller errorCheck for proper connections to any graphics cards installed and that enough power is provided to the card.
9 short beepsROM errorCheck if system is attempting to boot from an external device.
10 short beepsROM read/write error1. Run a memory diagnostic, such as mdsched.exe in Windows.
2. Clear CMOS
11 short beepsCPU cache check failure1. Check CPU temperature.
2. Inspect CPU fan for proper function.
3. Clear dust or dirt from CPU fan.
4. Check for faulty CPU heatsink.

<br>

Categories
User Guides Documentation Categories Products exacqVision Hardware

ASRock H410 System Beep Codes

Beep SequenceDescriptionTroubleshooting
1 short constant beepError with RAM refresh1. Check RAM for physical damage.
2. Try another stick of RAM.
3. BIOS update
2 short beepsRAM parity error1. If adding new memory, try removing to see if this fixes issue.
2. Check for conflicts in memory types.
3. Check power supply for unstable voltages.
3 short beepsRAM read/write test failed1. Repair corrupted files.
2. Perform memory tests
4 short beepsSystem clock errorTry synchronizing system time with an internet (NTP) time source.
5 short beepsCPU errorCheck that CPU is properly seated.
6 short beepsKeyboard not detected/
keyboard controller error		Check keyboard is properly connected or try a different keyboard.
7 short beepsGeneral CPU or RAM error1. Check that CPU is properly seated and connected.
2. Check that RAM is properly seated and connected.
3.Inspect connections for dirt or corrosion.
8 short beepsGraphics controller errorCheck for proper connections to any graphics cards installed and that enough power is provided to the card.
9 short beepsROM errorCheck if system is attempting to boot from an external device.
10 short beepsROM read/write error1. Run a memory diagnostic, such as mdsched.exe in Windows.
2. Clear CMOS
11 short beepsCPU cache check failure1. Check CPU temperature.
2. Inspect CPU fan for proper function.
3. Clear dust or dirt from CPU fan.
4. Check for faulty CPU heatsink.

<br>

Categories
User Guides Documentation Categories Products exacqVision Hardware

ASRock C236M WS System Beep Codes

Beep SequenceDescriptionTroubleshooting
1 short constant beepError with RAM refresh1. Check RAM for physical damage.
2. Try another stick of RAM.
3. BIOS update
2 short beepsRAM parity error1. If adding new memory, try removing to see if this fixes issue.
2. Check for conflicts in memory types.
3. Check power supply for unstable voltages.
3 short beepsRAM read/write test failed1. Repair corrupted files.
2. Perform memory tests
4 short beepsSystem clock errorTry synchronizing system time with an internet (NTP) time source.
5 short beepsCPU errorCheck that CPU is properly seated.
6 short beepsKeyboard not detected/
keyboard controller error		Check keyboard is properly connected or try a different keyboard.
7 short beepsGeneral CPU or RAM error1. Check that CPU is properly seated and connected.
2. Check that RAM is properly seated and connected.
3.Inspect connections for dirt or corrosion.
8 short beepsGraphics controller errorCheck for proper connections to any graphics cards installed and that enough power is provided to the card.
9 short beepsROM errorCheck if system is attempting to boot from an external device.
10 short beepsROM read/write error1. Run a memory diagnostic, such as mdsched.exe in Windows.
2. Clear CMOS
11 short beepsCPU cache check failure1. Check CPU temperature.
2. Inspect CPU fan for proper function.
3. Clear dust or dirt from CPU fan.
4. Check for faulty CPU heatsink.

<br>

Categories
User Guides Documentation Categories Products exacqVision Hardware

ASRock H110-E1 System Beep Codes

Beep SequenceDescriptionTroubleshooting
1 short constant beepError with RAM refresh1. Check RAM for physical damage.
2. Try another stick of RAM.
3. BIOS update
2 short beepsRAM parity error1. If adding new memory, try removing to see if this fixes issue.
2. Check for conflicts in memory types.
3. Check power supply for unstable voltages.
3 short beepsRAM read/write test failed1. Repair corrupted files.
2. Perform memory tests
4 short beepsSystem clock errorTry synchronizing system time with an internet (NTP) time source.
5 short beepsCPU errorCheck that CPU is properly seated.
6 short beepsKeyboard not detected/
keyboard controller error		Check keyboard is properly connected or try a different keyboard.
7 short beepsGeneral CPU or RAM error1. Check that CPU is properly seated and connected.
2. Check that RAM is properly seated and connected.
3.Inspect connections for dirt or corrosion.
8 short beepsGraphics controller errorCheck for proper connections to any graphics cards installed and that enough power is provided to the card.
9 short beepsROM errorCheck if system is attempting to boot from an external device.
10 short beepsROM read/write error1. Run a memory diagnostic, such as mdsched.exe in Windows.
2. Clear CMOS
11 short beepsCPU cache check failure1. Check CPU temperature.
2. Inspect CPU fan for proper function.
3. Clear dust or dirt from CPU fan.
4. Check for faulty CPU heatsink.

<br>

Categories
User Guides Documentation Categories exacqVision Hardware Products

Asus Q87-MA System Beep Codes

Beep SequenceDescriptionTroubleshooting
One short beepNormal boot
One short beep, nothing displays on monitorNormal bootCheck that the monitor is functioning and connected correctly.
Power light is ON, no beepHardware issueCheck that the CPU and memory are installed correctly and there is no corrosion or dirt on the connections.
One continuous beep followed by two short beeps, then a pause (repeating)No memory (RAM) detected1. Confirm the memory is correctly installed.
2. Remove and reseat the memory.
3. Try isolating problem RAM by testing each stick of RAM individually, removing the other.
4. Try swapping suspect RAM with known working RAM.
One continuous beep followed by three short beepsNo VGA detectedIf the graphic card needs additional power supplied, ensure the power supply can provide enough wattage.
One continuous beep followed by four short beepsHardware component failure – CPU Fan Error, CPU Over Temperature, CPU Over Voltage1. Check that the CPU fan is installed correctly.
2. Check that the CPU fan is free to spin.
3. If still failing, enter BIOS to load default BIOS settings or clear CMOS before trying again.

<br>

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

Can I Update My PostgreSQL Database?

Only the version of PostgreSQL installed by the Enterprise Manager installer is supported.

<br>

The exacqVision Enterprise Manager application provides a PostgreSQL installation to store Enterprise Manager data by default.

The PostgreSQL Global Development Group may offer application updates that are not yet included within the ExacqVision Enterprise Manager installer. At times, users will seek to upgrade to the very latest version of PostgreSQL.

Updating the PostgreSQL database application independently from Enterprise Manager updates may break your Enterprise Manager operation and/or result in lost data. Changes made between versions of PostgreSQL and Enterprise Manager have not been tested. Only the version of PostgreSQL installed by the Enterprise Manager installer is supported.

<br>

Categories
exacqVision Enterprise Windows exacqVision Enterprise Other Knowledge Support Support exacqVision Enterprise Categories Products

Can’t reinstall the EM server

When uninstalling Exacq EM server version 23.06 or above and reinstalling it again on the Windows unit, It will not complete the installation and ask to close the open session even if no sessions are open.

Root cause

The root cause of this issue is The Microsoft Open Database Connectivity (ODBC) that was not removed when uninstalling the EM server software

Solution

Uninstall the ODBC, reboot the Windows machine, and install the EM server again.