Another Good Reason to Recommend Upgrading an Image Capture System

I recently had a ticket I found to be very interesting. As I started to dig into the issue with an older version of an imaging capture system and I soon realized that .NET 2.0 was not supported, and manufacture recommended their customers to uninstall the .NET 2.0 framework. As you know that’s very hard to do in today’s world so they came up with an unsupported workaround.

The workaround is very tedious and can be very painful to implement depending on the customer’s Image Capture setup and the number of scan stations they might have. The workaround consists of creating 13 configuration files for the Image Capture install and they have to be installed on each scan station as well as the Image Capture server.  If you have third party software installed you will also have to create configuration files for each of these as well

The other kicker to this workaround is that when a customer updates their .NET 2.0 framework, it breaks the connection with the License server and you have to restart the Image Capture Service on the server.  Sometimes this doesn’t even work and you have to do a registry hack on each of the scan stations and then you have to restart the service on the server.

As you can see from the examples above this is not a very efficient way to manage and operate your Image Capture system, and it’s about time to upgrade your system to something new that supports the latest .NET framework.  We would love to help you with your Imaging Capture System and customize it to fit your needs. You can contact us at for more information.

John Hart
Software Developer
ImageSource Inc.