Our company is running IC 3.0 SU15, and we are unable to fax on Windows 7 64bit. I understand that you must install the driver for it, however the driver won't install. We try running InteractionFax64bit_SU15.msp, but we get the error: The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. Again, the client on the machines is IC 3.0 SU15, installed with all the defaults. We used an administrator account and we have no group policies about unsigned drivers. Any help would be appreciated! Thanks, -Scarter

We updated to SU17 last night and Interaction Fax is now generating the following error during the transmission process: ININ.IceLib.NotCachedException: The requested object or attribute is not being watched. Name: The object is not being watched. at ININ.IceLib.Directories.DirectoryConfiguration.GetList() in d:\eic_rum_su17\products\eic\src\icelib\Directories\DirectoryConfiguration.cs:line 138 The fax is ultimately sent, but the user never gets a confirmation email. Is there an update to the print drivers for SU17? This error was encountered on both Vista 32-bit and Windows 7 64-bit.

Originally posted by scarter;27403
Our company is running IC 3.0 SU15, and we are unable to fax on Windows 7 64bit. I understand that you must install the driver for it, however the driver won't install. We try running InteractionFax64bit_SU15.msp, but we get the error: The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. Again, the client on the machines is IC 3.0 SU15, installed with all the defaults. We used an administrator account and we have no group policies about unsigned drivers. Any help would be appreciated! Thanks, -Scarter

Has anyone found a fix for this yet? We are having the exact same issue.