Error 5002

[josec]

I have some legacy products (written in VB6) that I have to update to make them usable/workable on Vista. So I bought and loaded the newest IR WInstaller up on Friday. Went MS site and downloaded the merge modules I needed. When I went to build the project, I am getting a lot of warnings and errors, I do not know if they are show stoppers, I hope someone would be able to shed some light on these errors.

I spend some time trying track down information from several places, but every time I tried something, things got worse. Attached is the log file. I can provide more information, but at this point, I am not certain what is important to include.

[snaghibi]

I am pretty much in the same boat as you are. VB6 app, merge modules, it is giving me 5001. The point is I have not yet managed to make ONE successful installation with SUFWI. Very frustrating!

[Brett]

We will look into these issues. From your build log it appears that most of the output are warnings - due to the merge modules not containing proper validation information. Let me look more deeply into this and I will get back to you in the next day or two.

[snaghibi]

Sorry Brett does this apply to my errors or are you addressing the originator of this thread?

[josec]

Thanks, Brett. If you need any more info or files, I'll be happy to provide them.

I went ahead and ran the resulting .msi file that it created and it installed the application. I did get one error during installation - it was the MFC42 merge file - it gave a message that it couldn't update the file because it was a protected file. I just clicked continue because I knew it would be ok, but my users may be uncomfortable with that. I am also a bit uncomfortable seeing all those warnings during the build process, even though they may be harmless.

I still have a few more questions, but I post them to a different/new thread, as they are separate issues.

Thanks.

[Brett]

Sorry Brett does this apply to my errors or are you addressing the originator of this thread?

Well both I guess. Just knowing that you are getting error 5001 without a build log does not tell me much. If you can supply more information that would be great.

Thanks, Brett. If you need any more info or files, I'll be happy to provide them.

I went ahead and ran the resulting .msi file that it created and it installed the application. I did get one error during installation - it was the MFC42 merge file - it gave a message that it couldn't update the file because it was a protected file. I just clicked continue because I knew it would be ok, but my users may be uncomfortable with that. I am also a bit uncomfortable seeing all those warnings during the build process, even though they may be harmless.

I still have a few more questions, but I post them to a different/new thread, as they are separate issues.

Thanks.

I have been looking into this issue this morning. As far as the "error LGHT0204" errors go, we are implementing a fix for that. The service release will be out by end of day Thursday. It stems from invalid (or old, I am not sure) _Validation table entries in the merge module. The fix in WiX is to include <EnsureTable> elements for those tables. This will make it include the tables in the msi before the merge so that the newer table validations are given precendence.

With regards to "warning LGHT1056 : The Directory table contains a row..." there is not much that we can do about that one. Unfortunately, those Visual Studio SP6 merge modules are old and do things in an outdated way. However, LGHT1056 can be safely ignored. If you want to suppress it, go to Build > Settings and on the Options tab in the Additonal linker options, add "-sw1056" (no quotes).

The "warning LGHT1076 : ICE09: Component: XYZ is a non-permanent system..." is just telling you that you should mark the component as permanent. See http://msdn2.microsoft.com/en-us/library/aa368933.aspx for details. Again, this one is your own judgement call. You can either mark the components that those files are in as permanent, or ignore the warning. It is only a warning, so again, it is up to you and is not fatal.

I am still looking into which merge module is causing "error LGHT0204 : ICE99:..." Perhaps we can fix the module and make it available.

This is all ongoing, I just wanted to let you know what we have uncovered so far. Thank you for supplying the build log as it really helps us to see what is going on and replicate the problem.

[josec]

Thanks, Brett every little bit helps.