KB2918614

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

KB2918614

Keith.Douglas
I was given this by one of our internal deployment people this morning. Any thoughts?



Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
[hidden email]
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


_____________________________________________
[deleted]
Sent: September-22-14 8:41 AM
To: Douglas, Keith - CoSD/DSCo
Subject: FW: Service Request # 01298424 - KB2918614



Good morning Keith,

Any luck with the problem you were having with KB2918614?

I've asked IT security to remove this for you but we are not allowed since this is a security update from Microsoft rated important.

He did find a few things to maybe fix this problem for you:

I've seen some workaround on the net, I don't know in Keith's case, if they could be easily applied or not...

Workaround if you have problems with repairing application:

    Uninstall the application and reinstall it with the security update installed. (sourcehash file generated with security update)

    Manually copy the sourcehash file to c:\windows\installer folder. As the sourcehash file is generated based on the application files, the sourcehash file generated on computer A can be used on computer B.


I've also read in a few different blog, from people contacting Microsoft about this issue and the answer they got form Microsoft is that they are hoping to have an additional patch that fixes this somewhere in the time range of mid October to beginning of November.  Now, I haven't seen anything official about this yet, but it would make sense.

Let me know if this helps...
Have a great day!



------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: KB2918614

roberthyang
Aha !  This would explain what we have been seeing: if the install is done after KB2918614, then the repair is successful.  If the install was done prior to KB2918614, then the repair for SQL Server CE 3.5 SP2 x64 fails.

The difference in the log is as follows :

MSI (s) (50:CC) [12:30:26:258]: Determining source type
MSI (s) (50:CC) [12:30:26:258]: Source type from package 'SSCERuntime-ENU-x64.msi': 2
MSI (s) (50:CC) [12:30:26:258]: SECREPAIR: Hash Database: C:\windows\Installer\SourceHash{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}

vs.

MSI (s) (0C:F8) [10:17:28:915]: Determining source type
MSI (s) (0C:F8) [10:17:28:915]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (0C:F8) [10:17:28:915]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi
MSI (s) (0C:F8) [10:17:28:915]: SECREPAIR: Error determining package source type
MSI (s) (0C:F8) [10:17:28:915]: SECUREREPAIR: SecureRepair Failed. Error code: 524F6DF34B8
MSI (s) (0C:F8) [10:18:52:364]: Product: Microsoft SQL Server Compact 3.5 SP2 x64 ENU -- Error 1316.The specified account already exists.

Thanks !
-Rob

Keith.Douglas wrote
I was given this by one of our internal deployment people this morning. Any thoughts?



Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
[hidden email]
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


_____________________________________________
[deleted]
Sent: September-22-14 8:41 AM
To: Douglas, Keith - CoSD/DSCo
Subject: FW: Service Request # 01298424 - KB2918614



Good morning Keith,

Any luck with the problem you were having with KB2918614?

I've asked IT security to remove this for you but we are not allowed since this is a security update from Microsoft rated important.

He did find a few things to maybe fix this problem for you:

I've seen some workaround on the net, I don't know in Keith's case, if they could be easily applied or not...

Workaround if you have problems with repairing application:

    Uninstall the application and reinstall it with the security update installed. (sourcehash file generated with security update)

    Manually copy the sourcehash file to c:\windows\installer folder. As the sourcehash file is generated based on the application files, the sourcehash file generated on computer A can be used on computer B.


I've also read in a few different blog, from people contacting Microsoft about this issue and the answer they got form Microsoft is that they are hoping to have an additional patch that fixes this somewhere in the time range of mid October to beginning of November.  Now, I haven't seen anything official about this yet, but it would make sense.

Let me know if this helps...
Have a great day!



------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: KB2918614

Phil Wilson
This seems to be the fix - I haven't noticed anyone post it here yet:

http://support.microsoft.com/kb/3000988
---------------
Phil Wilson


On Mon, Sep 29, 2014 at 11:19 AM, roberthyang <[hidden email]> wrote:

