Related Topics
The following table contains error codes that you may see in the various user interfaces or in log files.
| Error Code | Description |
|---|---|
| -1 | Unknown error code (generated when a command failed but the failure is not linked to a pre-defined error code) |
| -101 | Invalid parameter was supplied |
| -102 | Command is not a valid or the syntax is incorrect |
| -103 | Double-Take Availability source module is not loaded |
| -104 | No Double-Take Availability source identified |
| -105 | Double-Take Availability target module is not loaded |
| -106 | Connection already established |
| -107 | Connection does not exist |
| -108 | Mirror currently active |
| -109 | Server does not exist or could not be located |
| -110 | Server is not responding |
| -111 | Double-Take Availability is running |
| -112 | Unknown connection error |
| -113 | Mirror already active |
| -114 | Date is invalid - valid format is mm/dd/yy |
| -115 | Time is invalid - valid format is hh:mm |
| -116 | Invalid option supplied |
| -117 | Mirror is not paused |
| -118 | Connection is not paused |
| -119 | Connection does not exist |
| -120 | Connection already connected |
| -121 | Mirror is not running |
| -122 | Replication set exists |
| -123 | Replication set does not exist |
| -124 | No replication set has been selected |
| -125 | Connection is replicating |
| -126 | Connection is not replicating |
| -127 | Replication set is enabled |
| -128 | Schedule is not defined |
| -129 | Replication set is changed |
| -130 | Replication set is in use |
| -131 | No Double-Take Availability target identified |
| -132 | Memory is low |
| -133 | Memory is sufficient |
| -134 | Replication is pending |
| -135 | Invalid option supplied |
| -136 | Replication set rule does not exist |
| -137 | Mirror queue is full |
| -138 | Insufficient security access |
| -139 | Schedule command is invalid |
| -140 | Source path is invalid |
| -141 | Replication set is not changed |
| -142 | Insufficient source security access |
| -143 | Invalid statistics file |
| -144 | Replication set not saved |
| -145 | Connection failed |
| -146 | Cleaner option is not enabled |
| -147 | Target mirror capacity high threshold is met |
| -148 | Target mirror capacity low threshold is met |
| -149 | New option applied |
| -150 | Target is restarted |
| -151 | Replication is out of memory |
| -152 | Write access is blocked on the volume |
| -153 | This error code could be one of two errors. 1) Compression level is not supported, or server does not support compression 2) Transmission is paused |
| -154 | Transmission is active |
| -155 | Target does not support the command |
| -156 | Command conversion to accommodate a different Double-Take Availability version has failed |
| -157 | Incompatible source and target Double-Take Availability versions |
| -158 | Incompatible source and target operating system versions |
| -159 | NAS server to non-NAS server is not a supported configuration |
| -160 | Target module is not loaded |
| -161 | Operation or command is not supported |
| -162 | Target is paused |
| -163 | Target is pending |
| -164 | Target is active |
| -165 | Target is retrying operations |
| -166 | Target is no longer retrying operations |
| -167 | Restore required state is unknown |
| -168 | Not a valid failover source |
| -169 | Failover login failed |
| -170 | Feature is not supported |
| -171 | Command is not supported |
| -172 | Target queue log file error |
| -173 | Target disk is full |
| -174 | Target disk has sufficient disk space |
| -175 | Error reading from or writing to the queue log file |
| -176 | Memory-based queue is in use |
| -177 | Disk-based queue is in use |
| -178 | Restore is required |
| -179 | ID the driver supplied to the service is invalid |
| -180 | Child path is blocked |
| -181 | Parent path is blocked |
| -182 | Target path blocking is disabled |
| -183 | Connection ID specified is invalid |
| -184 | No command objects are in the queue |
| -185 | Target is discarding operations from the target queue |
| -186 | Target is not discarding operations from the target queue |
| -187 | Schedule is paused |
| -188 | Schedule is resumed |
| -189 | Target state has changed |
| -190 | Target name has changed |
| -201 | Monitor name exists |
| -202 | Monitor name does not exist |
| -203 | Monitor configuration exists |
| -204 | Monitor configuration does not exist |
| -205 | Monitor configuration is in use |
| -206 | Monitor configuration is not in use |
| -207 | Source is online |
| -208 | Source is offline |
| -209 | Server is not failed over |
| -210 | Server is failed over |
| -211 | Server is not being monitored |
| -212 | Failback is in progress |
| -213 | IP address placeholders on the target are unavailable |
| -214 | Target NIC was not found |
| -215 | Source module is not loaded |
| -216 | Failed to set the source state |
| -217 | Unable to ping source |
| -218 | Invalid argument |
| -219 | Recovery is busy |
| -220 | Invalid command |
| -221 | Recovery is started |
| -222 | Script failed to start |
| -223 | Script timeout met |
| -224 | No replication timeout met - connection is bad |
| -225 | Invalid path |
| -226 | Kernel module is not loaded |
| -2201 | Error communicating with e-mail server |
| -2202 | Error connecting to e-mail server |
| -2203 | E-mail notification is disabled |
| -2204 | E-mail notification is enabled |
| -2205 | E-mail notification requires Internet Explorer version 5.0 and WMI |
| -2206 | E-mail notification requires Internet Explorer version 5.0 |
| -2207 | Error sending e-mail |
| -2208 | Error sending test e-mail |
| -2209 | WMI error connecting to e-mail server |
| -2210 | E-mail notification requires WMI |
| -2211 | Event Viewer settings for e-mail notification are invalid |
| -2212 | E-mail notification setting is invalid |
| -2213 | E-mail notification address exists |
| -2214 | E-mail notification alert ID is invalid |
| -2215 | E-mail notification format is invalid |
| -2216 | E-mail notification address does not exist |
| -2217 | E-mail notification address notification list is empty |
| -2218 | E-mail warning is not set |
| -2219 | E-mail test warning is not set |
| 2200 | E-mail notification is functioning properly |
| -2301 | Bandwidth limiting time exists |
| -2302 | Bandwidth limiting name exists |
| -2303 | Bandwidth limit not found |
| -2304 | Bandwidth limit day is invalid |
| -2305 | Bandwidth limit label is invalid |
| -2401 | Snapshot module is not loaded |
| -2402 | Error reading the snapshot .dll |
| -2403 | Snapshot not found |
| -2404 | No snapshot connections found |
| -2501 | Full-server functionality is disabled |
| -2502 | No full-server interface available |