Known Issues

If you upgrade from ImageManager version 6.5.1 to any newer version you need to do a repair install. In some cases when trying to install ImageManager 6.7.6 the service fails to start. It displays error 1067 "Process unexpectedly terminated". You can resolve this problem (in most cases) by doing a repair installation. In some cases, you may need to uninstall ImageManager and then do a fresh installation.
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 this error, you can make the following change to the ImageManager.exe.config file:

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. Restarting the service causes 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 re-queue 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.