|
If you cannot find description of the occurred error, it is recommended to contact technical support. Be ready to name the error code and describe steps to reproduce the issue. |
Error message: Feature not implemented.
Error code: x65
Description: One of Dr.Web for Linux components cannot be in operation as it is requested to perform a function which is not implemented in the current version.
Resolving the error:
SpIDer Gate: an attempt to enable check of incoming connections.
•Execute the command
# drweb-ctl cfset GateD.InputDivert Off
to disable check of incoming connections by SpIDer Gate.
Other components:
•Restore software defaults. For that purpose
1.Clear contents of the file /etc/opt/drweb.com/drweb.ini. It is recommended to back up the file before the procedure. For example:
# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini
2.Execute the command
# service drweb-configd restart
to restart Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: Invalid DRL file.
Error code: x90
Description: Updating cannot be performed as Updater detected integrity violation or cannot find a signed file with the list of update servers.
Resolving the error:
•Install drweb-bases and drweb-dws components (packages) separately and then start an update.
•If the error persists, remove Dr.Web for Linux and then install it again on the system and restart the update.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: Invalid compressed file.
Error code: x92
Description: Updater detected integrity violation or cannot find the archive file received from the update server.
Resolving the error:
•Restart the update after some time.
If the error persists, contact technical support and be ready to name the error code.
Error message: Proxy authentication error.
Error code: x93
Description: Updater failed to connect to an update server as was not authenticated on the proxy server used for receiving updates.
Resolving the error:
•Check and correct parameters of the used proxy server (user name and password used for authentication).
•If an error persists, change the proxy server or do not use proxy for connections.
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: Updater cannot connect to any of the update servers.
Resolving the error:
•Check whether the network connection is established and verify the connectivity. Ensure that your computer is connected to the Internet.
•If Internet connection is allowed only via proxy, configure the use of proxy for receiving updates.
•If a proxy server is used, check and adjust the used connection parameters.
If the error persists, contact technical support and be ready to name the error code.
Error message: File format is unknown or unsupported.
Error code: x95
Description: Updates cannot be received as key file integrity is violated.
Resolving the error:
•Install the key file from the backup. If you cannot find the backup, contact technical support to obtain it.
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: Updates cannot be received as the used license is expired.
Resolving the error:
•Purchase a new license and activate the product via License Manager.
If you are sure that the licensed period is not expired, contact technical support and be ready to name the error code.
Error message: Network operation timed out.
Error code: x97
Description: Updater cannot receive the updates because connection was lost.
Resolving the error:
•Check whether the network connection is established and verify the connectivity. Ensure that your computer is connected to the Internet.
•If a proxy server is used, check and adjust the used connection parameters.
•If an error persists, change the proxy server or do not use proxy for connections.
If the error persists, contact technical support and be ready to name the error code.
Error message: Invalid checksum.
Error code: x98
Description: A file with updates received by Updater has a checksum that is not equal to expected.
Resolving the error:
•Restart the update after some time.
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: Updates cannot be received as demo key file integrity is violated or its use is not authorised.
Resolving the error:
•Purchase a license and activate the product via License Manager.
If you are sure that the demo key file is valid, contact technical support and be ready to name the error code.
Error message: Blocked license key.
Error code: x100
Description: Updates cannot be received as the used key file is blocked by Doctor Web.
Resolving the error:
•Purchase a license and activate the product via License Manager.
If you are sure that the used key file is valid, contact technical support and be ready to name the error code.
Error message: Invalid configuration.
Error code: x102
Description: One of Dr.Web for Linux components cannot be in operation due to incorrect configuration settings.
Resolving the error:
SpIDer Guard: the specified operation mode is not supported by the operating system.
•Execute the command
# drweb-ctl cfset LinuxSpider.Mode AUTO
to switch the operation of SpIDer Guard to automatic mode.
•If the error persists, manually build and install the loadable kernel module to be used by SpIDer Guard.
|
Note that operation of SpIDer Guard and of the loadable kernel module is guaranteed only on the tested Linux distributives (see System Requirements). |
Other components:
•Restore software defaults. For that purpose
3.Clear contents of the file /etc/opt/drweb.com/drweb.ini. It is recommended to back up the file before the procedure. For example:
# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini
4.Execute the command
# service drweb-configd restart
to restart Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: Invalid executable file.
Error code: x104
Description: An executable file of one of Dr.Web for Linux components unavailable or corrupted.
Resolving the error:
•Install the package with the necessary component:
odrweb-spider, if the executable file of SpIDer Guard is invalid
odrweb-gated, if the executable file of SpIDer Gate is invalid
odrweb-update, if the executable file of Updater is invalid
•If the error persists, or you cannot detect which executable file is invalid, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: Invalid core engine file.
Error code: x105
Description: Dr.Web for Linux cannot operate because executable file of anti-virus engine Dr.Web Virus-Finding Engine is unavailable or corrupted.
Resolving the error:
•Update virus databases.
•If the error persists, install the drweb-bases package containing virus databases and anti-virus engine executable file.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: No virus databases.
Error code: x106
Description: Dr.Web for Linux cannot protect your computer because virus databases are unavailable or corrupted.
Resolving the error:
•Update virus databases.
•If the error persists, install the drweb-bases package containing virus databases and anti-virus engine executable file.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: Incompatible software detected.
Error code: x109
Description: One of Dr.Web for Linux components cannot be in operation as an incompatible software is detected.
Resolving the error:
SpIDer Gate: software detected which generates rules for the system firewall are incompatible with SpIDer Gate operation.
•Disable or reconfigure the software so as to prevent any interference in SpIDer Gate operation.
•On SUSE Linux OS with default settings, conflicts between SpIDer Gate and system firewall SuseFirewall2 can occur. To remove the conflict, change the settings of the system firewall SuseFirewall2. For that purpose:
1.Open the configuration file of SuseFirewall2 (by default, this is the /etc/sysconfig/SuSEfirewall2 file).
2.Find the following text block:
## Type: yesno
#
# Install NOTRACK target for interface lo in the raw table. Doing so
# speeds up packet processing on the loopback interface. This breaks
# certain firewall setups that need to e.g. redirect outgoing
# packets via custom rules on the local machine.
#
# Defaults to "yes" if not set
#
FW_LO_NOTRACK=""
3.Set the parameter value to "no":
FW_LO_NOTRACK="no"
4.Restart SuseFirewall2. To do it, use the following command:
# rcSuSEfirewall2 restart
|
Note that if SuseFirewall2 does not have the FW_NO_TRACK option in its settings, disable the firewall to resolve the conflict (for example, it is necessary to do for OS SUSE Linux Enterprise Server 11). |
5.Restart SpIDer Gate (disable and then enable it on the corresponding page).
Other components:
•Disable or reconfigure the software so as to prevent any interference in Dr.Web for Linux operation.
If the error persists, contact technical support and be ready to name the error code.
Error message: ScanEngine is not available.
Error code: x119
Description: Cannot check files as drweb-se module is missing or failed to start. This module is used for searching malicious objects.
Failed to start: Scanner, SpIDer Guard, SpIDer Gate (partially).
Resolving the error:
•If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see System Requirements) and, if necessary, install them. After installing the library, restart Dr.Web for Linux by the following command
# service drweb-configd restart
•If your operating system uses SELinux, configure the security policy for drweb-se module (see Adjusting SELinux Policies).
•Execute the command
# drweb-ctl cfshow ScanEngine.ExePath
If the output string differs from ScanEngine.ExePath = /opt/drweb.com/bin/drweb-se, execute the following command:
# drweb-ctl cfset ScanEngine.ExePath /opt/drweb.com/bin/drweb-se
•If the error persists, install drweb-se component (package) separately.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: FileCheck is not available.
Error code: x120
Description: Cannot check files as a Scanner component drweb-filecheck, used for this function, is missing.
Failed to start: Scanner, SpIDer Guard.
Resolving the error:
•If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see System Requirements) and, if necessary, install them.
•If your operating system uses SELinux, configure the security policy for drweb-filecheck module (see Adjusting SELinux Policies).
•Execute the command
# drweb-ctl cfshow FileCheck.ExePath
If the output string differs from FileCheck.ExePath = /opt/drweb.com/bin/drweb-filecheck, execute the following command:
# drweb-ctl cfset FileCheck.ExePath /opt/drweb.com/bin/drweb-filecheck
•If the error persists, install drweb-filecheck component (package) separately.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: Firewall is not available.
Error code: x122
Description: Cannot control Internet access as drweb-firewall is missing or failed to start. The module is used for diverting of connections.
Failed to start: SpIDer Gate.
Resolving the error:
•Execute the command
# drweb-ctl cfshow Firewall.ExePath
If the output string differs from Firewall.ExePath = /opt/drweb.com/bin/drweb-firewall, execute the following command:
# drweb-ctl cfset Firewall.ExePath /opt/drweb.com/bin/drweb-firewall
•If an error persists, install drweb-firewall component (package) separately.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Error message: NetCheck is not available.
Error code: x123
Description: Cannot control Internet access as drweb-netcheck is missing or failed to start. The module is used for check of downloaded files.
Failed to start: SpIDer Gate (partially).
Resolving the error:
•Execute the command
# drweb-ctl cfshow NetCheck.ExePath
If the output string differs from NetCheck.ExePath = /opt/drweb.com/bin/drweb-netcheck, execute the following command:
# drweb-ctl cfset NetCheck.ExePath /opt/drweb.com/bin/drweb-netcheck
•If the error persists, install drweb-netcheck component (package) separately.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.
Main window of Dr.Web for Linux is disabled and displays the message Dr.Web for Linux is loading... or status indicator in notification area of desktop displays an critical error mark, and drop-down menu contains only one disabled item Loading...
Description:
Anti-virus cannot start because core component drweb-configd is not available.
Resolving the error:
•Execute the command
# service drweb-configd restart
to restart Dr.Web for Linux.
•If this command returns error message, or has no any effect, install drweb-configd component (package) separately.
•If the error still occurs, remove Dr.Web for Linux and then install it again on the system.
•For details on how to install and remove the product or product components, refer to the Installation Procedure and Removing Dr.Web for Linux.
If the error persists, contact technical support.
•The status indicator is not displayed in the notification area after the user logged in;
•Trying to run the graphical user interface of Dr.Web for Linux by the command
$ drweb-gui
opens the Dr.Web for Linux main window.
Description:
The problem could mean that necessary additional library libappindicator1 is not installed in your system.
Resolving the error:
•Install the library (package) libappindicator1 using the system package manager.
•Log out and then log in again.
If the error persists, contact technical support.