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
- :
- Build Error ISDEV : error Val0006
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
‎Jan 12, 2012
04:12 PM
Build Error ISDEV : error Val0006
Here is the error we're getting when building a patch:
ISDEV : error Val0006: The Component '_3805868D3EBCD7CDCB07B265E1487FDE' identified by ComponentID '{3805868D-D3EB-CD7C-DCB0-7B265E1487FD}' is missing from the newest version of your setup. You can not delete components and still do a minor/small upgrade. You must perform a major upgrade.
Here is the background. We needed to build a new automated build server. We configured everything exactly the same as the old one to the best of our ability. Including copying over the old established uncompressed "BASELINE" so we can build patches. In the build process, when it tries to build the patch file we got the above error.
By using the MSI diff tool I was able to isolate the exact file that was causing the issue. It turns out the file was not part of our component definitions. It was being automatically installed because we had left a component setup to ".NET Scan for Properties and Dependencies".
The .ISM has not changed, that component is still set to pick up dependencies automatically and it is successfully picking up the file in question. The problem is the "File" and "Component" GUID's are changing, therefore the old BASELINE thinks that we have removed a component when it does the diff. So it errors out with the a fore mentioned error.
It is imperative that we're able to build a patch based off that old established BASELINE because we have users we need to be able to patch.
TRINITY!!... HELP!!
ISDEV : error Val0006: The Component '_3805868D3EBCD7CDCB07B265E1487FDE' identified by ComponentID '{3805868D-D3EB-CD7C-DCB0-7B265E1487FD}' is missing from the newest version of your setup. You can not delete components and still do a minor/small upgrade. You must perform a major upgrade.
Here is the background. We needed to build a new automated build server. We configured everything exactly the same as the old one to the best of our ability. Including copying over the old established uncompressed "BASELINE" so we can build patches. In the build process, when it tries to build the patch file we got the above error.
By using the MSI diff tool I was able to isolate the exact file that was causing the issue. It turns out the file was not part of our component definitions. It was being automatically installed because we had left a component setup to ".NET Scan for Properties and Dependencies".
The .ISM has not changed, that component is still set to pick up dependencies automatically and it is successfully picking up the file in question. The problem is the "File" and "Component" GUID's are changing, therefore the old BASELINE thinks that we have removed a component when it does the diff. So it errors out with the a fore mentioned error.
It is imperative that we're able to build a patch based off that old established BASELINE because we have users we need to be able to patch.
TRINITY!!... HELP!!
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 13, 2012
08:30 AM
Are you using patch optimization (where you specify the earlier patch in the Releases view, so that InstallShield can synchronize component names, component GUIDs, and other data)? The following help topic provides more details:
Upgrade Considerations
Upgrade Considerations
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 02, 2021
07:40 AM
Hello,
I'm running into the same issue. Was there a resolution to this?