Code
|
Error
|
Description
|
1
|
Error on monitor channel
|
One of the components cannot connect with the configuration daemon Dr.Web ConfigD.
|
2
|
Operation is already in progress
|
Operation requested by the user is already in progress.
|
3
|
Operation is in pending state
|
Operation requested by the user is in a pending state (probably, network connection is currently being establishing or one of the application components is loading or initializing, which takes a long time).
|
4
|
Interrupted by user
|
Action is terminated by the user (probably, the action was taking too much time).
|
5
|
Operation canceled
|
Action is cancelled (probably, the action was taking too much time).
|
6
|
IPC connection terminated
|
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).
|
7
|
Invalid IPC message size
|
Message of an invalid size is received during the component inter-process communication (IPC).
|
8
|
Invalid IPC message format
|
Message of an invalid format is received during the component inter-process communication (IPC).
|
9
|
Not ready
|
Required action cannot be performed because the required component or device is not initialized yet.
|
10
|
Component is not installed
|
Some function of Dr.Web for macOS is not available because the corresponding component (performing this function) is not installed in the system.
|
11
|
Unexpected IPC message
|
Unexpected message is received during component inter-process communication (IPC).
|
12
|
IPC protocol violation
|
Protocol violation happens during component inter-process communication (IPC).
|
13
|
Subsystem state is unknown
|
Current state is not known for a certain subsystem that is a part of this software and is needed for carrying out the requested operation.
|
20
|
Path must be absolute
|
Absolute path to file or directory is required (beginning with root directory of the file system). Relative path is used now.
|
21
|
Not enough memory
|
Not enough memory to complete the required operation (for example, an attempt to open a large file).
|
22
|
IO error
|
An input/output (I/O) error has occurred (for example, the drive is not initialized yet or the partition of the file system is not available anymore).
|
23
|
No such file or directory
|
Specified object of the file system (file or directory) is missing. It was probably removed.
|
24
|
Access denied
|
Insufficient rights to access the specified object of the file system (file or directory).
|
25
|
Not a directory
|
Specified object of the file system is not a directory. Enter the path to the directory.
|
26
|
Data file corrupted
|
Requested data is corrupted.
|
27
|
File already exists
|
When attempting to create a file, another file with the same name is detected.
|
28
|
Read-only file system
|
When attempting to create or change an object of the file system (directory, file, or socket), it is detected that the file system is read-only.
|
29
|
Network error
|
Network error occurs (probably, a remote host stopped responding unexpectedly or the required connection failed).
|
30
|
Not a drive
|
Accessed input/output (I/O) device is not a drive.
|
31
|
Unexpected EOF
|
During data reading, the end of the file is reached unexpectedly.
|
32
|
File was changed
|
During the file scan, it is detected that the file was changed.
|
33
|
Not a regular file
|
During accessing an object of the file system, it is detected that it is not a regular file (that is, a directory, socket, or other object of the file system).
|
34
|
Name already in use
|
When attempting to create an object of the file system (directory, file, or socket), another object with the same name is detected.
|
35
|
Host is offline
|
Remote host is not available through the network.
|
36
|
Resource limit reached
|
The limit defined for the use of a certain resource has been reached.
|
37
|
Different mount points
|
An attempt to restore a file requires to move it between file system directories belonging to different mount points.
|
38
|
Unpacking error
|
Archive unpacking failed (it is probably password protected or corrupted).
|
40
|
Virus database corrupted
|
It is detected that virus databases are corrupted.
|
41
|
Non-supported virus database version
|
It is detected that current virus databases are meant for an earlier application version.
|
42
|
Empty virus database
|
Virus databases are empty.
|
43
|
Object cannot be cured
|
An attempt to apply the Cure action to an incurable object during threat neutralization.
|
44
|
Non-supported virus database combination
|
Current virus database combination is not supported.
|
45
|
Scan limit reached
|
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 so on).
|
47
|
Authentication failed
|
Invalid user credentials are used for authentication.
|
48
|
Authorization failed
|
A user whose credentials are used for authorization does not have the required permissions.
|
49
|
Access token is invalid
|
One of the application components provides an invalid authorization token when attempting to access the operation that required elevated permissions.
|
60
|
Invalid argument
|
An invalid argument is used when attempting to run a command.
|
61
|
Invalid operation
|
An attempt to run an invalid command is detected.
|
62
|
Root access required
|
Only a user with root access can perform this action.
|
63
|
Not allowed in central protection mode
|
The required action can be performed only if the application operates in the standalone mode.
|
64
|
Non-supported OS
|
The application does not support the operating system installed on the host.
|
65
|
Feature not implemented
|
Required features of one of the components are not implemented in the current version of the application.
|
66
|
Unknown option
|
The configuration file contains parameters unknown or not supported in the current version of the application.
|
67
|
Unknown section
|
The configuration file contains sections unknown or not supported in the current version of the application.
|
68
|
Invalid option value
|
One of the parameters in the configuration file contains an invalid value.
|
69
|
Invalid state
|
The application or one of the components is in an invalid state to complete the required operation.
|
70
|
Only one value allowed
|
One of the parameters in the configuration file contains a list of values instead of a single value.
|
71
|
Tag value is invalid
|
Invalid tag detected in one of the sections in the configuration file with a name containing a unique tag identifier.
|
80
|
Record not found
|
The accessed threat record is missing (probably, another application component processed the threat).
|
81
|
Record is in process now
|
The accessed threat record is being processed by another application component.
|
82
|
File has already been quarantined
|
When attempting to move the file with the detected threat to quarantine, it was detected that the file is already in quarantine (most likely, another application component processed the threat).
|
89
|
Cannot backup before update
|
An attempt to make a backup copy of the files before downloading updates from the update server failed.
|
90
|
Invalid DRL file
|
An integrity violation of one of the files with the list of update servers is detected.
|
91
|
Invalid LST file
|
An integrity violation of the file containing the list of updated virus databases is detected.
|
92
|
Invalid compressed file
|
An integrity violation of the downloaded file containing updates is detected.
|
93
|
Proxy authentication error
|
Application fails to connect to update servers using the proxy server specified in preferences.
|
94
|
No update servers available
|
Application fails to connect to any of update servers.
|
95
|
Invalid key file format
|
Key file format is violated.
|
96
|
License is expired
|
Current license is expired.
|
97
|
Network operation timed out
|
Network operation timed out.
|
98
|
Invalid checksum
|
Checksum of the downloaded file containing updates is invalid.
|
99
|
Invalid demo key file
|
Current demo key file is invalid (for example, it was received from another computer).
|
100
|
License key file is blocked
|
Current license is blocked (probably, the license agreement conditions on using Dr.Web were violated).
|
101
|
Invalid license
|
Current license is meant for another product or does not allow operation of the installed product components.
|
102
|
Invalid configuration
|
One of the application components cannot be in operation because of incorrect configuration preferences.
|
104
|
Invalid executable file
|
One of the application components cannot run due to incorrect path or corrupted execution file contents.
|
105
|
Virus-Finding Engine is not available
|
A file of Dr.Web Virus-Finding Engine required for threat detection is missing or unavailable.
|
106
|
No virus databases
|
Virus databases are missing.
|
107
|
Process terminated by signal
|
A component shuts down (probably, because of the user command or being idle).
|
108
|
Unexpected process termination
|
A component unexpectedly shuts down because of a failure.
|
109
|
Incompatible software detected
|
An application component cannot be in operation because incompatible software is detected. This software interrupts correct component operation.
|
110
|
Invalid VadeRetro library
|
A file of VadeRetro anti-spam library is missing, unavailable or corrupted. It is necessary for email scanning.
|
112
|
Databases of web resource categories
|
Databases of web resource categories are missing.
|
113
|
Kernel module for SpIDer Guard is not available
|
The kernel module required for SpIDer Guard operation is missing.
|
117
|
SpIDer Gate is not available
|
SpIDer Gate component required for scanning network connections is missing.
|
118
|
MailD is not available
|
SpIDer Mail component required for scanning email is missing.
|
119
|
Scanning Engine is not available
|
Cannot scan files as Scanning Engine component is missing or failed to start. This module is used for searching malicious objects.
|
120
|
Scanner is not available
|
Cannot scan files as the Scanner component used for this feature is missing.
|
121
|
ESAgent is not available
|
The ESAgent component is missing. This component is necessary to connect to the central protection server.
|
122
|
Firewall is not available
|
Cannot control network connections as the Firewall component is missing or failed to start. This module is used to redirect connections.
|
123
|
Network Checker is not available
|
Cannot control network connections as the Network Checker component is missing or failed to start. The module is used to scan the downloaded files.
|
124
|
CloudD is not available
|
The CloudD component required for connection to Dr.Web Cloud service is missing.
|
125
|
Unexpected error
|
Unexpected error occurs in operation of one of the components.
|