Microsoft .NET Framework 1.1 Service Pack 1 (KB867460) cannot be installed because you have one or more hot fixes installed. Remove them and try again

If you see this error, refer to http://support.microsoft.com/?kbid=899619 for further information and to correct the error.

4. The IO Libraries Suite installation process normally installs version 1.2.1.0 of the IVI Shared Components. If you have already installed an earlier version of the IVI Shared Components, the IO Libraries Suite installation will not overwrite your version of the IVI Shared Components, because you may have instrument drivers that depend on a specific version.
   
   However, Agilent VEE Pro and Agilent T&M Toolkit require IVI Shared Components version 1.2.1.0 or later, and require that the Microsoft .NET Framework be installed prior to the installation of the IVI Shared Components. If you are using either of these products with an older version of the IVI Shared Components, or with a version that was installed prior to the installation of the .NET Framework, you may see an "Error 758" message when you attempt certain VEE operations, "Could not load the configuration file" or "File or assembly name Ivi.ConfigServer.Interop was not found" when starting T&M Toolkit, or other errors.
   
   If you are in this situation, you should check the documentation for any IVI drivers you are using to determine the correct version of IVI Shared Components for your needs. Determine your installed version by navigating to the IVI Components Path (by default, C:\Program Files\IVI), then to the Bin directory. Right-click on IviSharedComponentVersion.dll and select Properties, then Version.

   You can upgrade your IVI Shared Components as follows:

   • Close Agilent Connection Expert, if it is running.

   • Close all Agilent VEE Pro, Agilent T&M Toolkit, and Visual Studio .NET windows.

   • Remove your current installation of IVI Shared Components as follows:

     • Go to Start > Control Panel > Add or Remove Programs, select IVI Shared Components and then Remove. Choose the Partial removal option to retain configuration information.

     • Some older versions of IVI Shared Components may not appear in the Add or Remove Programs dialog. In this case, go to http://www.ivifoundation.org, follow the links to Downloads, then to Shared Components. Download the IVI Cleanup Utility and run it.

   • Install a newer version of IVI Shared Components in either of the following ways:

     • Repair your IO Libraries Suite installation by clicking Start > Control Panel > Add or Remove Programs, select Agilent IO Libraries Suite and then Repair. This will install the version of IVI Shared Components that is shipped with Agilent IO Libraries Suite 14.1, or:

     • Go to the IVI Foundation Web site, http://www.ivifoundation.org. Follow the links to Downloads, then to Shared Components. Follow the instructions on this page to download the latest version of the components. This page always contains the latest available version.

5. If you connect (plug in) devices to your PC while the Connection Expert is starting up (i.e. while the auto-configuration and discovery process is occurring, and the small Connection Expert splash screen is displayed), Connection Expert may show incorrect states of some devices and interfaces in the explorer view. For example, devices may display Communication Failure states when they are actually operating correctly. Close Connection Expert and restart it to resolve this problem.

6. If you change the properties of the Remote IO Server software while it is running, or if you change the properties of a shared interface on the remote I/O server PC, the changes will not take effect until you stop and restart the Remote IO Server software.

7. If the SICL interface ID and/or logical unit of a shared GPIB, USB, or serial interface is changed on a remote I/O server (a PC running the Agilent Remote IO Server software), that interface cannot be accessed remotely until the Remote IO Server software is stopped and re-started on the server PC.

8. If you upgrade from Agilent IO Libraries G.02.02 to IO Libraries Suite 14.1, some LAN devices may be deleted from your I/O configuration even if you have selected the option to save your configuration. If this happens, you will need to use the Connection Expert utility to add these devices manually.

9. Do not attempt to install Agilent IO Libraries version H.01.02 or G.02.02 (or other versions beginning with "H" or "G") after you have installed Agilent IO Libraries Suite 14.1. The software will not warn you that you are installing an older version of the software over a newer version, and the resulting system configuration is unsupported.

10. In some cases, you may experience PC performance problems if you put your PC into Windows Standby mode while the IO Control process is running. If this occurs, you will see very slow PC operation and high CPU utilization after exiting Standby mode. To prevent this problem, exit the IO Control (click on the  IO Control icon in the taskbar notification area and click Exit) before going into Standby mode. After you leave Standby mode, restart the IO Control by clicking Start > Programs > Agilent IO Libraries Suite > Utilities > IO Control.

11. The following defect may be seen if you are using USBTMC instruments on a hyperthreaded or dual-CPU PC, and if multiple processes on the PC are receiving VISA events. If, after receiving the events, two processes attempt to disable events simultaneously (or almost simultaneously), memory corruption can occur. This will cause an exception in the affected process. To work around this problem, boot the PC in single-processor (non-hyperthreaded) mode, or synchronize the processes so that they disable events sequentially.