Page 1 of 1

Setup will not install.... Update_Configured?

Posted: Mon Nov 19, 2007 9:55 pm
by defiant11
I have a customers installing an update to my product and it's failing.

She installed the software via a CD uncompressed format. That worked fine.

I sent her a web update of the software via cd and the first time she tries to install she get a popup asking for a MSI. She cancels and retries only you get :

Line 13: Attempting to get value of undefined variable Update_Configured

Now the GUID of the CD to the Web update setup are different, so it should just install over the top of the existing install.

We got her to uninstall the original CD setup and tried to install the web update, only to get the same errors.

So we tried to reinstall the CD version, Now that will not install and has the same errors.

I've cleaned up all the ApplicationData directories and other files. Even cleaned up the registry.. still we can't reinstall the original CD version

Why is this so?

Posted: Wed Nov 21, 2007 2:39 am
by defiant11
tick tock

Same Issue

Posted: Thu Dec 13, 2007 1:37 pm
by mikehejt
I am having exactly the same issue.

Where is support on this one...?!?!?

Posted: Sat Dec 15, 2007 1:28 pm
by Alex_Ronquillo
When I first got hired by IA, I had a similar problem. I never found a way to replicate it, however, what I did was clean the registry deleting all references to the package that was causing the problem. That solved it, and let me install the package again.

Same issue

Posted: Tue Jul 08, 2008 10:27 am
by skjpatel
How did you clean the registry - I mean what id/name did look for. My clients have installed several different modules of our software (all package using IA7 ) but only one of these is reporting the UPDATE_CONFIGURED issue - therefore I want them to only clear down any entries for this specific app. Do they search on the product name or product code?

Thanks.

Posted: Tue Jul 08, 2008 10:34 am
by Alex_Ronquillo
Tell them to try with Windows Installer Clean Up Utility http://support.microsoft.com/kb/290301. Once done that, if the problem persists, look in registry for product name and product code and delete all entries. That should solve it.