> Aha !  This would explain what we have been seeing: if the install is done
> after KB2918614, then the repair is successful.  If the install was done
> prior to KB2918614, then the repair for SQL Server CE 3.5 SP2 x64 fails.
>
> The difference in the log is as follows :
>
> MSI (s) (50:CC) [12:30:26:258]: Determining source type
> MSI (s) (50:CC) [12:30:26:258]: Source type from package
> 'SSCERuntime-ENU-x64.msi': 2
> MSI (s) (50:CC) [12:30:26:258]: SECREPAIR: Hash Database:
> C:\windows\Installer\SourceHash{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
>
> vs.
>
> MSI (s) (0C:F8) [10:17:28:915]: Determining source type
> MSI (s) (0C:F8) [10:17:28:915]: Note: 1: 2203 2: C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
> Edition\SSCERuntime_x64-enu.msi 3: -2147287038
> MSI (s) (0C:F8) [10:17:28:915]: Note: 1: 1316 2: C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
> Edition\SSCERuntime_x64-enu.msi
> MSI (s) (0C:F8) [10:17:28:915]: SECREPAIR: Error determining package source
> type
> MSI (s) (0C:F8) [10:17:28:915]: SECUREREPAIR: SecureRepair Failed. Error
> code: 524F6DF34B8
> MSI (s) (0C:F8) [10:18:52:364]: Product: Microsoft SQL Server Compact 3.5
> SP2 x64 ENU -- Error 1316.The specified account already exists.
>
> Thanks !
> -Rob
>
>
> Keith.Douglas wrote
>> I was given this by one of our internal deployment people this morning.
>> Any thoughts?
>>
>>
>>
>> Keith Douglas
>> Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
>> Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
>
>> Keith.Douglas@.gc
>
>> Telephone | Téléphone 613-854-5589
>> Facsimile | Télécopieur 613-951-4674
>> Government of Canada | Gouvernement du Canada
>>
>>
>> _____________________________________________
>> [deleted]
>> Sent: September-22-14 8:41 AM
>> To: Douglas, Keith - CoSD/DSCo
>> Subject: FW: Service Request # 01298424 - KB2918614
>>
>>
>>
>> Good morning Keith,
>>
>> Any luck with the problem you were having with KB2918614?
>>
>> I've asked IT security to remove this for you but we are not allowed since
>> this is a security update from Microsoft rated important.
>>
>> He did find a few things to maybe fix this problem for you:
>>
>> I've seen some workaround on the net, I don't know in Keith's case, if
>> they could be easily applied or not...
>>
>> Workaround if you have problems with repairing application:
>>
>>     Uninstall the application and reinstall it with the security update
>> installed. (sourcehash file generated with security update)
>>
>>     Manually copy the sourcehash file to c:\windows\installer folder. As
>> the sourcehash file is generated based on the application files, the
>> sourcehash file generated on computer A can be used on computer B.
>>
>>
>> I've also read in a few different blog, from people contacting Microsoft
>> about this issue and the answer they got form Microsoft is that they are
>> hoping to have an additional patch that fixes this somewhere in the time
>> range of mid October to beginning of November.  Now, I haven't seen
>> anything official about this yet, but it would make sense.
>>
>> Let me know if this helps...
>> Have a great day!
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> WiX-users mailing list
>
>> WiX-users@.sourceforge
>
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
> --
> View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/KB2918614-tp7596942p7597053.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: KB2918614

Keith.Douglas
I'm not sure this explains everything people reported, but it would explain why we never saw it ...

Thanks, Phil.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
[hidden email]
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada

-----Original Message-----
From: Phil Wilson [mailto:[hidden email]]
Sent: October-14-14 6:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] KB2918614

This seems to be the fix - I haven't noticed anyone post it here yet:

http://support.microsoft.com/kb/3000988
---------------
Phil Wilson


On Mon, Sep 29, 2014 at 11:19 AM, roberthyang <[hidden email]> wrote:

