Tag: Error

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
exacqVision Server Linux Knowledge Support Support exacqVision Server Categories Products

Server 23.09 Fails to Run on Ubuntu 14.04 x86

Description

Users with Ubuntu 14.04 x86 (32-bit) experience an error when attempting to install or update to ExacqVision Server version 23.09.

<br>

Product

ExacqVision Server 23.09 x86 and above

<br>

Steps to Reproduce

Attempt an update or fresh install of ExacqVision Server version 23.09 on a Ubuntu 14.04 x86 system.

<br>

Expected Results

Installation without error

<br>

Actual Results

The following error is encountered:

/usr/local/exacq/server/exacqd: /lib/i386-linux-gnu/libgcc_s.so.1: version ‘GCC_7.0.0’ not found (required by /usr/local/exacq/server/exacqd)

<br>

Solution

Perform the following steps:

  1. Open a Terminal window (CTRL+ALT+T).<br><br>
  2. Enter the following commands in the order given:
    • sudo apt-get update
    • sudo apt-get install --reinstall ca-certificates
    • sudo add-apt-repository ppa:ubuntu-toolchain-r/test
    • sudo apt-get update
    • sudo apt-get install gcc-7<br><br>
  3. Reboot the server<br><br>
  4. Run the ExacqVision Server installer

<br>

Categories
Knowledge Support Support exacqVision Client Categories Products

Directory Could Not be Created – Symbolic Linking Error 17

When exacqVision Client starts, it looks for a folder named “exacqVision Files” inside the directory of the currently active user. If it doesn’t find one, it creates the directory for exported video. On exacqVision systems, the masterscript creates a symbolic link here that directs data to the “/mnt/export/admin” directory so that exported video does not fill up the operating system partition.

If exacqVision Client starts and detects the symbolic link, but the targeted location is missing, you see the following error:

Instructions circulating through Tech Support incorrectly address this error by deleting the symbolic link, which means the client will create the directory the next time it runs. This eliminates the error message, but the exported video is saved to the operating system drive, which could eventually cause further problems.

Instead of deleting the symbolic link, you should troubleshoot why the export partition is not properly mounted with the proper directories/permissions. For reference, you can see where a symbolic link is pointing to in the following example:





On systems with a full root partition, verify whether the system should be using an export partition by typing cat /etc/fstab | grep /mnt/export. If you do not receive a response, you are using an exacqVision LC or EL with a larger SDD.

If you do receive a response, verify the symlink is intact by typing ls -l ~/ | grep exacqVision. The response should look like this:



If you do not see -> /mnt/export/admin, stop exacqVision Service, close exacqVision Client, and enter the following (using admin256 when prompted for a password). Then restart exacqVision Server and exacqVision Client to verify the message doesn’t appear:

sudo passwdsu -rm -r “/home/admin/exacqVision Files”rm -r “/home/user/exacqVision Files”mkdir -p /mnt/export/adminmkdir -p /mnt/export/userchown admin /mnt/export/adminchown user /mnt/export/userln -s /mnt/export/admin “/home/admin/exacqVision Files”ln -s /mnt/export/user “/home/user/exacqVision Files”exit

Categories
Knowledge Support Support exacqVision Server Categories Products

“Failed to write fstab” Error Displayed while Configuring S-Series Partitions

Symptom

A “Failed to write fstab” error can appear if the system is running low on space on the root “/” partition.

<br>

Affected Versions

This affects all exacqVision S-Series versions. A fix will be released at a later date.

<br>

Resolution

To recover from this error, free up space on the root partition using these steps:

  1. Open a Terminal window.
  2. Type cd /var/log.
  3. Type sudo ls -lh to view a list of directory files and the size of each file (this might require root access).
  4. Look for files that use a large amount of space, perhaps 100KB or larger.
  5. Delete the large files by typing sudo rm immediately folllowed by the filename. For example, type sudo rm tw_mgmt.log.
  6. Type cd /var/log/samba.
  7. Repeat steps 3 to 5 in this location to list, find, and remove large files.
Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM returns error when entering a rule duration using a decimal

Affected platforms

ESM 3.2 or later

<br>

Symptom

If the user enters a value using a decimal (for example, 10.5) for the duration value of a rule, ESM returns an error page when the user attempts to create the rule.

<br>

Workaround

Enter a valid integer (not a decimal number) between 1 second and the number of seconds in a year, which is about 31536000 seconds.

<br>

Resolution

No resolution at this time.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

exacqCloud dashboard search for server name returns error page

There are occasions when a server name search on the dashboard on ESM returns an error page with “contact administrator” message.

<br>

If this happens

  • get the esm logfiles.
  • open logfile-websevice file
  • verify that this log file has the messages “ProtocolError: (‘Connection aborted.’, error(111, ‘Connection refused’))”

If the message above is in the log file, restart the solr service.

<br>

Restarting solr service on Windows

  • open up the windows task manager
  • click services tab
  • find solr Jetty service
  • restart solr Jetty service

<br>

Restating solr service on Linux

  • Open linux terminal application
  • Type “sudo restart ESMWebservice”, OR “sudo /etc/init.d/ESMWebservice restart”, which will restart webservice and sorl service.

Once solr has restarted, verify that you can search for a server name on the ESM dashboard.

Categories
Knowledge Support Support exacqVision Client Categories Products

Line Expected Mac Client Error

Problem

When opening the Mac client the user sees an error dialog box appear stating something similar to “file, line X: ‘-‘ expected”. This is caused by a corrupted client configuration.

<br>

Steps to fix

  1. Close the exacqVision client.
  2. Open “Finder” from the Mac desktop.
  3. From the desktop menu bar, open the “Go” menu and select “Go to Folder”.
  4. Locate “~/Library/Application Support/edvrclient” and delete this.
  5. Locate “~/Library/Preferences/edvrclient Preferences and delete this.
  6. Locate “~/Library/Saved Application State/com.exacq.edvrclient.savedState” and delete this.
  7. Open the exacqVision client. Reconnect to the server on the Add Systems page if needed.
Categories
Knowledge Support Support exacqVision Client

exacqVision Client Error – Unable to exclusively lock file

Symptom  

Problem

When viewing cameras, the user would occasionally see the following exacqVision Client Error message:

Unable to exclusively lock file<br>
C:\Users\&lt;username&gt;\AppData\Roaming\edvrclient\edvrclient.xml with file<br>
C:\ProgramData/boost_interprocess/1615401609/QzpcVXNIcnNicQ05Pc3N6XEFwcERhdGRcU…<br>
Error The system cannot find the path specified.

It was observed that the C:\ProgramData\boost_interprocess\ folder is being renamed by software running in their corporate environment.

The exacqVision Client uses the boosts IPC folder which is sometimes used by the other software.

Example

After a reboot it was observed that the folder 

C:\ProgramData\boost_interprocess\1616678833 

was renamed to:

C:\ProgramData\boost_interprocess\49010000_7D0A0000

Resolution

Update the exacqVision Client software to version 22.06 or higher, for which this issue has been resolved.

or

To temporarily resolve:

  1. Close the exacqVision Client application
  2. Remove the offending ‘C:\ProgramData\boost_interprocess\’ folder and re-start the client.

<br>