While installing or upgrading Kerio Outlook Connector Offline Edition (KOFF), the Windows wizard returns the following error, "Error 1722. There is a problem with this Windows Installer Package. Action FindKOFFServices, Location: C:\WINDOWS\Installer\MSIDDCD.tmp, command"
Users may report being unable to send/receive email messages using Outlook and KOFF before the upgrade attempt seeing a "Not Implemented" error.
KOFF installation and upgrade wizard uses the MAPI property library, which is included in Microsoft Office. This behavior was first identified as a known issue with the Office Outlook MAPI Initialize exception within Office 2016/2019 2003 (Build 12624.20466) and 2004 (Build 12730.20206). The same problem reappeared within the Volume License versions of Outlook starting in version 1808 Build 10368.20035.
Microsoft fixed this problem in Non-Volume License version 2004 build 12730.20236. At this time there is no confirmed fix for the Volume License versions of Outlook 2019, however, some users have reported that the issue appears to be fixed within the latest Outlook 2016 VL release. You can reference the steps below to attempt to remediate this Outlook issue.
Non-Volume Licensing Users
- Open Outlook application.
- Navigate to File > Office account > Update Options > Update Now. For more information, please refer to Install Office updates.
As new releases will resolve this behavior, the first step will be to check for available updates to your affected version of Microsoft Outlook, as shown above. If the behavior persists, however, you can attempt the following workarounds that have been reported to help some users:
- Downgrade to an Older version of Outlook.
- Attempt Rebuilding the Send/Receive Settings File:
- Close Outlook.
- Navigate to
- Back up any
.srsfiles in this folder by renaming them.
.oldto the end of the file will suffice for renaming.
- Open Outlook for these to be rebuilt.
After making the changes above, the installation/upgrade wizard completes successfully.
If none of the above workarounds help resolve the issue, then, you can open a Support ticket with us with the below information:
- Enable advanced logging on a client machine where the error is seen.
- Reproduce the
- Disable advanced logging.
- Attach the
debug.logfile with the Support ticket.
- Open Event Viewer on the same machine.
- Right-click on Windows Logs > Application, select Save All Events As..., and save the file.
- Zip this file and attach this as well with the Support ticket.