Error message: Error on monitor channel.

Error code: x1

Description: One of the components cannot connect with the Dr.Web ConfigD configuration daemon.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Restart the configuration daemon by executing the command

2.Check whether the authentication mechanism for PAM is installed, configured and operates correctly. If not so, install and configure it (for details refer to administration guides and manuals for your OS distribution).

3.If PAM is configured correctly and restart of the configuration daemon does not help, restore program settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the configuration daemon after clearing the contents of the configuration file.

4.If it is not possible to start the configuration daemon, reinstall the drweb-configd package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Operation is already in progress.

Error code: x2

Description: Operation requested by the user is already in progress.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Wait until operation is finished. If necessary, repeat the required action after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: Operation is in pending state.

Error code: x3

Description: An operation requested by the user is in pending state (possibly, a network connection is currently establishing or one of the program components is loading or initializing, which takes a long time).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Wait for the operation to start. If necessary, repeat the required action after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: Interrupted by user.

Error code: x4

Description: The action is terminated by the user (possibly, it takes a long time).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the required action after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: Operation canceled.

Error code: x5

Description: The action is canceled (possibly, it takes a long time).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the required action again.

If the error persists, contact technical support and be ready to name the error code.

Error message: IPC connection terminated.

Error code: x6

Description: An inter-process communication (IPC) connection with one of the components is terminated (most likely, the component shuts down because of the user command or being idle).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.If the operation is not finished, start it again. Otherwise, the termination is not an error.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid IPC message size.

Error code: x7

Description: A message of invalid size is received during component inter-process communication (IPC).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Restart the program by executing the following command:

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid IPC message format.

Error code: x8

Description: A message of invalid format is received during component inter-process communication (IPC).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Restart the program by executing the following command:

If the error persists, contact technical support and be ready to name the error code.

Error message: Not ready.

Error code: x9

Description: The required action cannot be performed because the necessary component or device is not initialized yet.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the required action after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: Component is not installed.

Error code: x10

Description: One of the components which is necessary to execute a function is not installed.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Install or reinstall the necessary component. If you do not know the component name, try to determine it reviewing the log file.

2.If installation or reinstallation of the necessary component does not help, reinstall the program.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Unexpected IPC message.

Error code: x11

Description: An unexpected message is received during component inter-process communication (IPC).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Restart the program by executing the following command:

If the error persists, contact technical support and be ready to name the error code.

Error message: IPC protocol violation.

Error code: x12

Description: Protocol violation happens during component inter-process communication (IPC).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Restart the program by executing the following command:

If the error persists, contact technical support and be ready to name the error code.

Error message: Subsystem state is unknown.

Error code: x13

Description: It was discovered that the current state is not known for a certain subsystem that is part of this software and is needed for carrying out the requested operation.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the operation.

2.If the error persists, restart the program by executing the command

and then repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Path must be absolute.

Error code: x20

Description: Absolute path to file or directory is required (beginning with the root directory of the file system). Relative path is used now.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Change the path to the file or the directory so as to make the path absolute.

If the error persists, contact technical support and be ready to name the error code.

Error message: Not enough memory.

Error code: x21

Description: Not enough memory to complete the required operation (for example, an attempt to open a large file).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Increase size of available memory for program processes (for example, by changing the limits with the ulimit command), restart the program and repeat the operation.

Note that in some cases the system service systemd can ignore the specified limit changes. In this case, edit (or create if it does not exist) a file /etc/systemd/system/drweb-configd.service.d/limits.conf and specify the changed limit value, for example:

The list of available limits of systemd can be viewed in the documentation man systemd.exec.

Uninstall Dr.Web for UNIX File Servers by entering the following command:

If the error persists, contact technical support and be ready to name the error code.

Error message: I/O error.

Error code: x22

Description: An input/output (I/O) error occurs (for example, the drive is not initialized yet or the partition of the file system is not available anymore).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether the required I/O device or the partition of the file system is available. If necessary, mount it and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: No such file or directory.

Error code: x23

Description: A specified object of the file system (file or directory) is missing. Possibly, it is removed.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path. If necessary, change it and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Permission denied.

Error code: x24

Description: There are not enough permissions to access the specified object of the file system (file or directory).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether the path is correct and whether the component has required permissions. If it is necessary to access the object, change access permissions or elevate component’s permissions. Repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Not a directory.

