Failed to connect SMB share (\%1\%2\%3) – mount error ***.
Description
%1 = IP address of SMB share. %BR%
%2 = SMB share name. %BR%
%3 = Server name. %BR%
Archiving target failed to connect.
Notes
Use the SMB mount error to troubleshoot.
Failed to connect SMB share (\%1\%2\%3) – mount error ***.
%1 = IP address of SMB share. %BR%
%2 = SMB share name. %BR%
%3 = Server name. %BR%
Archiving target failed to connect.
Use the SMB mount error to troubleshoot.
Opening|creating database in location: C:/Program Files/exacqVision/Server/eventpi.db
In Linux, this will say: /usr/local/exacq/Server/eventpi.db
This is a normal message during startup. If the file gets “created” on an existing installation, this indicates there was a corruption or missing database.
Loaded config and event linkages.
This is a normal message during startup.
Loaded configuration.
This is a normal message during startup.
Device %1: Config socket connect error (10060)
%1 – IP address of the camera. %BR%
Timeout connecting to camera indicated, will attempt delayed reconnect.
If you see this and do not think the camera is going down. Try an extended ping test, or accessing the camera via the webpage.
Transform failure on send ***
Communication failure while sending config information to a Client.
Can be due to a corrupted installation or anti-virus.
<br>
Starting Log Manager (%1).
%1 = The Server version number. %BR%
Indicates the Exacq Server service started.
This log should be preceded by Stopping Log Manager. If it is not, this often indicates an ungraceful shutdown (due to a crash, freeze, power loss, etc…).
File ***.ps not found
Indicates that that the Exacq Server had knew about this file. But when it went to remove this data to make room for new data, it could not find the file in question.
This can mean a few things. It can mean that the drive is falling behind, if we do not get a response in time this causes us “not to find” the file. Or that the file was manually deleted and the software did not know about it. Either we discard that entry very quickly and move on to the next file. This should not in and of itself cause any problems.
*** EWOULDBLOCK – 143 ***
The socket is non-blocking, but the called function would block.
This error is detected when a requested operation is not ready to be done, but the socket is set to a non-blocking mode. select can be used to wait with timeout for the operation to become ready.
<br>
*** ETIMEDOUT – 140 ***
Timeout.
An operation such as connect, recv or send timed out. For TCP, this error could occur during a send operation if the remote host is not responding with acknowledgments. This could also occur if the remote host is not responding to an ARP request.
<br>