This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Obect Already Exists Error all of a sudden
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 20, 2014
02:27 PM
Obect Already Exists Error all of a sudden
Basic MSI project. Client has Windows 7 Home.
Getting Object already Exists error. Any ideas what happened?
Lance
MSI (s) (74:20) [14:53:05:558]: Determining source type
MSI (s) (74:20) [14:53:05:558]: Source type from package 'BLS2015INSTALL.msi': 0
MSI (s) (74:20) [14:53:05:559]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{E8B12E79-DB5F-4DDB-A27F-9B38C5667528}
MSI (s) (74:20) [14:53:05:559]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (74:20) [14:53:06:029]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (74:20) [14:53:06:180]: SECREPAIR: New Hash Database creation complete.
MSI (s) (74:20) [14:53:06:193]: SECREPAIR: CryptAcquireContext: Could not create the default key container
MSI (s) (74:20) [14:53:06:193]: SECREPAIR: Crypt Provider not initialized. Error:-2146893809
MSI (s) (74:20) [14:53:06:193]: SECUREREPAIR: Failed to CreateContentHash of the file: BLS2015INSTALL.msi: for computing its hash. Error: -2146893809
MSI (s) (74:20) [14:53:06:193]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (74:20) [14:53:06:193]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (74:20) [14:53:06:193]: SECUREREPAIR: SecureRepair Failed. Error code: 8009000fF85434B8
Object already exists.
MSI (s) (74:20) [14:53:09:076]:
Action ended 14:53:09: ResolveSource. Return value 3.
Action ended 14:53:09: INSTALL. Return value 3.
Getting Object already Exists error. Any ideas what happened?
Lance
MSI (s) (74:20) [14:53:05:558]: Determining source type
MSI (s) (74:20) [14:53:05:558]: Source type from package 'BLS2015INSTALL.msi': 0
MSI (s) (74:20) [14:53:05:559]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{E8B12E79-DB5F-4DDB-A27F-9B38C5667528}
MSI (s) (74:20) [14:53:05:559]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (74:20) [14:53:06:029]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (74:20) [14:53:06:180]: SECREPAIR: New Hash Database creation complete.
MSI (s) (74:20) [14:53:06:193]: SECREPAIR: CryptAcquireContext: Could not create the default key container
MSI (s) (74:20) [14:53:06:193]: SECREPAIR: Crypt Provider not initialized. Error:-2146893809
MSI (s) (74:20) [14:53:06:193]: SECUREREPAIR: Failed to CreateContentHash of the file: BLS2015INSTALL.msi: for computing its hash. Error: -2146893809
MSI (s) (74:20) [14:53:06:193]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (74:20) [14:53:06:193]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (74:20) [14:53:06:193]: SECUREREPAIR: SecureRepair Failed. Error code: 8009000fF85434B8
Object already exists.
MSI (s) (74:20) [14:53:09:076]:
Action ended 14:53:09: ResolveSource. Return value 3.
Action ended 14:53:09: INSTALL. Return value 3.
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 20, 2014
02:35 PM
It appears related to kb2918614.
I uninstalled the KB, rebooted their machine, and tried the installer and it worked.
I uninstalled the KB, rebooted their machine, and tried the installer and it worked.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2014
10:57 AM
Looks like it is related to our issue, not the same error but the same cause ( kb2918614):
https://community.flexerasoftware.com/showthread.php?217786-Did-Microsoft-break-per-user-minor-upgrades-with-their-recent-kb2918614-Fix
https://community.flexerasoftware.com/showthread.php?217786-Did-Microsoft-break-per-user-minor-upgrades-with-their-recent-kb2918614-Fix
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2014
03:04 PM
We are now seeing this error on a few systems too. Microsoft Visual C++ Runtime Redistributable 2010 SP1 fails as well as another 3rd party installer.
Both are due to 'Object Already Exists'.
What in the heck did Microsoft do in that update?
Just as Lance stated, removing the KB2918614 and rebooting fixes the problem.
Both are due to 'Object Already Exists'.
What in the heck did Microsoft do in that update?
Just as Lance stated, removing the KB2918614 and rebooting fixes the problem.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 07, 2014
02:19 AM
DLee65 wrote:
We are now seeing this error on a few systems too. Microsoft Visual C++ Runtime Redistributable 2010 SP1 fails as well as another 3rd party installer.
Both are due to 'Object Already Exists'.
What in the heck did Microsoft do in that update?
Just as Lance stated, removing the KB2918614 and rebooting fixes the problem.
What is the KB2918614 and how does one go about removing it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 08, 2014
09:39 AM
KB items are patches that Microsoft has released through their update system.
To remove one you simply go to Programs and Features and click on the link to the left to 'view installed updates'. Type in the KB2918614 item in the search box at the top and it should appear and allow you to uninstall. I do not know if any group policy settings will limit this ability, but it stands to reason that it might.
To remove one you simply go to Programs and Features and click on the link to the left to 'view installed updates'. Type in the KB2918614 item in the search box at the top and it should appear and allow you to uninstall. I do not know if any group policy settings will limit this ability, but it stands to reason that it might.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2014
01:15 PM
I was able to uninstall this update and it solved my problem, but with automatic updates turned on (which I don't want to have to turn off) windows keeps reinstalling it whenever I reboot, what can I do to isolate this update so I don't have to keep uninstalling it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2014
01:31 PM
Do a check for updates. Isolate the offending one. You should be able to select it and choose to hide this update.