Error code: x25

Description: A specified object of the file system is not a directory. Enter the path to the directory.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path. Change it and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Data file corrupted.

Error code: x26

Description: Requested data is corrupted.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the operation.

2.If the error persists, restart the program by executing the command

and then repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: File already exists.

Error code: x27

Description: On attempt to create a file, another file with the same name is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path. Change it and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Read-only file system.

Error code: x28

Description: On attempt to create or change an object of the file system (directory, file or socket), it is detected that the file system is read-only.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path. Change it so that the path indicates the writable partition of the file system and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Network error.

Error code: x29

Description: A network error occurs (possibly, a remote node stops responding unexpectedly or the required connection fails).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether the network is available and network settings are correct. If necessary, change network settings and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Not a drive.

Error code: x30

Description: An accessed input/output (I/O) device is not a drive.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the device name. Change the path so that it indicates to the drive and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Unexpected EOF.

Error code: x31

Description: During data reading, the end of the file is reached unexpectedly.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the name of the file. If necessary, change the path so that it indicates the correct file and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: File was changed.

Error code: x32

Description: During scanning the file, it is detected that the file was changed.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat scanning.

If the error persists, contact technical support and be ready to name the error code.

Error message: Not a regular file.

Error code: x33

Description: During accessing an object of the file system. it is detected that it is not a regular file (that is, it is a directory, socket or other object of the file system).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the name of the file. If necessary, change the path so that it indicates the regular file and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Name already in use.

Error code: x34

Description: On attempt to create an object of the file system (directory, file or socket), another object with the same name is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path. Change it and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Host is offline.

Error code: x35

Description: A remote node is not available through the network.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether the required node is available. If necessary, change the node address and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Resource limit reached.

Error code: x36

Description: The limit defined for the use of a certain resource has been reached.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the availability of the required resource. If necessary, raise the limit on the use of this resource and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Different mount points.

Error code: x37

Description: Attempt to restore a file which requires its movement between the file system directories, which belong to different mounting points.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Choose another path for the file restoration and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Unpacking error.

Error code: x38

Description: Archive unpacking unsuccessful (it is possibly password protected or corrupted).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Make sure that file is not corrupted. If the archive is protected with password, remove the protection by entering the correct password and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Virus database corrupted.

Error code: x40

Description: Virus databases are corrupted.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

To view and change the path, go to the Common Settings page of the web interface (if it is installed).

You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Non-supported virus database version.

Error code: x41

Description: Current virus databases are meant for earlier program version.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

To view and change the path, go to the Common Settings page of the web interface (if it is installed).

You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Empty virus database.

Error code: x42

Description: Virus databases are empty.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

•To view and change the path, go to the Common Settings page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Object cannot be cured.

Error code: x43

Description: An attempt to apply the Cure action to an incurable object during threat neutralization.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Select an action that can be applied to the object and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Non-supported virus database combination.

Error code: x44

Description: The current virus database combination cannot be supported.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

•To view and change the path, go to the Common Settings page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Scan limit reached.

Error code: x45

Description: When scanning an object, the specified limits have been reached (for example, the limit on the size of an unpacked file, on the nesting depth and others).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Change limits for scanning (in the component settings) by any of the following methods:

•On the page with the component settings on the web interface (if it is installed)

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

2.After changing the settings, repeat the previously attempted operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Authentication failed.

Error code: x47

Description: Invalid user credentials are used for authentication.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Enter valid credentials of the user with the necessary privileges. Try to complete authentication again.

If the error persists, contact technical support and be ready to name the error code.

Error message: Authorization failed.

Error code: x48

Description: A user whose credentials are used for authorization does not have enough privileges.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Enter valid credentials of the user with the necessary privileges. Try to complete authentication again.

If the error persists, contact technical support and be ready to name the error code.

Error message: Access token is invalid.

Error code: x49

Description: One of the program components provides invalid authorization token on attempt to access the operation, requiring elevated privileges.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Enter valid credentials of the user with the necessary privileges. Try to complete authentication again.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid argument.

Error code: x60

Description: An invalid argument is used on attempt to run a command.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the required action again using valid argument.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid operation.

Error code: x61

Description: An attempt to run an invalid command is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the required action again using valid command.

If the error persists, contact technical support and be ready to name the error code.

Error message: Superuser privileges required.

Error code: x62

