I have 2 class builder,1 windows application, and a deployment package builder project in a vs.net 2003 solution. I think, the dependencies are set correctly for the configuration.

Still about 2 months ago I could use the built-in deploymentpackage maker of the vs.net 2003 without any problem.

Nowadays it seems to be working randomly. Sometimesa Windows Installer window appears telling "Preparing to install ", and if I let it "completed", then after long-long minutes it tells me finally, that some vsinstallation package is not available, and the whole "installation" is withdrawn. In the meantime these2 events below appear in the events log:

Event Type:Warning
Event Source:MsiInstaller
Event Category:None
Event ID:1004
Date:1/26/2009
Time:9:03:32 AM
User:P3-866\Mesti
Computer:P3-866
Description:
Detection of product '{20610409-CA18-41A6-9E21-A93AE82EE7C5}', feature 'Visual_Studio.NET_Professional', component '{19D39DFE-675D-4FF8-80BD-092CF5894B84}' failed. The resource 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved\{42042206-2D85-11D3-8CFF-005004838597}' does not exist.

Event Type:Warning
Event Source:MsiInstaller
Event Category:None
Event ID:1001
Date:1/26/2009
Time:9:03:32 AM
User:P3-866\Mesti
Computer:P3-866
Description:
Detection of product '{20610409-CA18-41A6-9E21-A93AE82EE7C5}', feature 'Visual_Studio.NET_Professional' failed during request for component '{FD153241-37EC-11D2-8892-00A0C981B015}'

I havn't found any reasonable explanation for the events related with my case, and I couldn't really solve my deployment problem.
The really disturbing is, that about once in 5 deployments the build finishessuccessfully: in these casesthe window of theinstaller appears for a very short time, but it disappears, and everything seems to be on the good track. Sometimes I had a feeling, that there could be something around the dependencies, but doing the same helps once, and prooves erratic in the other time...


It is a bit frustrating, that after a hard work of programming an other hard work follows, but it is without control(at least at me, until now;-)
I would appreciate, if somebody would be able to tell me, what's going on.

SlowArrow

Thanks for your support too! (Until now I was not able to deal with the problem because of a little planned surgery...)

Reconstructing the deployment project didn't solve the problem, nor going through the procedures of the suggestedarticle.

Finally I reinstalled the VS.NET 2003 SP1, and this providedthe solution (however, during installation it asked the originalCD as well). It's a bit mistery for me, how the vs installation package could repair something which seems to be related with the Office (msohev.dll)? Perhaps, it was prepared for such kind of error, and just initiated an other repair (or module reregistration)?

Hi Slow Arrow,

Do you mean the event error logged during the installation process? These message seems it cannot find special information in Windows registry.

In your post, you have mentioned that reset the dependencies will help once. How did you reset dependencies? Did you delete all custom dependencies from your project and add them one by one? Or did you remove the primary output from your setup project and add them again?

Since it is a random problem, I think there may be the corrupt of your setup project. You can try to remove the setup project from your solution and then create a new one to see if the problem can be fixed.

Please inform me the process.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

Hi Kira,

I'm happy, that someone tries to help me...

No, this events occur during the building phase in the vs studio. IfI'm able to produce the installation files somehow (because if this erratic behaviour of the building process, it may take 1-2 frustrating hours), then the program seems to beinstalledcorrectly, as it used to be before, and there is no problem with thework of the program as well.

Yes, it seems to me, that some information in the registry, or the handling of some information which can be found in the registry went wrong somehow.

I haven't reset the dependencies yet, just tried to change the order of the dependencies in different rational ways. However, I'm not sure that it has something to do with my problem. Really I couldn'tfind anything that seemed toeffect the arratic behaviour of the environment in a consistent way. So, the most frustrating, that it happens randomly, and I can't reproduce it consistently.

However, your idea to reset the dependencies and also to recreate the setup project seems to be fruitful:-) I'll try it (but now there will be a couple ofdays gap in my activities).

Best regards,

Slow Arrow

Hi Slow Arrow,

Please inform me the test result after you do that, that will help other people who have met or will meet the similar situation to take it for reference. Thank you for your understanding.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

We are changing the issue type to “General Discussion�because you have not followed up with the necessary information. If you have more time to look at the issue and provide more information, please feel free to change the issue type back to “Question�by opening the Options list at the top of the post editor window, and changing the type. If the issue is resolved, we will appreciate it if you can share the solution so that the answer can be found and used by other community members having similar questions.

---

Please mark the replies as answers if they help and unmark if they don't.

This is a Windows Installer repair. It's normal for certain activities to cause Windows to check that a product is still installed correctly - it's the automatic version of right-click on an MSI file and doingrepair. When you do your build it's detecting that something in your installed VS 2003 is broken, like that registry key. The repair depends on a .msi file in Windows\installer, so if files in there got removed then the repair can't run.Or it may ask for you to put the original CD you installed it from. As to why that registry key might be missing, I've no idea.

That guid that starts withFD153241 refers to mergemod.dll. My guess is that you installed something that broke that registration, maybe another install tool. Although you haven't got the exact error referred to in this article there's some things you can try:
http://support.microsoft.com/kb/329214

---

Phil Wilson

Thanks for your support too! (Until now I was not able to deal with the problem because of a little planned surgery...)

Reconstructing the deployment project didn't solve the problem, nor going through the procedures of the suggestedarticle.

Finally I reinstalled the VS.NET 2003 SP1, and this providedthe solution (however, during installation it asked the originalCD as well). It's a bit mistery for me, how the vs installation package could repair something which seems to be related with the Office (msohev.dll)? Perhaps, it was prepared for such kind of error, and just initiated an other repair (or module reregistration)?