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
- :
- error 6552 during build
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
Nov 24, 2009
11:23 AM
error 6552 during build
I have a basic MSI project that I recently made some modifications to using IS2010.
Now when I build it I get 8 files that are throwing an error 6552 "The file key could not be synchronized with the previous package because that file key is already in use."
The 8 files throwing the error have not changed since the last time I successfully built this project, but have changed since the previous package. Does anyone have an idea as to what is causing this or how to fix it?
Now when I build it I get 8 files that are throwing an error 6552 "The file key could not be synchronized with the previous package because that file key is already in use."
The 8 files throwing the error have not changed since the last time I successfully built this project, but have changed since the previous package. Does anyone have an idea as to what is causing this or how to fix it?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 24, 2009
12:43 PM
I figured out what caused the issue, and had to use the direct editor to fix it.
The files in question had been removed from the project and re-added due to a change in the application that was using them. When this was done they were given different file keys that were similiar to each other because the filenames begin the same. When it tried to synch up with the old keys it found other files in existance with the file key that matched the old entry in the previous release. Using the direct editor to set the file keys to match the same files in the previous release eliminated the error.
The files in question had been removed from the project and re-added due to a change in the application that was using them. When this was done they were given different file keys that were similiar to each other because the filenames begin the same. When it tried to synch up with the old keys it found other files in existance with the file key that matched the old entry in the previous release. Using the direct editor to set the file keys to match the same files in the previous release eliminated the error.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)