|
|
The following table identifies the Double-Take events. The event ID is followed by the event message. Below the ID and message you will find the following information.
1: This evaluation period has expired. Mirroring and replication have been stopped. To obtain a license, please contact your vendor.
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Error
Required response—Contact your vendor to purchase either a single or site license.
2: The evaluation period expires in %1 day(s).
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Information
User action required—Contact your vendor before the evaluation period expires to purchase either a single or site license.
3: The evaluation period has been activated and expires in %1 day(s).
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Information
User action required—Contact your vendor before the evaluation period expires to purchase either a single or site license.
4: Duplicate activation codes detected on machine %1 from machine %2.
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Warning
User action required—If you have an evaluation license or a site license, no action is necessary. If you have a single license, you must purchase either another single license or a site license.
5: This product edition can only be run on Windows Server or Advanced Server running the Server Appliance Kit.
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Error
User action required—Verify your activation code has been entered correctly and contact CustomerCare.
200: ExchFailover failover from %1 to %2 was started in commit mode. See log file %3 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Information
User action required—See the specific log message for additional details.
201: ExchFailover failover from %1 to %2 was started in test mode. See log file %3 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Information
User action required—See the specific log message for additional details.
202: ExchFailover failback to %1 from %2 was started in commit mode. See log file %3 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Information
User action required—See the specific log message for additional details.
203: ExchFailover failback to %1 from %2 was started in test mode. See log file %3 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Information
User action required—See the specific log message for additional details.
204: ExchFailover setup started for server %1. See log file %2 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Information
User action required—See the specific log message for additional details.
205: ExchFailover was unable to open the default log file. A new log file has been created. All messages will be log in %1.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Error
User action required—See the specific log message for additional details.
210: ExchFailover completed. Moved %1 users in %2 mail stores in %3 seconds. Check log file %4 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Success
User action required—See the specific log message for additional details.
211: ExchFailover completed with warnings. Moved %1 users in %2 mail stores in %3 seconds. Check log file %4 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Warning
User action required—See the specific log message for additional details.
212: ExchFailover completed. Tested %1 users in %2 mail stores in %3 seconds. Check log file %4 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Success
User action required—See the specific log message for additional details.
213: ExchFailover completed with warnings. Moved %1 users in %2 mail stores in %3 seconds. Check log file %4 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Warning
User action required—See the specific log message for additional details.
214: ExchFailover setup completed. Updated %1 mail stores in %2 seconds. Check log file %3 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Success
User action required—See the specific log message for additional details.
220: ExchFailover start failed. Could not open log file: %1.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Error
User action required—Restart failover. Contact CustomerCare if this event occurs again.
221: ExchFailover start failed. Invalid command line arguments. See log file %1 for details.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Error
User action required—See the specific log message for additional details.
222: ExchFailover start failed. Double-Take is not licensed on this machine.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Error
User action required—Verify your activation code has been entered correctly and contact CustomerCare.
223: ExchFailover start failed due to an Active Directory error.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Error
User action required—Restart failover. Contact CustomerCare if this event occurs again.
224: ExchFailover failed to find one (or both) of the Exchange servers. Check the server names. This can also occur if the process does not have sufficient privileges to access Active Directory.
Event log—Application
Source—ExchFailover
Category—None
Type or Level—Error
User action required—Verify the Exchange server names and the account has sufficient privileges to update Active Directory.
1000: An exception occurred: %1
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
1001: The Double-Take counter DLL could not initialize the statistics handler object to gather performance data.
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
1002: The Double-Take counter DLL could not map shared memory file containing the performance data.
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
1003: The Double-Take counter DLL could not open the "Performance" key in the Double-Take section of the registry.
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
1004: The Double-Take counter DLL could not read the "First Counter" value under the Double-Take\Performance Key.
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
1005: The Double-Take counter DLL read the "First Help" value under the Double-Take\Performance Key.
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
1006: The Double-Take counter DLL could not create event handler for the worker thread.
Event log—Application
Source—DTCounters
Category—None
Type or Level—Error
User action required—Run the installation and select Repair. Contact CustomerCare if this event occurs again.
3000: Logger service was successfully started.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
3001: Logger service was successfully stopped.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4000: Kernel was successfully started.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4001: Target service was successfully started.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4002: Source service was successfully started.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4003: Source service was successfully stopped.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4004: Target service was successfully stopped.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4005: Kernel was successfully stopped.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4006: Service has aborted due to the following unrecoverable error: %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Restart the Double-Take service.
4007: Auto-disconnecting from %1 (%2) for Replication Set %3, ID: %4 due to %5
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—The connection is auto-disconnecting because the disk-based queue on the source has been filled, the service has encountered an unknown file ID, the target server has restarted, or an error has occurred during disk queuing on the source or target (for example, Double-Take cannot read from or write to the transaction log file).
4008: Auto-disconnect has succeeded for %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4009: Auto-reconnecting Replication Set %1 to %2 (%3)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4010: Auto-reconnect has succeeded connecting Replication Set %1 to %2 (%3)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4011: Auto-reconnect has failed connecting Replication Set %1 to %2 (%3)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Manually reestablish the job to target connection.
4012: %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—This is a placeholder message for many other messages. See the specific log message for additional details.
4013: %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—This is a placeholder message for many other messages. See the specific log message for additional details.
4014: Service has started network transmission.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4015: Service has stopped network transmission.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4016: Service has established a connection to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4017: Service has disconnected from %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4018: %1, however, mirroring and replication have been disabled as a restore is required due to a previous failover.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Perform a restoration.
4019: Service has started a mirror to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4020: Service has paused a mirror to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4021: Service has resumed a mirror to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4022: Service has stopped a mirror to %1 for Replication Set %2, ID: %3, %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4023: Service has completed a mirror to %1 %2 for Replication Set %3, ID: %4, %5
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4024: Service has started Replication to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4025: Service has stopped Replication to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4026: The target has been paused due to user intervention.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4027: The target has been resumed due to user intervention.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4028: Registration of service class with Active Directory failed. Verify that the Active Directory server is up and the service has the proper permissions to update its entries.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify that the Active Directory server is running and that the Double-Take service has permission to update Active Directory.
4029: Registration of service instance with Active Directory failed. Verify that the Active Directory server is up and the service has the proper permissions to update its entries.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify that the Active Directory server is running and that the Double-Take service has permission to update Active Directory.
4030: RSResource.dll has an unknown error. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4031: RSResource.dll could not be opened. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4032: The RSResource.dll component version does not match the component version expected by the product. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4033: RSResource.dll build version is invalid. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4034: Error verifying the service name. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4035: Error verifying the product name. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4036: Error verifying the vendor name. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4037: Error verifying the vendor URL name. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4038: Error verifying the product code. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4039: Error while reading RSResource.dll. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4040: The product code is illegal for this computer hardware. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4041: The product code is illegal for this operating system version. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4042: The product code requires installing the Windows Server Appliance Kit. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4043: This product can only be run on a limited number of processors and this server exceeds the limit. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact CustomerCare if this error persists.
4044: An error was encountered and replication has been stopped. It is necessary to stop and restart the service to correct this error.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Contact CustomerCare if this error persists.
4045: %1 value must be between 1025 and 65535. Using default of %2.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify that the Double-Take port value you are trying to use is within the valid range. If it is not, it will automatically be reset to the default value.
4046: This service failed to start because of a possible port conflict. Win32 error: %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Verify that the Double-Take ports are not conflicting with ports used by other applications.
4047: Could not load ZLIB DLL %1. Some levels of compression will not be available.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—The compression levels available depend on your operating system. You can reinstall the software, using the installation Repair option, to install a new copy of the DynaZip.dll, or contact CustomerCare if this error persists.
4048: Service has started a delete orphans task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4049: Service has paused a delete orphans task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4050: Service has resumed a delete orphans task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4051: Service has stopped a delete orphans task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4052: Service has completed a delete orphans task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4053: Service has started a restore task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4054: Service has paused a restore task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4055: Service has resumed a restore task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4056: Service has stopped a restore task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4057: Service has completed a restore task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4058: Service has started a verification task to %1 (%2) for Replication Set %3, ID: %4, Checksum: %5
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4059: Service has paused a verification task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4060: Service has resumed a verification task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4061: Service has stopped a verification task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4062: Service has completed a verification task to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4063: Bandwidth limit to %1 (%2) has changed to %3.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4064: Bandwidth limit to %1 (%2) is now in the "%3" period at %4.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4065: Target data state for connection %1 from %2 (%3) has changed because %4.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—No action required.
4066: The product code requires a virtual server environment. The product functionality has been disabled.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—The activation code you are using is for the Virtual SystemsTM edition. This code will not work on non-virtual server environments.
4067: No replication ops have been received from the driver for an extended period of time.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Check other messages for errors with the Double-Take drivers and correct as required. If there are no driver messages, verify that your drives are connected to the source. If this error persists, contact CustomerCare.
4068: Failed to write to a replicating volume.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Reboot the source server. Contact CustomerCare if this event occurs again.
4069: The option MoveOrphansDir has been updated because it was missing or empty.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—No action required.
4070: An error occurred while reading data for connection %1. All data needs to be remirrored. See the log for details.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Initiate a remirror to guarantee data integrity. Contact CustomerCare if this event occurs repeatedly.
4096: The registry parameter %2 is unknown.
Event log—System
Source—RepDrv
Category—None
Type or Level—Warning
User action required—Delete the parameter and report this issue to CustomerCare.
4097: Failed to initialize WMI support. The last Word in the Data Window is the NT status code.
Event log—System
Source—RepDrv, RepKap, RepHsm, or RepSis
Category—None
Type or Level—Warning
User action required—No action required.
4097: The file system filter failed to load. Replication will not occur. Reboot your server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Reboot your server and contact CustomerCare if this event occurs again.
4098: The registry parameters failed to load, so the default configuration values will be used. The last Word in the Data window is the NT status code.
Event log—System
Source—RepKap
Category—None
Type or Level—Warning
User action required—No action required.
4098: The control device %2 was not created. Communication with the service will be disabled. Reboot the server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepDrv, RepDac, RepKap, or RepHsm
Category—None
Type or Level—Error
User action required—Reboot your server and contact CustomerCare if this event occurs again.
4099: The driver detected a hard link for a file on drive %2. Hard links are not supported. Changes to this file will not be replicated.
Event log—System
Source—RepDrv
Category—None
Type or Level—Warning
User action required—Hard links are not supported.
4099: The driver failed to register with filter manager. Reboot the server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Reboot your server and contact CustomerCare if this event occurs again.
4100: Product activation code is invalid. Please check that it is typed correctly and is valid for the version of the operating system in use.
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Error
User action required—If you are in the process of installing Double-Take, verify that you are using a 24-character alphanumeric code. If Double-Take is already installed, confirm that the code entered is correct. If the code appears to be correct, contact CustomerCare.
4100: The versions of the driver and the filter driver do not match. Replication will not occur. Reboot your server. If this error occurs again, reinstall the software. Contact technical support if this error occurs after the software has been reinstalled. The last three Words in the Data window are the NT status code and the driver version numbers.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Reboot your server. Reinstall the software if this event occurs again. Contact CustomerCare if this event occurs after reinstalling the software.
4101: This service will not run on this device. Contact your sales representative for upgrade procedures.
Event log—Application
Source—Double-Take
Category—ActivationKey
Type or Level—Error
User action required—The activation code does not match the type of server you are attempting to run on. Contact your vendor for a new activation code or contact CustomerCare.
4110: Target cannot write %1 due to target disk being full. Operation will be retried (%2 times or forever)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—The disk on the target is full. The operation will be retried according to the TGExecutionRetryLimit setting.
4111: Target can not write %1 due to a sharing violation. Operation will be retried (%2 times or forever)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—A sharing violation error is prohibiting Double-Take from writing on the target. The operation will be retried according to the TGExecutionRetryLimit setting.
4112: Target can not write %1 due to access denied. Operation will be retried (%2 times or forever)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—An access denied error is prohibiting Double-Take from writing on the target. The operation will be retried according to the TGExecutionRetryLimit setting..
4113: Target can not write %1 due to an unknown reason. Operation will be retried (%2 times or forever). Please check the log files for further information on the error.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—An unknown error is prohibiting Double-Take from writing on the target. The operation will be retried according to the TGExecutionRetryLimit setting.
4120: Target write to %1 was completed successfully after %2 retries.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4150: Target write %1 failed after %2 retries and will be discarded. See the event log or log files for error conditions. After correcting the problem, you should re-mirror or run a verify to resynchronize the changes.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—The operation has been retried according to the TGExecutionRetryLimit setting but was not able to be written to the target and the operation was discarded. Correct the problem and remirror the files.
4155: The service was unable to complete a file system operation in the allotted time. See the log files for error conditions. After correcting the problem, remirror or perform a verification with remirror to synchronize the changes.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Correct the file system error and then remirror or perform a verification with remirror to synchronize the changes.
4200: In band task %1 submitted from %2 by %3 at %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4201: In band task %1 discarded (submitted from %2 by %3 at %4)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—A task may be discarded in the following scenarios: all connections to a target are manually disconnected, replication is stopped for all connections to a target, or an auto-disconnect occurs. If one of these scenarios did not cause the task to be discarded, contact CustomerCare.
4202: Running %1 in band script: %2 (task %3 submitted from %4 by %5 at %6)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4203: Completed run of in band script: %1 (exit code %2)
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4204: Error running in band script: %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Review the task and its associated script(s) for syntax errors.
4205: Timeout (%1 seconds) running in band script: %2
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—The timeout specified for the script to complete has expired. Normal processing will continue. You may need to manually terminate the script if it will never complete.
4206: Run timeout disabled for in band script: %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—The timeout period was set to zero (0). Double-Take will not wait for the script to complete before continuing. No action is required.
4207: In band scripts disabled by server - no attempt will be made to run %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Enable task command processing.
4300: A connection request was received on the target before the persistent target paths could be loaded.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—You may need to stop and restart your job.
4301: Unable to block target paths, the driver is unavailable.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—If you need to block your target paths, contact CustomerCare.
4302: Target Path %1 has been successfully blocked
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4303: Blocking of target path: %1 failed. Error Code: %2
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—If you need to block your target paths, contact CustomerCare.
4304: Target Path %1 has been successfully unblocked
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4305: Unblocking of target path: %1 failed. Error Code: %2
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—If you need to unblock your target paths, contact CustomerCare.
4306: Target paths for source %1 (%2) Connection id: %3 are already blocked
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—No action required.
4307: Target paths for source %1 (%2) Connection id: %3 are already unblocked
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—No action required.
4308: Error loading target paths for blocking, registry key %1 has been corrupted.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—If you need to block your target paths, contact CustomerCare.
4400: Failed to create snapshot set for source %1 (%2) Connection ID: %3. Error: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—The snapshot could not be created. This may be due to a lack of disk space or memory or another reason. The error code is the Microsoft Volume Shadow Copy Service (VSS) error. Check your VSS documentation or contact CustomerCare.
4401: Failed to delete automatic snapshot set for source %1 (%2) Connection ID: %3. Error: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—The automatic snapshot could not be deleted. This may be due to a lack of memory, the file does not exist, or another reason. The error code is the Microsoft Volume Shadow Copy Service (VSS) error. Check your VSS documentation or contact CustomerCare.
4402: Failed to delete snapshot set for source %1 (%2) Connection ID: %3. Error: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—The snapshot could not be deleted. This may be due to a lack of memory, the file does not exist, or another reason. The error code is the Microsoft Volume Shadow Copy Service (VSS) error. Check your VSS documentation or contact CustomerCare.
4403: A scheduled snapshot could not be created for source %1 (%2) Connection ID: %3. because the target data was in a bad state. A snapshot will automatically be created when the target data reaches a good state.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—No action required. A snapshot will automatically be created when the target data reaches a good state.
4404: Set snapshot schedule for source %1 (%2) connection %3 to every %4 minutes. Next snapshot: %5.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4405: Removed snapshot schedule for source %1 (%2) connection %3.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4406: Enabled snapshot schedule for source %1 (%2) connection %3.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4407: Disabled snapshot schedule for source %1 (%2) connection %3.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
4408: %1 was unable to move some orphans for source %2 on connection ID %3. Check the %1 logs for further details.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Orphan files could not be moved. For example, the location could be out of disk space. Check the Double-Take log for more information.
4409: %3 was unable to delete some orphans for source %1 on connection ID %2. Check the %3 logs for further details.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Orphan files could not be deleted. Check the Double-Take log for more information.
4410: The registry hive dump failed with an of error: %1.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Error
User action required—Contact CustomerCare.
4411: The Service has detected that port %1 is being %2 by the Windows Firewall.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—The firewall port needs to be unblocked or restrictions against Double-Take removed so that Double-Take data can be transmitted.
5000: Server Monitor service was successfully started.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
5001: Server Monitor service was successfully stopped.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
5002: Placeholders were modified to %1.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
5100: Failover completed for %1.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5101: IP address %1 with subnet mask %2 was added to target machine's %3 adapter.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5102: %1 has reached a failover condition. A response from the user is required before failover can take place.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Warning
User action required—User intervention has been configured. Open the Failover Control Center and accept or decline the failover prompt.
5103: Started adding drive shares from %1 to %2.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5104: %1 drive shares were taken over by %2.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5105: Attempting to run the %1 script.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5106: The %1 script ran successfully.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5107: Error occurred in running %1 script.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Error
User action required—Verify that the script identified exists with the proper permissions.
5108: The source machine %1 is not responding to a ping.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Error
User action required—This occurs when all monitored IP addresses on the source machine stop responding to pings. Countdown to failover will begin at the first occurrence and will continue until the source machine responds or until failover occurs.
5109: The public NIC on source machine %1 is not responding to a ping.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Error
User action required—The failover target did not receive an answer to its ping of the source machine. Eventually, a failover will result. Investigate possible errors (down server, network error, and so on).
5110: The %1 script "%2" is still running.
Event log—Application
Source—Double-Take
Category—Failover
Type or Level—Information
User action required—No action required.
5200: Failback completed for %1.
Event log—Application
Source—Double-Take
Category—Failback
Type or Level—Information
User action required—No action required.
5201: IP address %1 was removed from target machine's %2 adapter.
Event log—Application
Source—Double-Take
Category—Failback
Type or Level—Information
User action required—No action required.
5202: Unable to Failback properly because IP address %1 was missing a corresponding SubNet Mask.
Event log—Application
Source—Double-Take
Category—Failback
Type or Level—Error
User action required—Contact CustomerCare.
5300: The following IP address was added to target's monitoring list: %1
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Information
User action required—No action required.
5301: The following IP address was removed from target's monitoring list: %1
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Information
User action required—No action required.
5302: Drive share information for %1 has been updated on the target machine.
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Information
User action required—No action required.
5303: The application monitor script has started successfully.
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Information
User action required—No action required.
5304: The application monitor script has finished successfully.
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Information
User action required—No action required.
5305: The application monitor has found the %1 service stopped.
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Warning
User action required—Application Manager will attempt to restart the service.
5306: The application monitor has restarted the %1 service.
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Warning
User action required—No action required.
5307: The application monitor cannot contact the server %1.
Event log—Application
Source—Double-Take
Category—Monitoring
Type or Level—Error
User action required—Verify the server is running. Verify available network communications with the server.
5400: Broadcasted new MAC address %1 for IP address %2.
Event log—Application
Source—Double-Take
Category—ARP
Type or Level—Information
User action required—No action required.
5500: Could not connect to e-mail server. Check to make sure the SMTP server %1 is available (error code: %2).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Double-Take could not connect to your SMTP server or the username and/or password supplied is incorrect. Verify that SMTP server is available and that you have identified it correctly in your e-mail notification configuration. Also verify that your username and password have been entered correctly.
5501: E-mail notification could not be enabled (error code: %1).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—This alert occurs if there is an unexpected error enabling e-mail notification during service startup. Check to see if any other errors related to e-mail notification have been logged. Also, check to make sure the Windows Management Instrumentation (WMI) service is enabled. If neither of these apply, contact CustomerCare.
5502: E-mail notification could not be initialized. Check to make sure Internet Explorer 5.0 or later is installed.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—E-mail notification no longer requires Internet Explorer 5.0 or later. If you receive this error, contact CustomerCare.
5503: E-mail notification could not be processed. Check to make sure the correct version of SMTPMail.DLL is registered on the system (error code: %1).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—If you are using Double-Take 4.4.2.1 or earlier and Windows NT 4.0, e-mail notification requires Windows Management Instrumentation (WMI) to be installed. Verify that you have it installed on the Double-Take server.
5504: Could not load LocalRS.dll (for e-mail notification).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—This alert occurs if there is an error loading the resource DLL for the service. Typically, this is caused by a missing LocalRS.dll file. Reinstall the software, using the installation Repair option, to install a new copy of the LocalRS.dll. Contact CustomerCare if this error persists.
5505: E-mail could not be sent. Check e-mail settings (error code: %1).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify that the e-mail server that you have identified in your e-mail notification configuration is correct.
5506: One or more required e-mail settings have not been specified (error code: %1).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—At a minimum, you must specify the e-mail server, the From and To addresses, and at least one type of event to include.
5507: E-mail notification could not be initialized. Check to make sure WMI is installed and available (error code: %1).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—If you are using Double-Take 4.4.2.1 or earlier and Windows NT 4.0, e-mail notification requires Windows Management Instrumentation (WMI) to be installed. Verify that you have it installed on the Double-Take server.
5508: An error occurred connecting to the WMI namespace. Check to make sure the Windows Management Instrumentation service is not disabled (error code %1).
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—This alert occurs if there is an error with the Windows Management Instrumentation (WMI) service. Verify that you have it installed on the Double-Take server and that it is enabled.
5600: Part or all of the e-mail setting %1 is not in a valid format.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify that the include categories and exclude ID list are identified and formatted correctly.
6000: %1
Event log—Application
Source—Double-Take Management Service
Category—None
Type or Level—Information
User action required—This is a placeholder message for many other messages. See the specific log message for additional details.
6001: %1
Event log—Application
Source—Double-Take Management Service
Category—None
Type or Level—Warning
User action required—This is a placeholder message for many other messages. See the specific log message for additional details.
6002: %1
Event log—Application
Source—Double-Take Management Service
Category—None
Type or Level—Error
User action required—This is a placeholder message for many other messages. See the specific log message for additional details.
6100: The job "%1" has begun provisioning a replica for %2.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6101: The job "%1" has successfully completed provisioning a replica for %2.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6102: The job "%1" has failed to provision a replica for %2. %3
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Error
User action required—Review the additional error information to identify the problem. Correct the problem and retry the operation. Contact CustomerCare if this event occurs again.
6110: The job "%1" has begun a %2 failover of the replica of %3.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6111: The job "%1" has successfully completed a %2 failover of the replica of %3.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6112: The job "%1" has encountered an error while performing a %2 failover of the replica of %3. %4
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Error
User action required—Review the additional error information to identify the problem. Correct the problem and retry the operation. Contact CustomerCare if this event occurs again.
6120: The job "%1" has begun undoing the failover for the replica of %2.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6121: The job "%1" has successfully reattached the replica and resumed protecting %2.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6122: The job "%1" has encountered an error undoing the failing over for the replica of %2. %3
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Error
User action required—Review the additional error information to identify the problem. Correct the problem and retry the operation. Contact CustomerCare if this event occurs again.
6130: The job "%1" has begun reversing the direction of the protection of %2.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6131: The job "%1" has successfully reversed the direction of the protection of %2.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6132: The job "%1" has encountered an error reversing the direction of the protection of %2. %3
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Error
User action required—Review the additional error information to identify the problem. Correct the problem and retry the operation. Contact CustomerCare if this event occurs again.
6140: The job "%1" is being deleted.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6141: The job "%1" has successfully been deleted.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
6142: The job "%1" has encountered an error while being deleted. %2
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Error
User action required—Review the additional error information to identify the problem. Correct the problem and retry the operation. Contact CustomerCare if this event occurs again.
6150: The job "%1" protecting %2 has completed its mirror.
Event log—Application
Source—Double-Take Virtual Recovery Assistant
Category—Service
Type or Level—Information
User action required—No action required.
7106: The driver was unable to get valid name information from the Filter Manager for the file %2. (Filename may be truncated.) It cannot be replicated. Please contact technical support.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
7107: The driver was unable to get valid name information from the Filter Manager for a file. It cannot be replicated. Please contact technical support.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
8100: The driver encountered an unrecoverable internal error. Contact technical support. The last Word in the Data window is the internal error code.
Event log—System
Source—RepDac
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
8192: Driver failed to allocate Kernel memory. Replication is stopped and server must be rebooted for replication to continue. The last word in the data window is the tag of the allocation that failed.
Event log—System
Source—RepDrv, RepKap, or RepHsm
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8192: Kernel memory is exhausted. Replication is stopped. This may have been caused by low system resources.
Event log—System
Source—RepDrv or RepHsm
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8192: Problem loading registry parameters. The last Word in the Data Window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Warning
User action required—An error occurred attempting to load configuration settings from the registry for the RepSIS filter driver. Default values will be used.
8193: The driver failed to create a thread required for normal operation. This may have been caused by low system resources. Reboot your server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8193: Failed to initialize WMI support. The last Word in the Data Window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Warning
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8194: Volume was dismounted. This message is only a warning. If you receive this message repeatedly, contact technical support. The last Word in the Data window is the volume pFltObjects->Volume.
Event log—System
Source—RepSis
Category—None
Type or Level—Warning
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8196: The maximum amount of memory for replication queuing has been reached. Replication is stopped and memory is being freed.
Event log—System
Source—RepDrv
Category—None
Type or Level—Warning
User action required—Contact CustomerCare if this event occurs again.
8198: The driver registry path could not be saved. The default registry path will be used.
Event log—System
Source—RepDrv, RepKap, or RepHsm
Category—None
Type or Level—Warning
User action required—No action required.
8200: The driver failed to allocate a buffer for a file name longer than 260 characters. The file will be skipped. The last Word in the Data window is the NT status code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Warning
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8240: The control device %1 was not created. Communication with the deduplication service will be disabled. Contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8242: The driver failed to register with filter manager. Reboot the server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Deduplicated data will not be accessible and no further candidate processing will occur. Reboot the server and contact CustomerCare if the event occurs again.
8243: The driver failed to Queue a Recall. This could be due to system resource limitations. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8244: The driver failed to Recall file %1 . The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8245: The driver failed to Query a Recall related file %2 . This could be due to system resource limitations. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8246: The driver failed to read from a Common Store file during recall. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8247: The driver failed to write to a link file during recall. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8248: The driver failed to obtain information from the reparse point of a recall candidate file. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8249: The driver failed to open the Common Store file, recall has failed. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8250: The driver failed to create/set stream and handle contexts during PostCreate, we cannot track the file - FATAL ERROR. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8251: The driver failed to failed to initialize cancel safe queue. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8252: The driver failed to failed to initialize cancel safe queue. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8253: The driver failed to set stream context, we cannot track the file - FATAL ERROR. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8254: The driver failed to set stream context, we cannot track the file - FATAL ERROR. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
8255: The driver failed to attach to a mounted volume of interest. The last Word in the Data window is the NT status code.
Event log—System
Source—RepSis
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
9000: The driver has failed to process a rename operation. The driver will resend the rename operation. This message is only a warning. If you receive this message repeatedly, contact technical support. The last Word in the Data window is the NT status code.
Event log—System
Source—RepKap
Category—None
Type or Level—Warning
User action required—Contact CustomerCare if this event occurs again.
9100: The driver encountered an error opening a file from the service. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9101: The driver encountered an error reading from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9102: The driver encountered an error writing to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9103: The driver encountered an error writing to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9104: The driver encountered an error querying for file security from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9105: The driver encountered an error querying for file security from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9106: The driver encountered an error writing file security data to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9107: The driver encountered an error querying for an allocated range from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9108: The driver encountered an error querying for an allocated range from the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9109: The driver encountered an error writing an allocated range to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9110: The driver encountered an error querying for a directory from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9111: The driver encountered an error querying for a directory from the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9112: The driver encountered an error writing a directory query to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9113: The driver encountered an error querying a stream from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9114: The driver encountered an error writing a stream query to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9115: The driver encountered an error writing a stream query to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9116: The driver has failed to close a file handle. If you receive this message repeatedly, contact technical support. The last Word in the Data window is the NT status code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
9117: The driver encountered an error querying for extended attributes from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9118: The driver encountered an error writing extended attributes to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9119: The driver encountered an error writing extended attributes status to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9120: The driver encountered an error querying for file information from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9121: The driver encountered an error writing file information to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9122: The driver encountered an error writing file information status to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9123: The driver encountered an error querying for fsctl information from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9124: The driver encountered an error writing fsctl information to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9125: The driver encountered an error writing fsctl status to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9126: The driver encountered an error reading from the service input buffer, KFAI_OPEN_BY_FILE_ID. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9127: The driver encountered an error writing to the service output buffer, KFAI_OPEN_BY_FILE_ID. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9128: The driver encountered an error reading from the service input buffer, KFAI_QUERY_INFO. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
9129: The driver encountered an error writing to the service output buffer, KFAI_QUERY_INFO. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Check for related service messages. Contact CustomerCare if this event occurs again.
10000: This message is only a placeholder warning. The last Word in the Data window is the NT status code.
Event log—System
Source—Double-Take
Category—RepHsm
Type or Level—Warning
User action required—No action required.
10000: Connect failed to node %1 for resource %2. Adding node to reconnect list.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Error
User action required—Ensure that GeoCluster is running on all possible owners and that it can communicate on the network selected for mirroring and replication traffic. GeoCluster will try to reestablish a connection using the check unresponsive node interval specified for the resource.
10001: Reconnect succeeded to node %1 for resource %2. Will be added as a possible owner when mirror is complete.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Information
User action required—No action required.
10002: Disk check failed on node %1 for resource %2. Removing as a possible owner.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Error
User action required—Ensure that GeoCluster is running on all possible owners and that it can communicate on the public network. Also ensure that the disk specified for the resource is functioning correctly on all possible owners.
10003: Owner %1 of the quorum resource %2 couldn't access the arbitration path %3. Network may be down.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Error
User action required—Ensure that the network used to access the arbitration path is up and that the server is operational. Also ensure that the arbitration share path does exist and that the account running the cluster service has write privileges to the share path.
10004: Failover of the group %1 is being delayed. Group will be brought online when the target queue is below the limit or the timeout has expired.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—No action required.
10005: Node %1 is taking ownership of the group %2. The group will be brought online on this node.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Information
User action required—No action required.
10006: The cluster notification thread failed to start on node %1 for resource %2. The resource should be taken offline and brought back online.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—Take the resource offline and bring it back online.
10007: The user %1 has reverted a snapshot for the %2 resource on node %3.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—No action required. The snapshot you selected will be reverted.
10008: The user %1 has discarded queued data for the %2 resource on node %3.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—No action required. The queue you selected will be discarded.
10009: The user %1 is verifying data for the %2 resource on node %3.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—A snapshot of the current data has been taken. After you have verified the data, accept or reject the data.
10010: The user %1 has rejected the data for the %2 resource on node %3.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—No action required. Since the data was rejected, the data has been reverted to the snapshot taken when the data was selected for verification.
10011: The user %1 has accepted the data for the %2 resource on node %3.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—No action required. The current data will be used.
10012: The GeoCluster Replicated Disk resource %1 has been set to validate its data. No data replication is occurring to the remaining nodes in the cluster. Please Accept or Reject the data by right-clicking on the resource and selecting the appropriate option.
Event log—Application
Source—Double-Take
Category—GeoCluster
Type or Level—Warning
User action required—Replication has been stopped because of the validation request. Accept or reject the data on the node by right-clicking on the resource and selecting the appropriate option.
10100: The driver could not recall a file because it did not have a token for impersonation. The security provider service should set this token. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Contact CustomerCare if this event occurs again.
10101: The driver could not access the file in the archive bin, due to a failed impersonation attempt. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Contact CustomerCare if this event occurs again.
10102: The driver could not recall the file. The last Word in the Data window is the exception code.
Event log—System
Source—RepKap
Category—None
Type or Level—Error
User action required—Contact CustomerCare if this event occurs again.
11000: Service has started an archive to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
11001: Service has completed an archive to %1 (%2) for Replication Set %3, ID: %4, %5
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
11002: Service has started a recall from %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
11003: Service has completed a recall from %1 (%2) for Replication Set %3, ID: %4, %5
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
11004: Service has failed connection to the RepHSM driver. %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Reboot the server or manually restart the RepHSM.sys driver.
11005: Service has aborted the archive operation.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify the activation code on the source and target is valid for archiving. Reboot an unlicensed server.
11006: Service has aborted the archive recall operation.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify the activation code on the source and target is valid for archiving. Reboot an unlicensed server.
11007: Verification has finished with errors. %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Review the verification log to correct or accept the errors.
11008: Archive feature is not supported on volume %1
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—The source and target must be NTFS for archiving functionality.
11009: Service has started an archive preview to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
11010: Service has completed an archive preview to %1 (%2) for Replication Set %3, ID: %4
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Information
User action required—No action required.
11011: Service has aborted the archive preview operation.
Event log—Application
Source—Double-Take
Category—Service
Type or Level—Warning
User action required—Verify the activation code on the source and target is valid for archiving. Reboot an unlicensed server.
12000: The service has started.
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Information
User action required—This message refers to the Double-Take Recall service. No action required.
12001: The service failed to start.
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Error
User action required—Check the user name and password for the Double-Take Recall service to ensure validity. Reinstall the software if this event occurs again.
12002: The service has stopped.
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Information
User action required—This message indicates a system shutdown or the user stopped the Double-Take Recall service. No action is required.
12003: The service failed to create a stop control event. (Error %1)
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Error
User action required—Restart the Double-Take Recall service. Reinstall the software if this event occurs again.
12004: RegisterServiceCtrlHandler failed. (Error %1)
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Error
User action required—Restart the Double-Take Recall service. Reinstall the software if this event occurs again.
12005: Service encountered SetServiceStatus error (Error %1)
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Error
User action required—Restart the Double-Take Recall service. Reinstall the software if this event occurs again.
12006: Service could not get handle to driver for security update. (Error %1)
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Error
User action required—The Double-Take Recall service could not connect to the Double-Take Recall archiving driver. Reboot the server and reinstall the software if this event occurs again.
12007: Service failed a periodic security update. (Error %1)
Event log—Application
Source—Double-Take
Category—DTRecall
Type or Level—Warning
User action required—This message refers to the Double-Take Recall service. The operation will be performed every five minutes. Reinstall the software if this event occurs after five minutes.
12288: The driver encountered an error accessing a buffer from the service. Contact technical support. The last Word in the Data window is the exception code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
16384: The driver encountered an unrecoverable error. Contact technical support.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
16385: The driver encountered an unexpected internal result. Contact technical support. The last Word in the Data window is the NT status code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
16393: The driver encountered an internal error. Contact technical support. The last Word in the Data window is the internal error code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
16395: The driver detected a memory error which may have been caused by a bad driver or faulty hardware. Contact technical support. The last Word in the Data window is the internal error code.
Event log—System
Source—RepDrv or RepHsm
Category—None
Type or Level—Error
User action required—Contact CustomerCare.
16396: The driver failed to create work queues for normal operation. This may have been caused by low system resources. Reboot the server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code.
Event log—System
Source—RepDrv
Category—None
Type or Level—Error
User action required—Reboot the server and contact CustomerCare if this event occurs again.
16400: RepDrv has encountered an unexpected condition, usually caused by low kernel memory. Unless otherwise mentioned, this event has already been handled and your data remains protected. If you continue to receive these events or have further questions please contact tech support.
Event log—System
Source—RepDrv
Category—None
Type or Level—Information
User action required—No action required.