Appendix E. Known Errors |
Error message: Feature not implemented. Error code: x65 Description: one of the Dr.Web for UNIX servers components cannot be in operation as it is requested to perform a function which is not implemented in the current version. Resolving the error: •Restore software defaults. For that purpose 1.Clear the contents of <etc_dir>/drweb.ini file It is recommended to back up the file before starting the procedure. For example: # cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save 2.Execute the command # service drweb-configd restart to restart Dr.Web for UNIX servers. 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 Dr.Web 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 UNIX servers 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 Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). If the error persists, contact technical support and be ready to name the error code. Error message: Invalid compressed file. Error code: x92 Description: Dr.Web 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: Dr.Web 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 (username 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: Dr.Web Updater cannot connect to any of the update servers. Resolving the error: •Check whether the network connection is established and verify the connectivity. Make sure 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 parameters used for the connection to proxy. 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. 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: Dr.Web Updater cannot receive the updates because connection was lost. Resolving the error: •Check whether the network connection is established and verify the connectivity. Make sure that your computer is connected to the Internet. •If a proxy server is used, check and adjust the parameters used for the connection to proxy. •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 DRL file Error code: x98 Description: A file with updates received by Dr.Web 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 authorized. Resolving the error: •Purchase a license and activate the product. If you are sure that the demo key file is valid, contact technical support and be ready to name the error code. Error message:Key file is blocked. 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. 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 UNIX servers 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.
Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). Other components: •Restore software defaults. For that purpose 1.Clear the contents of <etc_dir>/drweb.ini file 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 2.Execute the command # service drweb-configd restart to restart Dr.Web for UNIX servers. 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 UNIX servers components is 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-update if the executable file of Dr.Web Updater is invalid •If the error persists or you cannot detect which executable file is invalid, remove Dr.Web for UNIX servers 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 Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). 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 UNIX servers cannot operate because the executable file of the dynamic library for the anti-virus engine <%COREENGINE%> 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 persists, remove Dr.Web for UNIX servers and then install it again. •For details on how to install and remove the product or product components, refer to the "Installation Procedure" and "Removing Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). 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 UNIX servers cannot protect your computer because virus databases are unavailable or corrupted. Resolving the error: •Updatevirus databases. •If the error persists, install the drweb-bases package containing virus databases and anti-virus engine executable file. •If the error persists, remove Dr.Web for UNIX servers and then install it again. •For details on how to install and remove the product or product components, refer to the "Installation Procedure" and "Removing Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). 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 UNIX servers components cannot be in operation as an incompatible software is detected. Resolving the error: •Disable or reconfigure the software so as to prevent any interference in Dr.Web for UNIX servers 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. Resolving the error: •Execute the command $ drweb-ctl rawscan / If the output contains message Error: No valid license provided, the valid key file is not available. Register the product and purchase the license. If you have the license, check that the key file is placed to the valid directory and install it if necessary (see "Licensing" and "Key File" sections in Administrator Manual). •If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see "System Requirements" in Administrator Manual) and, if necessary, install them. After installing the library, restart Dr.Web for UNIX servers 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" section in Administrator Manual). •Execute the command # drweb-ctl cfshow ScanEngine.ExePath If the output string differs from ScanEngine.ExePath = <opt_dir>/bin/drweb-se, execute the following command: # drweb-ctl cfset ScanEngine.ExePath <opt_dir>/bin/drweb-se •If the error persists, install drweb-se component (package) separately. •If the error persists, remove Dr.Web for UNIX servers and then install it again. •For details on how to install and remove the product or product components, refer to the "Installation Procedure" and "Removing Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). 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. 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" in the Manual) and, if necessary, install them. •If your operating system uses SELinux, configure the security policy for drweb-filecheck module (see "Adjusting SELinux Policies" in the Manual). •Execute the command # drweb-ctl cfshow FileCheck.ExePath If the output string differs from FileCheck.ExePath = <opt_dir>/bin/drweb-filecheck, execute the following command: # drweb-ctl cfset FileCheck.ExePath <opt_dir>/bin/drweb-filecheck •If the error persists, install drweb-filecheck component (package) separately. •If the error persists, remove Dr.Web for UNIX servers and then install it again. •For details on how to install and remove the product or product components, refer to the "Installation Procedure" and "Removing Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). 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 a check of downloaded files. Resolving the error: •Execute the command # drweb-ctl cfshow NetCheck.ExePath If the output string differs from NetCheck.ExePath = <opt_dir>/bin/drweb-netcheck, execute the following command: # drweb-ctl cfset NetCheck.ExePath <opt_dir>/drweb-netcheck •If the error persists, install drweb-netcheck component (package) separately. •If the error persists, remove Dr.Web for UNIX servers and then install it again. •For details on how to install and remove the product or product components, refer to the "Installation Procedure" and "Removing Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). If the error persists, contact technical support and be ready to name the error code. Web browser cannot establish connection to Dr.Web management web interface; components of the Dr.Web solution are not on the list of running processes, which is output by the command 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 servers cannot start as the configuration daemon Dr.Web ConfigD is not available. Resolving the error: •Execute the command # service drweb-configd restart to restart Dr.Web ConfigD and Dr.Web for UNIX servers. •If the command returns an error or has no effect, install the drweb-configd package. •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). •If the error persists, remove Dr.Web for UNIX servers and then install it again. •For details on how to install and remove the product or product components, refer to the "Installation Procedure" and "Removing Solution" sections in Administrator Manual. Full version of the Dr.Web for UNIX servers Administrator Manual is available: •on Doctor Web website at http://download.drweb.com/doc/?lng=en (requires a valid Internet connection) •as the PDF file residing in <opt_dir>/share/doc directory (the suffix in the file name determines the language of the document). If the error persists, contact technical support. |