Description: Only a user with superuser privileges can perform this action.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Elevate you privileges to root privileges and repeat the required action. To elevate privileges, you can use the commands su and sudo.

If the error persists, contact technical support and be ready to name the error code.

Error message: Not allowed in central protection mode.

Error code: x63

Description: The required action can be performed only if the program operates in standalone mode.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Change product’s operation mode to standalone mode and repeat the operation.

2.To change the mode

•Clear the Enable the central protection mode check box on the Central protection of web interface management (if installed).

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Non-supported OS.

Error code: x64

Description: The program does not support operating system installed on the host.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Install the operating system from the list mentioned in system requirements.

If the error persists, contact technical support and be ready to name the error code.

Error message: Feature not implemented.

Error code: x65

Description: Required features of one of the components are not implemented in the current version of the program.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Restore program settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the program after clearing the contents of the configuration file by executing the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Unknown option.

Error code: x66

Description: The configuration file contains parameters unknown or non-supported in the current version of the program.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Open the <etc_dir>/drweb.ini file in any text editor, remove the line, containing invalid parameter. Save the file and restart the Dr.Web ConfigD configuration daemon by executing the command:

2.If it does not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the configuration daemon after clearing the contents of the configuration file.

If the error persists, contact technical support and be ready to name the error code.

Error message: Unknown section.

Error code: x67

Description: The configuration file contains sections unknown or non-supported in the current version of the program.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Open the <etc_dir>/drweb.ini file in any text editor, remove the unknown (non-supported) section. Save the file and restart the Dr.Web ConfigD configuration daemon by executing the command:

2.If it does not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the configuration daemon after clearing the contents of the configuration file.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid option value.

Error code: x68

Description: One of the parameters in the configuration file contains invalid value for the parameter.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Set the valid parameter value by any of the following methods:

•On the page with the component settings on the web interface (if it is installed)

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

If you do not know which value is valid for the parameter, refer to the help file of the component which uses this parameter. You may also restore parameter value to the default.

2.You may also directly edit the configuration file <etc_dir>/drweb.ini. To do this, open the configuration file in any text editor, find the line containing invalid parameter value, set valid value, then save the file and restart the Dr.Web ConfigD configuration daemon by executing the command

3.If the previous steps do not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the configuration daemon after clearing the contents of the configuration file.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid state.

Error code: x69

Description: The program or one of the components is in invalid state to complete the required operation.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the required action after some time.

2.If the error persists, restart the program by executing the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Only one value allowed.

Error code: x70

Description: One of the parameters in the configuration file contains a list of values; while it is allowed to contain only a single value.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Set the valid parameter value by any of the following methods:

•On the page with the component settings on the web interface (if it is installed)

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

If you do not know which value is valid for the parameter, refer to the help file of the component which uses this parameter. You may also restore parameter value to the default.

2.You may also directly edit the configuration file <etc_dir>/drweb.ini. To do this, open the configuration file in any text editor, find the line containing invalid parameter value, set valid value, then save the file and restart the Dr.Web ConfigD configuration daemon by executing the command

3.If the previous steps do not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the configuration daemon after clearing the contents of the configuration file.

If the error persists, contact technical support and be ready to name the error code.

Error message: Tag value is invalid.

Error code: x71

Description: One of the sections in the configuration file with a name containing a unique tag identifier has an invalid tag identifier.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.If the error occurs on attempt to create a section in the web interface or while using the command

set valid value for the tag and save the section again.

2.If the section is saved directly in the configuration file <etc_dir>/drweb.ini, edit the file. To do this, open the configuration file in any text editor, find the section name containing invalid tag value and set valid value for the tag. Save the file and restart the Dr.Web ConfigD configuration daemon by executing the command

3.If the previous steps do not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the configuration daemon after clearing the contents of the configuration file.

If the error persists, contact technical support and be ready to name the error code.

Error message: Record not found.

Error code: x80

Description: On attempt to access a threat record, it is found out that the record is missing (possibly, another program component processed the threat).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Update the threat list after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: Record is in process now.

Error code: x81

Description: On attempt to access a threat record, it is found out that another program component is processing the record now.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Update the threat list after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: File has already been quarantined.

Error code: x82

Description: On attempt to move the file with the detected threat to quarantine, it is found out that the file is already in quarantine (most likely, another program component processed the threat).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Update the threat list after some time.

