Known Issues

• Upgrades from early versions of ImageManager may require Repair install after reboot. If you upgrade from ImageManager version 6.5.1 or earlier you may need to run a Repair install if the service does not start after the reboot.
• In some rare situations the ImageManager Service may crash when used for ShadowStream Replication. Fixes have been made that will make this much less likely to occur.
• In some very rare situations the ShadowStream Service may crash. Normally the service can be restarted and replication will continue. If this occurs, you should contact Arcserve and we will investigate. If you have a memory dump for the crashed service you can provide it to Arcserve support.
• Upgrades from earlier versions of ImageManager
• If you upgrade from an earlier version of ImageManager (6.5.1 or earlier) you may need to run a Repair install if the service does not start after the reboot.
• ShadowStream Replication fails: SST-Error(10): Connection Lost:
• In some rare situations, an ImageManager ShadowStream Replication Job may fail with the following error message:
• "ShadowStream Send Failure - SST-Error(10): Connection Lost"
• and
• "send error: Connection Lost"
• ShadowStream has been updated to improve the way it handles these kinds of failure conditions. It is worth noting that these kinds of failures can be caused by a firewall that is blocking the UDP traffic used by ShadowStream.
• HSR to VHDX fails with -87 Parameter is incorrect. If you perform an HSR of a volume that is close to the maximum size of an MBR disk (i.e, 2TB) you would encounter the following error: sbrest 411 Cannot create partition on virtual disk D:\F_VOL_SYS-b001.vhdx (-87 The parameter is incorrect.) and the HSR Job would fail.
• This error occurs because Arcserve requires a very small amount of space on the volume HSR related meta data. This would result in a volume larger than the 2TB size limit (232 × 512 bytes) being associated with the default MBR partitioning style which is used by HSR when writing virtual disks.
• To prevent this error, you can shrink the Source volume by a few MBs. In a future release, the Arcserve HSR will detect if the Source volume is close to the 2TB limit (within a few MB) and use the GPT partitioning style within the VHDX file, rather than MBR.
• "Unknown error occurred": Incorrect Wizard behavior when trying to uninstall. In some rare situations, you may encounter an "Unknown Error" when installing or upgrading ImageManager. This happens in the following situations:
1. An install on a server OS that only had .Net 4.0/4.5 installed. One of the components in the installer is not configured to run on these versions of .Net and so an error was generated. The error occurs at the end of the install wizard but is benign. ImageManager still installs just fine.
2. During a "Repair" install where the machine is not restarted afterwards. If you then run the installer again, the install wizard will pop up a prompt to install, but the text is missing from the installation path field. After running the installation, the wizard shows "Unknown error occurred"
3. To avoid this error, you must restart your computer after running a Repair install.
• ImageManager will not run if the FIPS security mode is enabled. It is possible to configure Windows .Net so that only FIPS compliant encryption algorithms are used for .Net applications. This is also something that you can configure in Group Policies using:
• GPO_name\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options.
• This setting may prevent ImageManager from running. However, you can avoid this problem with a simple change to the ImageManager configuration file.
• To prevent the error above, you can make the following change to the ImageManager.exe.config file:
• Search for the <runtime> tag which currently has:
• Copy

  <runtime>
  <generatePublisherEvidence enabled="false"/>
  </runtime>

• and after the generatePublisherEvidence entry add the following:
• Copy

  <enforceFIPSPolicy enabled="false"/>

• Save the file and then restart the service for the setting to take effect.
• In some situations, it may appear that an ImageManager Replication Job is re-sending files that it has already sent successfully. This happens after restarting the ImageManager service. In this case some replication jobs requeue the files in the managed folder and attempts to resend them. This is not a bug but it can occur in two situations: (1) When the replication job is deleted and recreated it causes ImageManager to lose history of what has been sent so it resends files that have been deleted on the target. (2) Changing the replication mode to "No ImageManager running remotely."
• When replicating files via FTP, it is possible to receive the following error: "unable to set file time: Command not understood. (code=500)" This is a known limitation of some FTP Servers, including the IIS FTP server.
• The HSR - Getting error "Can not create partition greater than disk size" (even though the target disk is larger than volume size) when trying to set up the job again to the ESX server.