> Aha !  This would explain what we have been seeing: if the install is
> done after KB2918614, then the repair is successful.  If the install
> was done prior to KB2918614, then the repair for SQL Server CE 3.5 SP2 x64 fails.
>
> The difference in the log is as follows :
>
> MSI (s) (50:CC) [12:30:26:258]: Determining source type MSI (s)
> (50:CC) [12:30:26:258]: Source type from package
> 'SSCERuntime-ENU-x64.msi': 2
> MSI (s) (50:CC) [12:30:26:258]: SECREPAIR: Hash Database:
> C:\windows\Installer\SourceHash{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
>
> vs.
>
> MSI (s) (0C:F8) [10:17:28:915]: Determining source type MSI (s)
> (0C:F8) [10:17:28:915]: Note: 1: 2203 2: C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (0C:F8)
> [10:17:28:915]: Note: 1: 1316 2: C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (0C:F8)
> [10:17:28:915]: SECREPAIR: Error determining package source type MSI
> (s) (0C:F8) [10:17:28:915]: SECUREREPAIR: SecureRepair Failed. Error
> code: 524F6DF34B8
> MSI (s) (0C:F8) [10:18:52:364]: Product: Microsoft SQL Server Compact
> 3.5
> SP2 x64 ENU -- Error 1316.The specified account already exists.
>
> Thanks !
> -Rob
>
>
> Keith.Douglas wrote
>> I was given this by one of our internal deployment people this morning.
>> Any thoughts?
>>
>>
>>
>> Keith Douglas
>> Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
>> Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
>> 0T6
>
>> Keith.Douglas@.gc
>
>> Telephone | Téléphone 613-854-5589
>> Facsimile | Télécopieur 613-951-4674
>> Government of Canada | Gouvernement du Canada
>>
>>
>> _____________________________________________
>> [deleted]
>> Sent: September-22-14 8:41 AM
>> To: Douglas, Keith - CoSD/DSCo
>> Subject: FW: Service Request # 01298424 - KB2918614
>>
>>
>>
>> Good morning Keith,
>>
>> Any luck with the problem you were having with KB2918614?
>>
>> I've asked IT security to remove this for you but we are not allowed
>> since this is a security update from Microsoft rated important.
>>
>> He did find a few things to maybe fix this problem for you:
>>
>> I've seen some workaround on the net, I don't know in Keith's case,
>> if they could be easily applied or not...
>>
>> Workaround if you have problems with repairing application:
>>
>>     Uninstall the application and reinstall it with the security
>> update installed. (sourcehash file generated with security update)
>>
>>     Manually copy the sourcehash file to c:\windows\installer folder.
>> As the sourcehash file is generated based on the application files,
>> the sourcehash file generated on computer A can be used on computer B.
>>
>>
>> I've also read in a few different blog, from people contacting
>> Microsoft about this issue and the answer they got form Microsoft is
>> that they are hoping to have an additional patch that fixes this
>> somewhere in the time range of mid October to beginning of November.  
>> Now, I haven't seen anything official about this yet, but it would make sense.
>>
>> Let me know if this helps...
>> Have a great day!
>>
>>
>>
>> ---------------------------------------------------------------------
>> --------- Meet PCI DSS 3.0 Compliance Requirements with EventLog
>> Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI
>> DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download
>> White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
>> EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg
>> .clktrk _______________________________________________
>> WiX-users mailing list
>
>> WiX-users@.sourceforge
>
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/KB291861
> 4-tp7596942p7597053.html Sent from the wix-users mailing list archive
> at Nabble.com.
>
> ----------------------------------------------------------------------
> -------- Slashdot TV.  Videos for Nerds.  Stuff that Matters.
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.
> clktrk _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: KB2918614

Neil Sleightholm
In reply to this post by Phil Wilson
I had this confirmed as the fault fix by our Microsoft support contact and we tried a beta of it and it fixed the original problem I reported (see below).

Neil

-----Original Message-----
From: Phil Wilson [mailto:[hidden email]]
Sent: 14 October 2014 23:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] KB2918614

