PDA

View Full Version : Windows XP + windows installer proxy


JLW
07-18-2003, 11:41 AM
I have an annoying problem with Windows XP. I have installed software that I have written onto Windows XP. The software works fine until I install any other software. With other software installed whenever i try and run my software I get an windows installer dialog box asking to install part of the software that I installed after my software.

I get two messages in the event viewer

Detection of product {EDCD4CE3-DE92-49A9-87F9-FE09B2F73A16C} feature MSredist failed during request for component {997FA962-E067-11D1-9396-00A0C90F27F93}

I have checked the registry and the component doesnt appear to exist

and the second event message
Windows installer proxy information not correctly registered

My software runs without any problems if I cancel the windows installer message approx 5 times.
The software runs without any problems on windows 2000

Any help with the above problem will be gratefully received

Jason

Paul Komski
07-19-2003, 05:45 AM
Could be a long shot, but think I have seen similar problem with XP somewhere that was sorted by installing SP1.

If you don't have SP1, consider creating a restore point or an image file before proceeding. Of course a clean install with SP1 from starters might be another option. You could always try this out with a dual boot XP/XP-SP1 as yet another method.

slim
07-19-2003, 08:31 AM
Is this windows XP home by any chance?

As I also have experienced problems with certain applications with mine on windows XP, but they always seem to work ok on windows 2000.

As paul mentioned, making sure you have got the latest service packs installed might help as well (but sometimes it can makes things worse).

Slim

JLW
07-21-2003, 05:41 AM
Thanks for your response.
Unfortunately I have already tried installing SP1. I have also re-installed XP from scratch and then installed SP1 but the problem still exists.
I think I might have found the problem in the microsoft technet site. Article Q330165 looks like it could be what is causing the problem on XP machines but you have to contact microsoft directly (which i suspect means a support contract) to get the fix