-- Error 1316 Out of nowhere.....

[MarcinK71]

Hi

I have installed latest version of my software (lets say 5.1.800) created by latest AI.21.9, then after that I have installed previous version (5.1.400) to check updater functionality. When I try to uninstall version 5.1.400 I am getting this error:

MSI (s) (50:34) [13:29:25:708]: File: C:\Users\Marcin\AppData\Roaming\SkalarkiIO Profiler 5.1\Settings.config; To be installed; Won't patch; No existing file
MSI (s) (50:34) [13:29:25:708]: Resolving source.
MSI (s) (50:34) [13:29:25:708]: Resolving source to launched-from source.
MSI (s) (50:34) [13:29:25:708]: Setting launched-from source as last-used.
MSI (s) (50:34) [13:29:25:708]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\WINDOWS\Installer\'.
MSI (s) (50:34) [13:29:25:708]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\WINDOWS\Installer\'.
MSI (s) (50:34) [13:29:25:708]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{1AAD815E-403A-488C-A360-5B06460C7FB0}'.
MSI (s) (50:34) [13:29:25:708]: SOURCEDIR ==> C:\WINDOWS\Installer\
MSI (s) (50:34) [13:29:25:708]: SOURCEDIR product ==> {1AAD815E-403A-488C-A360-5B06460C7FB0}
MSI (s) (50:34) [13:29:25:708]: Determining source type
MSI (s) (50:34) [13:29:25:708]: Note: 1: 2203 2: C:\WINDOWS\Installer\SkalarkiIOProfiler514001000.msi 3: -2147287038
MSI (s) (50:34) [13:29:25:708]: Note: 1: 1316 2: C:\WINDOWS\Installer\SkalarkiIOProfiler514001000.msi
MSI (s) (50:34) [13:29:25:708]: SECREPAIR: Error determining package source type
MSI (s) (50:34) [13:29:25:708]: SECREPAIR: Cleanup the Hash Value
MSI (s) (50:34) [13:29:25:708]: SECUREREPAIR: SecureRepair Failed. Error code: 524B59DB2C8
MSI (s) (50:34) [13:29:36:049]: Product: SkalarkiIO Profiler 5.1 -- Error 1316. The specified account already exists.


I need help, please to fix this issue...

[Liviu]

Hello,

This problem may appear if some registry entries get corrupted after many tests done on the same machine. That is why we recommend tests to be done on clean virtual machines that can be easily restored to their clean state.

Can you reproduce the problem on multiple clean machines? You can try to clean all the unnecessary information remained on your machine about the product that fails, by using the Microsoft Fixit Tool: https://support.microsoft.com/en-us/hel ... or-removed

Let us know if that helped.

Best regards,
Liviu