This seems to be the fix - I haven't noticed anyone post it here yet:

http://support.microsoft.com/kb/3000988
---------------
Phil Wilson



Has anyone seen the issue below?

We are deploying MSIs via a remote PowerShell script and last week it suddenly started failing with this error. We have tracked the problem down to Hotfix 2918614 (released 12 Aug 2014) but were curious if anyone else is experiencing the problem or know what is causing it.

MSI (s) (04:A0) [11:10:07:189]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{0853D2F3-3147-45BE-A153-23E5915150B3}
MSI (s) (04:A0) [11:10:07:189]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (04:A0) [11:10:07:221]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:A0) [11:10:07:314]: SECREPAIR: New Hash Database creation complete.
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: CryptAcquireContext: Could not create the default key container
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: Crypt Provider not initialized. Error:-2146892987
MSI (s) (04:A0) [11:10:07:938]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxxxxxxxx.msi: for computing its hash. Error: -2146892987
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (04:A0) [11:10:07:938]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:A0) [11:10:07:938]: SECUREREPAIR: SecureRepair Failed. Error code: 80090345F56034B8
Action start 11:10:07: ProcessComponents.
MSI (s) (04:A0) [11:10:07:938]:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

Neil

Neil Sleightholm
X2 Systems Limited
[hidden email]
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: KB2918614

js69
To give some contradictory feedback:

Installing KB3000988 did not fix the error 1316 issue on my machine.

From the log:

MSI (s) (5C:94) [10:14:49:895]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (5C:94) [10:14:49:895]: Determining source type
MSI (s) (5C:94) [10:14:49:896]: Note: 1: 2203 2: C:\Windows\Installer\ProgramFiles.msi 3: -2147287038
MSI (s) (5C:94) [10:14:49:896]: Note: 1: 1316 2: C:\Windows\Installer\ProgramFiles.msi
MSI (s) (5C:94) [10:14:49:896]: SECREPAIR: Error determining package source type
MSI (s) (5C:94) [10:14:49:896]: SECUREREPAIR: SecureRepair Failed. Error code: 524F7C234B8
MSI (s) (5C:94) [10:16:06:795]: Note: 1: 2205 2:  3: Error
MSI (s) (5C:94) [10:16:06:795]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (5C:94) [10:16:06:795]: Produkt: inLab SW 15.0.0.111111 (MSI) -- Fehler 1316. Das angegebene Konto ist bereits vorhanden.

I will try with uninstalled KB2918614 next.
Reply | Threaded
Open this post in threaded view
|

Re: KB2918614

ap84
In reply to this post by roberthyang
roberthyang wrote
The difference in the log is as follows :

MSI (s) (50:CC) [12:30:26:258]: Determining source type
MSI (s) (50:CC) [12:30:26:258]: Source type from package 'SSCERuntime-ENU-x64.msi': 2
MSI (s) (50:CC) [12:30:26:258]: SECREPAIR: Hash Database: C:\windows\Installer\SourceHash{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}

vs.

MSI (s) (0C:F8) [10:17:28:915]: Determining source type
MSI (s) (0C:F8) [10:17:28:915]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (0C:F8) [10:17:28:915]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi
MSI (s) (0C:F8) [10:17:28:915]: SECREPAIR: Error determining package source type
MSI (s) (0C:F8) [10:17:28:915]: SECUREREPAIR: SecureRepair Failed. Error code: 524F6DF34B8
MSI (s) (0C:F8) [10:18:52:364]: Product: Microsoft SQL Server Compact 3.5 SP2 x64 ENU -- Error 1316.The specified account already exists.
I get exactly the same difference in successful/unsuccessfull log (with different MSI name of course) when trying to apply minor upgrage with REINSTALL=ALL REINSTALLMODE=vomus.
But I ran it on Windows 8.1 and there is no KB2918614 in my updates list at all.

Minor uprade applies successfully only if MSI package of previous version is in the same folder.

If I'm trying to run my new MSI from another location, I get "The specified account already exists" error.