If the error persists, contact technical support and be ready to name the error code.

Error message: Cannot backup before update.

Error code: x89

Description:Prior to downloading the updates from the updates server, an attempt to make a backup copy of the files to be updated failed.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the directory that stores backup copies of the files that are updated. Change the path, if necessary (theBackupDir parameter in the [Update] section of the configuration file).

•To view and change the path, go to the Updater page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

3.If the error persists, check whether the user under whose account the Dr.Web Updater component is running has a write permission to the directory specified in the BackupDir. The name of this user is specified in the RunAsUser parameter. If necessary, change the user specified in the RunAsUser parameter or grant the missing permissions in the directory’s properties.

4.If the error persists, reinstall the drweb-update package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid DRL file

Error code: x90

Description: An integrity violation of one of the files with the list of update servers is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the file with the list of servers and change the path if necessary (parameters with *DrlPath in секции [Update] of configuration file).

•To view and change the path, go to the Updater page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view the current parameter value use the command (<*DrlPath> needs to be substituted with a specified parameter name. If parameter name is unclear, refer to parameters values in section, skipping the command part in brackets):

To set new parameter value, execute the command (<*DrlPath> needs to be substituted with a specified parameter name:

To restore parameter value to the default, execute the command (<*DrlPath> needs to be substituted with a specified parameter name:

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

3.If the error persists, reinstall the drweb-update package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid LST file.

Error code: x91

Description: An integrity violation of the file containing the list of updated virus databases is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Update virus databases again after some time.

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

2.If the error persists, reinstall the drweb-update package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid compressed file.

Error code: x92

Description: An integrity violation of the downloaded file containing updates is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Update virus databases again after some time.

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Proxy authentication error.

Error code: x93

Description: The program fails to connect to update servers using the proxy server specified in the settings.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the parameters used to connect to a proxy server (they are set in the Proxy parameter in the [Update] section of the configuration file).

•To view and set the connection parameters, go to the Updater page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: No update servers available.

Error code: x94

Description: The program fails to connect to any of the update servers.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether the network is available. Change network settings, if necessary.

2.If you can access the network only using a proxy server, set parameters to connect to the proxy server (you can set them in the Proxy parameter in the [Update]section of the configuration file).

•To view and set the connection parameters, go to the Updater page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

3.If network connection parameters (including parameters of proxy server) are correct, but the error occurs, make sure you use the available list of update servers. The list of udpate servers used is displayed in parameters *DrlPath in [Update] section of configuration file. Note that, if parameters *CustomDrlPath indicate the existing correct file of servers list, the servers specified there will be used instead of the servers of the standard update zone (the value specified in the corresponding parameter*DrlPath, is ignored).

•To view and set the connection parameters, go to the Updater page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view the current parameter value use the command (<*DrlPath> needs to be substituted with a specified parameter name. If parameter name is unclear, refer to parameters values in section, skipping the command part in brackets):

To set new parameter value, execute the command (<*DrlPath> needs to be substituted with a specified parameter name:

To restore parameter value to the default, execute the command (<*DrlPath> needs to be substituted with a specified parameter name:

4.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid key file format.

Error code: x95

Description: The key file format is violated.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether you have the key file and the path to it. You can specify the path to the key file in the KeyPath parameter in the [Root] section of the configuration file).

•To view and set the path to the key file, go to the Common Settings page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.If you do not have the key file or the used key file is corrupted, purchase and install it. For more details on the key file, purchase and installation refer to section Licensing.

3.To install the key file, you may use the license activation form which is located at the bottom of the Main page of the web interface (if it is installed).

4.You can view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.

If the error persists, contact technical support and be ready to name the error code.

Error message: License is already expired.

Error code: x96

Description: The used license is expired.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to section Licensing.

2.To install the received key file, you may use the license activation form which is located at the bottom of the Main page of the web interface (if it is installed).

3.You can view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.

If the error persists, contact technical support and be ready to name the error code.

Error message: Network operation timed out.

Error code: x97

Description: Network operation timed out (possibly, a remote node stops responding unexpectedly or the required connection fails).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check whether the network is available and network settings are correct. If necessary, change network settings and repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid checksum

Error code: x98

Description: A checksum of the downloaded file containing updates is detected.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Update virus databases again after some time.

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid demo key file.

Error code: x99

Description: The used demo key file is invalid (for example, it was received from another computer).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Send a request for a new demo period for this computer or purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to section Licensing.

2.To install the received key file, you may use the license activation form which is located at the bottom of the Main page of the web interface (if it is installed).

3.You can view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.

If the error persists, contact technical support and be ready to name the error code.

Error message: Key file is blocked.

Error code: x100

Description: The used license is blocked (probably, the license agreement conditions on using the Dr.Web program are broken).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to section Licensing.

2.To install the received key file, you may use the license activation form which is located at the bottom of the Main page of the web interface (if it is installed).

3.You can view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid license.

Error code: x101

Description: The used license is meant for other product or does not allow operation of the installed product components.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to section Licensing.

2.To install the received key file, you may use the license activation form which is located at the bottom of the Main page of the web interface (if it is installed).

3.You can view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid configuration.

Error code: x102

Description: One of the program components cannot be in operation because of incorrect configuration settings.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.If you do not know the name of the component which causes the error, try to determine it by reviewing the log file.

2.If the error is produced by the SpIDer Guard component, most likely that the mode which is selected for the component operation is not supported by OS. Check the selected mode and change it, if necessary. You can do it by setting the value AUTO (the Mode parameter in the [LinuxSpider] section configuration file).

•To view and change the mode, go to the SpIDer Guard page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To set the value to AUTO, execute the command

To restore the parameter value to the default, execute the command

•If the error persists, manually build and install the loadable kernel module for SpIDer Guard.

If the error is produced by another component, restore component settings to the defaults by any of the following methods:

•On the page with the component settings on the web interface (if it is installed)

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

•Edit the configuration file manually (delete all parameters from the component section).

5.If the previous steps do not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the program after clearing the contents of the configuration file by executing the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Invalid executable file

Error code: x104

Description: On of the program components cannot run, because of the incorrect path or corrupted file contents.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.If you do not know the name of the component which causes the error, try to determine it reviewing the log file.

2.Check the path to the executable file of the component in the program configuration file (the ExePath parameter in the component section), by executing the following command (change <component section> for the name of the corresponding section of the configuration file)

3.Restore the path to the default by executing the following command (change <component section> for the name of the corresponding section of the configuration file):

4.If the previous steps do not help, reinstall the package of the corresponding component.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Virus-Finding Engine is not available.

Error code: x105

Description: The file of Dr.Web Virus-Finding Engine is missing or unavailable (required for threat detection).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the drweb32.dll anti-virus engine file. Change the path, if necessary (the CoreEnginePath parameter in the [Root] section of the configuration file).

•To view and change the path, go to the Common Settings page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the command

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

3.If the path is correct and the error persists after updating virus databases, reinstall the drweb-bases package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: No virus databases.

Error code: x106

Description: Virus databases are not found.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

•To view and change the path, go to the Common Settings page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To view current parameter value, execute the command

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.Update virus databases:

•Click Update on the Main page of the web interface, if it is installed.

•Or execute the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Process terminated by signal.

Error code: x107

Description: A component shuts down (possibly, because of the user command or being idle).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.If the operation is not finished, start it again. Otherwise, the shutdown is not an error.

2.If a component shuts down constantly, restore its settings to the defaults by any of the following methods:

•On the page with the component settings on the web interface (if it is installed)

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

•Edit the configuration file manually (delete all parameters from the component section).

3.If it does not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the program after clearing the contents of the configuration file by executing the command

If the error persists, contact technical support and be ready to name the error code.

Error message: Unexpected process termination.

Error code: x108

Description: A component unexpectedly shuts down because of a failure.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Repeat the terminated operation.

2.If the component constantly shuts down abnormally, restore its settings to the defaults by any of the following methods:

•On the page with the component settings on the web interface (if it is installed)

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

•Edit the configuration file manually (delete all parameters from the component section).

3.If it does not help, restore program’s settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

Restart the program after clearing the contents of the configuration file by executing the command

4.If the error persists after restoring program settings, reinstall the component package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Incompatible software detected.

Error code: x109

Description: A program component cannot be in operation because an incompatible software is detected. This software interrupts correct component operation.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Disable or reconfigure the incompatible software so as to prevent any interference with the Dr.Web for UNIX File Servers operation.

If the error persists, contact technical support and be ready to name the error code.

Error message: Linux kernel module for SpIDer Guard is not available.

Error code: x113

Description: SpIDer Guard> requires a Linux kernel module which is missing.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check which operating mode of the component was selected and change it—if necessary—by setting the value to AUTO (for the Mode parameter in the [LinuxSpider] section of the configuration file).

•To view and change the mode, go to the SpIDer Guard page of the web interface (if it is installed).

•You also may use the commands of the command-line management tool.

To set the value to AUTO, execute the command

To restore the parameter value to the default, execute the command

2.If the error persists, manually build and install the loadable kernel module for SpIDer Guard.

If the error persists, contact technical support and be ready to name the error code.

Error message: Scanning Engine is not available.

Error code: x119

Description: Dr.Web Scanning Engine component is missing or failed to start (required for threat detection).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the drweb-se executable file. Change the path, if necessary (the ExePath parameter in the [ScanEngine] section of the configuration file).

You may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.If the error persists after entering the correct path

•Execute the command

If the line Error: No valid license provided, is output, a valid key file is missing. Register the program and receive a license. After receiving the license, check whether the key file is available and install it, if necessary.

•If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see section System Requirements) and, if necessary, install them. After installing the libraries, restart Dr.Web for UNIX File Servers by executing the command

•If your operating system uses SELinux, configure the security policy for the drweb-se module (see section Configuring SELinux Security Policies).

3.If the configuration does not contain the Dr.Web Scanning Engine component settings or if the steps previously mentioned do not help, install or reinstall the drweb-se package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: File Checker is not available.

Error code: x120

Description: Dr.Web File Checker component is missing or failed to start (required for threat detection).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the drweb-filecheck executable file. Change the path, if necessary (the ExePath parameter in the [FileCheck] section of the configuration file).

You may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.If the error persists after entering the correct path

•If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see section System Requirements) and, if necessary, install them. After installing the libraries, restart Dr.Web for UNIX File Servers by executing the command

•If your operating system uses SELinux, configure the security policy for the drweb-filecheck module (see section Configuring SELinux Security Policies).

3.If the configuration does not contain the Dr.Web File Checker component settings or if the steps previously mentioned do not help, install or reinstall the drweb-filecheck package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: ES Agent is not available.

Error code: x121

Description: Dr.Web ES Agent component is missing (it is necessary to connect to the central protection server).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the drweb-esagent executable file. Change the path, if necessary (the ExePath parameter in the [ESAgent] section of the configuration file).

You may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.If the configuration does not contain settings for the Dr.Web ES Agent component or if the error persists after entering the correct path, install or reinstall the drweb-esagent package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Network Checker is not available.

Error code: x123

Description: Dr.Web Network Checker component is missing (required for check of downloaded files).

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the drweb-netcheck executable file. Change the path, if necessary (the ExePath parameter in the [Netcheck] section of the configuration file).

You may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.If the configuration does not contain settings for the Dr.Web Network Checker component or if the error persists after entering the correct path, install or reinstall the drweb-netcheck package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: CloudD is not available.

Error code: x124

Description: Dr.Web CloudD (required for requests to the Dr.Web Cloud service) is missing.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Check the path to the drweb-cloudd executable file. Change the path, if necessary (the ExePath parameter in the [CloudD] section of the configuration file).

You may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

To set a new parameter value, execute the command

To restore the parameter value to the default, execute the command

2.If the configuration does not contain settings for the Dr.Web CloudD component or if the error persists after entering the correct path, install or reinstall the drweb-cloudd package.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support and be ready to name the error code.

Error message: Unexpected error.

Error code: x125

Description: Unexpected error occurs in operation of one of the components.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

Resolving the error:

1.Try restart the program by executing the command

If the error persists, contact technical support and be ready to name the error code.

Symptoms

After installation of the SpIDer Guard kernel module, operating system abnormally shuts down with a kernel error «Kernel panic»

Description

SpIDer Guard kernel module cannot operate in the operating system kernel environment (for example, when OS operates in the Xen hypervisor environment).

Resolving the error:

1.Cancel the load of the SpIDer Guard kernel module (kernel module name is drweb) by adding to the grub loader the following string

to the load settings string of the operating system kernel.

2.When the OS is loaded, remove the drweb PSB.Ko module from the /lib/' uname-r '/extra directory of additional modules.

3.Set operation mode for SpIDer Guard to AUTO by executing the following commands:

4.Do not use the Xen hypervisor, in case your operating system does not support the fanotify interface or this mode does not allow using SpIDer Guard for the full file system monitoring (relevant for GNU/Linux with mandatory access models, for example, for Astra Linux), making the use of the LKM mode mandatory for the file system monitoring.

If the error persists, contact technical support.

Symptoms:

Dr.Web MailD, SpIDer Gate, Dr.Web ICAPD (list of the indicated components depends on the installed product) do not scan messages; in the Dr.Web for UNIX File Servers log there are messages Too many open files.

Description:

Due to a large data scanning load, Dr.Web Network Checker has reached the ceiling of the number of available file descriptors.

Resolving the error:

1.Raise the limit of the number of open file descriptors available to the application via the command ulimit -n (default limit of the descriptor number for Dr.Web for UNIX File Servers is 16384).

Note that in some cases the system service systemd can ignore the specified limit changes. In this case, edit (or create if it does not exist) a file /etc/systemd/system/drweb-configd.service.d/limits.conf and specify the changed limit value:

The list of available limits of systemd can be viewed in the documentation man systemd.exec.

2.Once the limit is changed, restart Dr.Web for UNIX File Servers by executing the following command:

If the error persists, contact technical support.

Symptoms:

Web browser cannot establish connection to Dr.Web management web interface; components of Dr.Web anti-virus solutions are not in the list of running processes (ps ax | grep drweb); attempt to execute any drweb-ctl <command>, except for drweb-ctl rawscan, results in one of the following errors:

Error: connect: No such file or directory: "<path>/.com.drweb.public"

or

Error: connect: Connection refused: "<path>/.com.drweb.public".

Description:

Dr.Web for UNIX File Servers cannot start as the configuration daemon Dr.Web ConfigD is not available.

Resolving the error:

1.Execute the command

to restart Dr.Web ConfigD and Dr.Web for UNIX File Servers.

2.If this command returns error message, or has no any effect, install drweb-configd component (package) separately.

Also note that this may mean that PAM authentication is not used in the system. If so, please install and configure PAM (the product cannot operate correctly without PAM).

3.If the error persists, remove Dr.Web for UNIX File Servers and then install it again.

For details on how to install and uninstall the product or product components, refer to sections Installing the Product and Uninstalling the Product.

If the error persists, contact technical support.

0

EC_OK

Success

This is not an error

1

EC_MONITOR_IPC_ERROR

Error on monitor channel

Error x1

2

EC_ALREADY_IN_PROGRESS

Operation is already in progress

Error x2

3

EC_IN_PENDING_STATE

Operation is in pending state

Error x3

4

EC_INTERRUPTED_BY_USER

Interrupted by user

Error x4

5

EC_CANCELED

Operation canceled

Error x5

6

EC_LINK_DISCONNECTED

Link disconnected

Error x6

7

EC_BAD_MESSAGE_SIZE

Invalid IPC message size

Error x7

8

EC_BAD_MESSAGE_FORMAT

Invalid IPC message format

Error x8

9

EC_NOT_READY

Not ready

Error x9

10

EC_NOT_INSTALLED

Component is not installed

Error x10

11

EC_UNEXPECTED_MESSAGE

Unexpected IPC message

Error x11

12

EC_PROTOCOL_VIOLATION

Protocol violation

Error x12

13

EC_UNKNOWN_STATE

Subsystem state is unknown

Error x13

20

EC_NOT_ABSOLUTE_PATH

Path must be absolute

Error x20

21

EC_NO_MEMORY

Not enough memory

Error x21

22

EC_IO_ERROR

IO error

Error x22

23

EC_NO_SUCH_ENTRY

No such file or directory

Error x23

24

EC_PERMISSION_DENIED

Permission denied

Error x24

25

EC_NOT_A_DIRECTORY

Not a directory

Error x25

26

EC_DATA_CORRUPTED

Data file corrupted

Error x26

27

EC_FILE_EXISTS

File already exists

Error x27

28

EC_READ_ONLY_FS

Read-only file system

Error x28

29

EC_NETWORK_ERROR

Network error

Error x29

30

EC_NOT_A_DRIVE

Not a drive

Error x30

31

EC_UNEXPECTED_EOF

Unexpected EOF

Error x31

32

EC_FILE_WAS_CHANGED

File was changed

Error x32

33

EC_NOT_A_REGULAR_FILE

Not a regular file

Error x33

34

EC_NAME_ALREADY_IN_USE

Name already in use

Error x34

35

EC_HOST_OFFLINE

Host is offline

Error x35

36

EC_LIMIT_REACHED

Resource limit reached

Error x36

37

EC_CROSS_DEVICE_LINK

Mounting points are different

Error x37

38

EC_UNPACKING_ERROR

Unpacking error

Error x38

40

EC_BASE_CORRUPTED

Virus base corrupted

Error x40

41

EC_OLD_BASE_VERSION

Non-supported virus database version

Error x41

42

EC_EMPTY_BASE

Empty virus database

Error x42

43

EC_CAN_NOT_BE_CURED

Object cannot be cured

Error x43

44

EC_INVALID_BASE_SET

Non-supported virus database combination

Error x44

45

EC_SCAN_LIMIT_REACHED

Scan limit reached

Error x45

47

EC_AUTH_FAILED

Authentication failed

Error x47

48

EC_NOT_AUTHORIZED

Authorization failed

Error x48

49

EC_INVALID_TOKEN

Access token is invalid

Error x49

60

EC_INVALID_ARGUMENT

Invalid argument

Error x60

61

EC_INVALID_OPERATION

Invalid operation

Error x61

62

EC_ROOT_ONLY

Superuser privileges required

Error x62

63

EC_STANDALONE_MODE_ONLY

Not allowed in central protection mode

Error x63

64

EC_NON_SUPPORTED_OS

Non-supported OS

Error x64

65

EC_NOT_IMPLEMENTED

Feature not implemented

Error x65

66

EC_UNKNOWN_OPTION

Unknown option

Error x66

67

EC_UNKNOWN_SECTION

Unknown section

Error x67

68

EC_INVALID_OPTION_VALUE

Invalid option value

Error x68

69

EC_INVALID_STATE

Invalid state

Error x69

70

EC_NOT_LIST_OPTION

Only one value allowed

Error x70

71

EC_INVALID_TAG

Tag value is invalid

Error x71

80

EC_RECORD_NOT_FOUND

Record not found

Error x80

81

EC_RECORD_BUSY

Record is in process now

Error x81

82

EC_QUARANTINED_FILE

File has already been quarantined

Error x82

89

EC_BACKUP_FAILED

Cannot backup before update

Error x89

90

EC_BAD_DRL_FILE

Invalid DRL file

Error x90

91

EC_BAD_LST_FILE

Invalid LST file

Error x91

92

EC_BAD_LZMA_FILE

Invalid compressed file

Error x92

93

EC_PROXY_AUTH_ERROR

Proxy authentication error

Error x93

94

EC_NO_UPDATE_SERVERS

No update servers available

Error x94

95

EC_BAD_KEY_FORMAT

Invalid key file format

Error x95

96

EC_EXPIRED_KEY

License is already expired

Error x96

97

EC_NETWORK_TIMEDOUT

Network operation timed out

Error x97

98

EC_BAD_CHECKSUM

Invalid checksum

Error x98

99

EC_BAD_TRIAL_KEY

Invalid trial license

Error x99

100

EC_BLOCKED_LICENSE

Blocked license key

Error x100

101

EC_BAD_LICENSE

Invalid license

Error x101

102

EC_BAD_CONFIG

Invalid configuration

Error x102

104

EC_BAD_EXECUTABLE

Invalid executable file

Error x104

105

EC_NO_CORE_ENGINE

Core engine is not available

Error x105

106

EC_NO_VIRUS_BASES

No virus databases

Error x106

107

EC_APP_TERMINATED

Process terminated by signal

Error x107

108

EC_APP_CRASHED

Unexpected process termination

Error x108

109

EC_INCOMPATIBLE

Incompatible software detected

Error x109

113

EC_NO_KERNEL_MODULE

Kernel module is not available

Error x113

119

EC_NO_SCAN_ENGINE

ScanEngine is not available

Error x119

120

EC_NO_FILE_CHECK

FileCheck is not available

Error x120

121

EC_NO_ESAGENT

ESAgent is not available

Error x121

123

EC_NO_NET_CHECK

NetCheck is not available

Error x123

124

EC_NO_CLOUDD

CloudD is not available

Error x124

125

EC_UNEXPECTED_ERROR

Unexpected error

Error x125