/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi, I was searching on the forums and I found severals post about this error, but I can't find the solution.
I have the same problem, I can compile my package.msi, but when I want to install it on some PC, it shows a msg box with the error.
I have used ICE validation and I have found highlighted in red all files that are inside of a merge module.
Obviously, if I have a merge module in my package, the files included in this merge module doesn't appear like a component.... I think!
So, where I have to looking for??
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
I still have the problem, but I have new information that could help... to you help me!
The problem is about a merge module called BDE_ENT (Borland Database Engine). I did the package without use this merge module, then I installed it and it works fine, later I put the merge module, it replaced all files that are included in the merge module. I tried to install the package again and the msg error (2705) was there...
Why this merge do that??? I have to use this merge, but how can I do to fix that problem?
Answered 06/11/2009 by: cmi2000
Senior Purple Belt

Please log in to comment
0
The directory that you get the 2705 error for has no valid Directory_Parent directory.
Perform an ICE validation and you should be pointed to the invalid entry you must correct.
Answered 06/11/2009 by: AngelD
Red Belt

Please log in to comment
0
Perform an ICE validation and you should be pointed to the invalid entry you must correct.That isn't exactly straight-forward to do if the table is in a merge module! :)

If you have Wise, you can convert the MSI to a WSI, during which process the MM will be extracted. You might be able to correct the error then.
Answered 06/12/2009 by: VBScab
Red Belt

Please log in to comment
0
My point was the validate the MSI (with the merged MSM) and not the MSM itself.
Answered 06/12/2009 by: AngelD
Red Belt

Please log in to comment