The wizard was interrupted before [APPNAME] could be completely installed.

[boson_charles]

I have two packages that were setup as InstallScript/MSI projects. Both compiled fine. Both installed fine in the initial tests. I'm at the point where we have testers running the installation. The problem I have is occuring on 2 different machines. One is Windows 2000 SP4 and the other has Windows XP SP2. The user account being used does not have administrative rights. So far, other than the difference in operating systems, that is the only major difference.

On both machines the packages are failing to complete their installations. The message at the end is "The wizard was interrupted before [APPNAME] could be completely installed." and it does not leave an error notice of any kind. After having the testers run the installation with the "/verbose" command, I'm still at a stand still as the 3 and 5 mb files that were returned to me are not showing me any error numbers, at least that I've been able to see.

A description of the packages. The biggest difference is that one package, which was built with InstallShield X, has less redistributables and does not include MS JET or MDAC. The package built in InstallShield 9 has MS Jet and MDAC. The one that failed to install on the Windows 2000 machine was the one built in InstallShield 9.

Is this generally what happens when you don't have sufficient rights? No error notice? That's the only commond ground that both machines have that I can determine so far. One of the packages did return a "MSI (s) (70:60) [08:13:25:787]: Note: 1: 1708" near the end of the log file. The other package did not.

[Nate Bloyd]

Have you set ALLUSERS? (http://support.installshield.com/kb/view.asp?pcode=ALL&articleid=Q105063)

[boson_charles]

Yes AllUsers is set. Another thing that came to light after my initial post is the the Windows 2000 SP4 machine user has administrative rights to that machine. The products have both successfully been installed on 100's of machines. But in one day I got 2 different people with two different configurations using 2 different installers getting the same problem. The packages are almost identical except the one compiled in InstallShield X has had the MDAC removed from its infrastructure.

Very confusing...

[Nate Bloyd]

I realize it's going to be a bit of a pain, but can you compare logs on a successful install vs. the unsuccessful ones?

[boson_charles]

I was actually considering it... maybe I can whip up a little program to look for differences :D

I mean hey, after all, we are developers!

Thanks for your assistance. If I discover anything further, I'll post it.

[Nate Bloyd]

First of all, don't use Source Safe's Difference utility, every line of a log file is different because of the line header. I was thinking through the different circumstances I have come across related to the message you receive, and one thing I forgot to mention earlier for you to check is for any "Return value 3" entries in the log. Also, if you are not already using it, try WiLogUtl (http://www.microsoft.com/msdownload/platformsdk/sdkupdate/) for looking through the log files for issues.

[chilling]

Hi have you made any progress with this one? I am having the problem too :mad:

[boson_charles]

Hi have you made any progress with this one? I am having the problem too :mad:

Unfortunately no. I can't simulate the situation on our end, makes it very difficult to debug. Log files from installations aren't helping either, it just seems to stop and quit. :confused:

[chilling]

I'm pulling my hair out with this one (what little I have left) :eek: so any thoughts or ideas of what might be causing the problem from anyone would be great :)

[Nate Bloyd]

If you are (or if you are not)at all familiar with IS support, the first thing they would tell you to do is to start removing any Custom Actions, rebuild, and then test again. Another option for you to set is in the affected Custom Action change the "Return Processing" to "Synchronous (Ignores Exit Code)". This has worked for us in some circumstances.

[boson_charles]

The problem is that this particular item ocurred after a major release, months after. It was never an issue with any of our initial tests, and beta clients. It has only occured recently. Only thing I can gather is there is something with Win2000Sp4, and WinXPSp2, that is causing this, but I have yet to pin point it.

[chilling]

We have four custom actions all of which have been in the package without any alterations for a long time. Three of them have completed way before the problem occurs and the last is just a backup clearup .dll which unregisters and deletes any files left behind .. and we are Ignoring the Exit Code ...

but I will create a build without the custom actions and try it :)

[Nate Bloyd]

Believe me, I know how difficult it can be diagnosing offsite issues that only occur on "certain" machines. A couple of other things we have learned along the way:
Verify (this is if it is a requirement for your installs) the customer is logged in as the Administrator, and not just a user with Admin rights
Verify that any virus scanners or other scanning software is disabled - completely
Verify that you are controlling Services properly (IISAdmin, etc.) - if needed

[chilling]

This is not even offsite ... this is on the same pc that is creating the package :(

[Nate Bloyd]

The offsite comment was more for boson_charles. In your situation, is there other machines you can test on? I reformatted I don't know how many times before I confinced those with purchasing power to allow me to get Virtual PC, and that has saved me a ton of time, as well as made testing a more streamlined process. Just a bit of advise that I think you would receive from just about anyone - don't test on your development machines.

[chilling]

Don't normally ... I used to test in Virtual Machines until last week when someone else thought they liked my laptop more than I did :( .... it was stolen in the hotel I was staying at last week.

Temp laptop only has 20Gb hard disk orignial had 80Gb and even that was full ... VirtualPC's take up a lot of room - I had 30Gb's of different configurations :)

Anyway I have got to the bottom of my problem - actually it was problems.

I uninstalled Windows XP SP2 and then InstallShield started giving me better error codes ... via the verbose logging (ie C:\Setup.exe /d /v"/l*v C:\Setup.log") I tracked it down to a missing icon and corrupt .vbs file (all due to losing my laptop and not having backed up for a week :o )

[boson_charles]

We have an MSDN membership, I have Virtual PC installed with quite a few different flavors of Windows on it. I have WinXP, WinXP sp1, sp2, sp2 with adobe6 installed... Win2003.

The problem I think is when you incorporate other third party tools and installations. It's really hard, as you would already know, to recreate every situation. :cool:

Still working hard though, and yeah, Virtual PC is a great tool and I highly recommend it to everyone in development. That and/or VMWare are good tools. :D

[IQpierce]

Has there been a definite resolution to this issue? An installer for my application is also experiencing this, on a very few systems.

All indications that I've read here suggest that the issue was introduced with Windows XP Service Pack 2; has there been any confirmation on this?

Is there any way to force the installer to produce more informative error messages so that we can even tell InstallShield what's going on?

[boson_charles]

I can only say that on the few times it has come up, 4/5 of the clients had Windows XP Service Pack 2. That 1 person was using Windows 2000 Service Pack 4.

You can get the installation file to print out a log file, however it hasn't really been much help. I have not personally sent anything to InstallShield.

[Joel_KC]

This is most definantly a Windows XP service pack 2 issues. Has anyone found a solution or a cause to this. I have 8 installs that have not changed in 8 months. Within the last couple of weeks we have been getting calls from people having this issue. These installs had been being used without fail for the entire time period. It is not 100% accross the board as we know many people with service pack 2 that don't have this issue, but enough to be a problem. Is there a solution or at least an explanation?

[russellperry]

I just want to add my voice to the throng. Our tech support lit up in the last two weeks with this issue -- all Windows XP SP2. The verbose log was no help, it just says that ISScript was not found on the machine -- which is bizzare to me, because it wouldn't even get through the first window if the scripting engine wasn't installed. Help. Please.

[Nate Bloyd]

This is probably just useless banter for you all, but a few things that you may want to check:
- Do you have adequate error handling in scripts? I have said it before and I'll say it again, if you have vbscripts the best you can do is "On Error Resume Next", so consider migrating to InstallScript where you can have "Try...Catch" blocks.
- Verify that users are logged in as Admin. Period. No quasy-admin accounts.

I have tested dozens of installs of all sizes types and forms on XP SP2, and can tell you that if I verify these things, the installs work.

[IQpierce]

I've been in contact with an employee of Microsoft and they've just found a user fix for this issue.

We believe that the issue occurs when some product's previous installation is corrupt. Certain other installations then begin to experience this interrupt.

Here's the paraphrase of Microsoft's solution which I'm planning to provide to our users. It involves going through the Application Log to determine a number of installation GUID's from suspect installs.

-------------------------------------------------------------------------
1. Go to Control Panel->Administrative Tools->Event Viewer

2. In the left pane, choose "Application". In the right pane is a long list of Events. Sort by the "Event" tab (I think it's the third from the right). Then scroll down and find the ones with the value "11707" under that Event tab. Double-click to open the first one.

3. There's a text box at the bottom of this event, it contains data that might look like this:
0000: 7b 39 44 38 38 41 35 32 {9D88A52
0008: 45 2d 44 41 45 42 2d 34 E-DAEB-4
0010: 34 33 38 2d 41 30 35 43 438-A05C
0018: 2d 38 34 46 39 30 46 31 -84F90F1
0020: 43 39 45 32 46 7d C9E2F}

You see that there's a few columns here. We're only interested in the data in the right column (I marked it in red), which makes up a long string. In this example, the string we want is:
{9D88A52E-DAEB-4438-A05C-84F90F1C9E2F}
(It won't actually be that string, but it will look kinda like it... letters, numbers, hyphens, and brackets on each end.) You want to get this string (copy and paste) and put it in some text file where we can keep track of it. Because...

4. You need to repeat step 3 for all of the "Events" you found with the value "11707". (Actually if there are a lot of these, just worry about the ones within the last three months or so.) Again, keep track of all of those codes as you figure them out. You now have a list of codes.

5. Go to Start->Run, type "cmd" (no quotes), and hit enter.

6. Type in "cd windows\system32\" (no quotes) and hit enter.

7. Now, for each and every one of those codes we got, type this and hit enter:
msiexec.exe /x CODE
...Except that where I put CODE, you will put... the actual code. :) So for the example I gave, I would type:
msiexec.exe /x {9D88A52E-DAEB-4438-A05C-84F90F1C9E2F}
Again, you need to do this for every one of those codes. The effect of running one of these lines will be to start uninstallation of a product you had installed. One of these was your product which had a corrupt installation.

You may want to retry installing our demo after each one of these uninstallations.
-------------------------------------------------------------------------

Don't know of any way to avoid this on the developer end, but there's the fix on the user's end.

Microsoft confirmed that this fixed the problem for one user experiencing this problem with our product. I've sent it to another of our users with this problem to confirm it, and will post here to confirm whether or not it works.

[Nate Bloyd]

I narrowed one of our scenarios down to it being an InstallScript engine permissions issue. After following this advice from jippel (http://community.installshield.com/showthread.php?t=117720&page=2&pp=5&highlight=isscript), our installs were successful.
Hope this helps someone else.

[wbrins]

Hi. I'm NOT a developer, NOT a programmer. Just an end user who has spent 3 days now trying to get Quicken 2005 to install on my desktop. In my various interactions with Dell, Intuit, Microsoft, and now InstallShield I have discovered this community. Perhaps you can help a novice end user like me.
Problem: WinXP Home edition with SP2, on a Dell desktop - Quicken 2005 gets to 100% on the installation progress bar, says "Publishing Product Information", and then I get the "Installation was interrupted. Quicken 2005 was not installed" message. Now, it worked without a hitch, perfectly, no problem, on a Dell laptop also running WinXP SP2. Both appear to be configured nearly the same. I have administrator priviledges on both.

I don't get any error messages except if I try to install in Safe mode, and I get the 1607 error. I've been directed to all sorts of fixes for that error, and nothing works - I still get the error in Safe mode, and the interruption in normal mode.

I've been directed to edit the registry, start in selective start up mode, update the Installshield engine, start installation from the local drive, check permissions, and all sorts of things that are unnatural acts for me. All I want is for the damn software to load and install on my desktop.

Obviously there is something different between the desktop and the laptop, but no one has yet told me what to look for or how to find out. And apparently there is no simple, easy solution to this, like "face north and chant".

Repeat - I am not a developer, programmer, or anything else. I stumbled upon this community board as a result of all sorts of various attempts by folks to help me. Maybe you can help. What can a home user of Quicken do to get Quicken 2005 to install? I see other posts here about changing ISSCRIPT.msi registry values, and doing all sorts of other things that look very complicated and fraught with danger for someone like me.

Oh, one more bit of information. I installed Quicken 2004 earlier this year on this desktop, without incident. Later this year, I updated to Windows SP2. Now I have the Quicken 2005 issue, and also CANNOT install Quicken 2004. My simple conclusion is that SP2 is causing a problem somewhere. Microsoft's techs haven't pointed out the problem yet. Intuit has thrown up their hands. Dell has dropped out of the running.

(I have not tried IQPierce's solution posted 11/5/04.)

Many thanks.

[bigosmj]

Unfortunately, I am simply another end-user reporting the same behavior. I wanted to provide as much information as I could about my situation, because I think it might be helpful. (I am a .Net software engineer, so feel free to treat me as a user with a high technical background.)

I came across the problem when reformating and reinstalling my XP SP2 system. Specifically, this time I reinstalled Windows using my new "Windows XP Pro with SP2" CD. I only had reinstalled a few titles before the "the wizard was interrupted" InstallShield error message occurred, also with a Quicken product, as other users have reported - Quicken 2004. The exact list of Windows Installer titles from the Event Log were these:

{54DE0B75-6CD9-44C4-B10A-1F25DA9899D8} Quicken 2004
{790EC520-CCCC-4810-A0FE-061633204CE4} ISScript
{121634B0-2F4A-11D3-ADA3-00C04F52DD53} ByteFX MySQL .Net Client
{35D027A4-57BA-4E59-94DB-DFB36FFFDC1E} Remote Desktop
{FCE65C4E-B0E8-4FBD-AD16-EDCBE6CD591F} XP CD Writing Wizard (from Windows Update)
{5757AE1A-1DB4-4898-9806-09F77FBD5E57} MSDN
{20610409-CA18-41A6-9E21-A93AE82EE7C5} VS.NET 2003
{1A655D51-1423-48A3-B748-8F5A0BE294C8} J# Redistributable runtime
{CB2F7EDD-9D1F-43C1-90FC-4F52EAE172A1} .Net 1.1 (runtime?)
{D4D24FE5-FAB3-4FE2-AFFC-623955F4DF3A} VS.Net baseline
{17B66E83-1BC9-11D5-A54A-0090278A1BB8} Frontpage client
{FAAA508A-05C0-488B-BFC2-F9217E545A81} Logitech gaming
{CF6E7481-4487-46D3-810A-F73EEA232CE0} Intellipoint
{81463B08-A929-4125-A5F4-1B053AC35A09} Intellitype Pro
{91110409-6000-11D3-8CFE-0150048383C9} Office 2003
{350C97B0-3D7C-4EE8-BAA9-00BCB3D54227} Web Folders XP


After some web searching, I tried a few workarounds: I tried explicitly defining Default Access permissions in DCOM. As I recall, I tried added the local Administrators group, Interactive and System, in independent attempts, with reboots inbetween.

I tried using the Orca editor from the SDK to modify the isscript.msi from the Quicken CD (copied to HD) to add table values from the attached (obtained from this board, I think.)

In the end, I copied Quicken 2004 from another non SP2 computer to mine, used SysInternals File Monitor (www.sysinternals.com) to find DLLs from the install that were missing, and extracted them from the data1.cab file into the system32 folder. Definitely not a clean install - I'll be awaiting the times when I invoke an action with another missing DLL, crash Quicken and lose a night's worth of entering bills. I'll plan to provide these details to Quicken support too, although we'll just have to see who (Quicken, Microsoft, InstallShield) is able to provide the best end-user solution long-term.

Feel free to post here if anyone wants me to try a solution - I'll subscribe to the thread.

Michael Bigos

[wbrins]

I just had success installing Quicken 2005! I had to uninstall Service Pack 2, install Quicken, and then reinstall SP2. Here is information I received from Microsoft tech support, including their instructions. I tried all that is included here, but the only thing that worked was the uninstall/reinstall approach. I've provided this feedback to Microsoft, as well as posting in their Expert Zone community board (where others have also indicated having this issue).

From Microsoft:

"based on the detailed information you have provided, I have searched trough our internal database and found there is a compatible issue between Quicken 2005 and SP2. From our customers' feedbacks, they cannot install Quicken 2005 on systems with SP2 installed. The message they have encountered
is just the same.

I have then tested this issue on my side and found if we have SP2 installed on our computer, Quicken 2002 and later versions are able to get installed, but Quicken 2005 won't.

At this point, since installing Quicken only depends on Windows Installer, I suggest we double-check the status of Windows Installer on your system.

Step 1: Enable Windows Installer service
============
1. Click Start, click Run and type "services.msc" (without the quotation mark) and click OK.
2. Scroll down to the Windows Installer service on the right panel and double click it.
3. Check if the above service is enabled on the General Tab. (If it has already been enabled, please disable and re-enable it.)


Step 2: Check the Windows Installer service in Registry
============
1. Click Start, and then click Run.
2. In the Open box, type "regedit" (without the quotation marks), and then click OK.
3. Locate and click the following registry key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer]

4. In the right pane of the Registry Editor window, double-click ImagePath.

5. In the Edit String dialog box that appears, make sure that the string in the "Value data" box contains the correct path to the Msiexec.exe file. The following is the correct path, where <C> is the drive in which Windows XP is installed:

<C>:\Windows\System32\msiexec.exe /V

If not, please reset it.

6. Click Exit on the File menu to quit Registry Editor.


Step 3: Please temporarily remove any antivirus software such as Norton Antivirus or McAfee since they can cause similar issues as we have encountered.

After performing these steps, if Quicken 2005 still cannot be installed, I suggest we remove SP2 from your computer and then install Quicken on your computer to test this issue again. After installing Quicken, let's upgrade your computer to SP2 again.

To remove SP2, we can refer to the following steps:

Use the Add or Remove Programs tool in Control Panel
==========
1. Click Start, click Run, type appwiz.cpl in the Open box, and then click OK.
2. Click to select the Show Updates check box.
3. Click Windows XP Service Pack 2, and then click Remove.
4. Follow the instructions on the screen to remove Windows XP SP2.

For more information, please refer to the following Knowledge Base Article:

How to remove Windows XP Service Pack 2 from your computer
http://support.microsoft.com/default.aspx?scid=kb;[LN];875350"



(Note, I couldn't get Quicken 2004 to install either with SP2 installed. Also, I did install Quicken 2005 on my laptop, which has SP2, without any problem. So, there is apparently a certain configuration of SP2 that causes the problem.)

Good luck!

[psgamer0921]

Sorry to bump the thread, but I was wondering, has anyone found the fix that was posted on page 5 to work? I'm just an end user, but I really need to figure out how to fix this.

(Edit: I tried all the codes with 11701, and it said "This action is only vaild for products that are currently installed.)

[Joel_KC]

Yes, the fix in this thread does work. I have done it successfully on many users machines. Hopefully Installshield will fix their problem soon to stop it from happenning. Until then this is the only solution I have found.

[psgamer0921]

And you didn't have any problem with "This action is only vaild for products that are currently installed."

Any ideas why that would happen? (I followed the directions exactly)

Win XP Home
SP2
Account with Administrative Access

(The only thing I did different was change "cd windows\system32\" to "cd c:\windows\system32\ [without quotes])

[Joel_KC]

I don't know why that would be happenning. Luckily, I write the installs for my software so I had an informed knowledge of what GUID's I was looking for and which to remove. I have never had the message that you elude to. Sorry.

On a side not I have had this error happen on people's machine that use a base disc drive named something other than C. For example, one of my customers uses a machine with a D drive instead of a C drive and he has similar problems.

[ruvikazar]

Hi all,

I had this exact problem. I solved it by removing 2 objects from the redistributables page:
MSDE 2000 Connectivity Components
MSDE 2000 Setup Base Merge Module

My application (written in C#) was installed successfully and runs ok without these two objects for now.

Hope it helps.

[IQpierce]

psgamer: The error messages you're recieving are probably normal.

You're attempting to force the uninstallation of every installation of a certain type that has been run on your computer. Some of those installations are products that you will have uninstalled since then.

Ignore those messages and continue following the steps. Did you finish running the steps for every Event Log entry, or did you stop when you recieved those errors?

[psgamer0921]

I completed every step, regardless of errors, for every 11707 entry, but every single one gave me that error. Would this be something that a repair of XP could fix?

[neal007]

Does anyone know if IS 10.5 fixes this? My users are getting this now and I'm using IS X InstallScript MSI.

[habells]

I've spent hours working the same Quicken errors with 2005 and then trying to get back 2004.

I really need to get it working and Quicken support's only response is to work it thru InstallShield.

I finally got it installed by uninstalling sp2 but now I'm getting spooling errors that the error reporting says can be fixed by installing sp2. But the only way to install it is thru Windows update and my windows update thinks that it's already installed so I don't have an option to install it!

Can anyone help me with how I can get a link to install xp sp2?

btw: does Intuit have ANY clue that they have this problem???

[crmckenzie]

I'm having the same problem on Windows 2003 Server. Is there a resolution for this yet?

[habells]

well, I had a couple of problems.
To get Quicken installed, I had to uninstall sp2 and then quicken installed fine.

To get sp2 back installed again: I followed the MSFT links on their Win XP Sp2 site about if you were IT and trying to install this on multiple computers. That took me to a link to download the sp2 install.

Intuit provides no help so I don't know if there's a resolution or not.

I almost switched to Money since I had a copy anyway from a new computer.. you might try that.

[bmwlvwa]

I followed the guidelines on http://support.microsoft.com/?kbid=836724 to successfully resolve this issue.

[jbaker6953]

I have discovered that I can reliably reproduce this error in some third-party InstallShield script-based installs that call "OnMoved" from the ISScriptBridge.dll. If I remove that row from the CustomActions table I can install the product.

[wkrasl]

Hi. I'm NOT a developer, NOT a programmer. Just an end user who has spent 3 days now trying to get Quicken 2005 to install on my desktop. In my various interactions with Dell, Intuit, Microsoft, and now InstallShield I have discovered this community. Perhaps you can help a novice end user like me.
Problem: WinXP Home edition with SP2, on a Dell desktop - Quicken 2005 gets to 100% on the installation progress bar, says "Publishing Product Information", and then I get the "Installation was interrupted. Quicken 2005 was not installed" message. Now, it worked without a hitch, perfectly, no problem, on a Dell laptop also running WinXP SP2. Both appear to be configured nearly the same. I have administrator priviledges on both.

...

Many thanks.

I hit an install problem with Quicken 5 on my Dell Inspiron 300m laptop on Wednesday. Today, I got as far as your post and see you had the same problem at the same "Publishing Product Information, Installation was interrupted, Quicken 2005 was not installed" message.

I also see it hit you on your desktop, but not laptop. Mine is a laptop, so desktop vs laptop is not a parameter.

Did you get a solution? Is anybody here able to help? :confused:

Intuit told me it was Microsoft's fault with XP sp2. Microsoft referred me to Dell. Dell told me to wipe my hard drive and reinstall from the recovery disks.
:mad:

Regards,
Walt

======== Okay. Sorry. I found the above quote on a search, and didn't see that I was at the bottom of page 5 of 9. I just thought that was the last post in the thread. Give me time to try something from pages 6-9. I'll report back here if I succeed or fail. Thanks.

[wkrasl]

I followed the guidelines on http://support.microsoft.com/?kbid=836724 to successfully resolve this issue.

Hmmmm.... I'd love to know how it worked for you.

Going to the article, "RESOLUTION" failed at step "2.c.b." Right-clicking "My Computer" in Dcomcnfg.exe did not present "Properties" in a pop-up menu, so it could not be clicked. However, I did notice a computer icon on the right end of a toolbar just below the main window menu. It had a "COM Security" tab, which let me see Access Permissions and Launch & Activation Permissions. I figured this was the equivalent to the failed steps.

Continuing with the article, I clicked Edit Default under Access Permissions. It showed SELF and SYSTEM. I added my login name, "wkrasl," checking the "Allow" boxes. After a reboot, I tried to install Quicken again. No luck. Same error.

I then went back in and added "Administrator" thinking it wanted the default computer administrator name. I also tried to add a fake name as a control, which was correctly rejected on "Check Names." After a reboot, I tried to install Quicken again. Still no luck. Same error.

Going back to the article, based on the "CAUSE" description, I looked at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole. "DefaultAccessPermissions" does not exist. Therefore the problem is not caused by the two conditions stated in the article.

Arghhh!

[wkrasl]

Everything I tried failed, including very carefully following IQpierce's post on msiexec.exe /x {........}. It's amazing what I've learned tonight.

So I went back to basics. I used Add/Remove to remove SP2, installed and tested Quicken 2005 without a hint of a problem, and installed the 19 pre-SP2 security patches that showed up. I then reinstalled SP2, defragged the drive, and installed the 3 SP2 security patches. End of problem. :cool:

Thanks for listening... Bye...

[coedog]

If you come across this problem installing an application on a Windows 2003 server running IIS6, a change needs to be made to the local security policy. The local Administrators group needs to be given the Impersonate a client after authentication right and then the server needs to be rebooted for it to take effect.

[Seansms]

Ditto for me. Although others say they have had it work with SP2.

Everything I tried failed, including very carefully following IQpierce's post on msiexec.exe /x {........}. It's amazing what I've learned tonight.

So I went back to basics. I used Add/Remove to remove SP2, installed and tested Quicken 2005 without a hint of a problem, and installed the 19 pre-SP2 security patches that showed up. I then reinstalled SP2, defragged the drive, and installed the 3 SP2 security patches. End of problem. :cool:

Thanks for listening... Bye...

[praxis22]

I had the same problems, and the same discoveries about the MS article on SQL referenced above.

I'm having the same problems, mostly with games and game demos. I'm not a novice at this, I've been using computers for some 25 years, I built my first computer from a kit.

I started to get this with "Sid Meier's Pirates!" But I opted for the sneaky way of installing that, waiting untill it says "publishing/registering product" then hit the main power off switch before it can delete it all. With others I've simply copied out the programs either from the decrompressd install folders in the temp dir or from the installed location as it's installed, since XP, bless it's cotton socks still isn't trully multitasking, so if you copy the folder then paste it as it's installing it has to wait to finish the install, as the copy takes precedence.

The only drawback with that is that frequently you end up mising bits. There is no sound in Lego star wars, and the breifing don't work on the new Freedom Force demo.

I might try the Orca edit method, see if that works, because as somebody who installs and uninstalls stuff frequently, I don't want to have to uninstal all my 1707's nor SP2. If only because I'd end up doing it every week or so.

I figure it's dcom related, but I also figure it's installshield's problem, I'm running the latest patches as of this weekend, including the latest windows installer 3. I figure it's up to installshiled to sort thier **** out, though given my experience with software over the years I doubt this will happen in any good order. They have your money, they don't care if it works, anyone who belives otherwise is fooling themselves.

EDIT: set windows installer to Automatic, installed the latest installshield scripts (V 10) added everything I can think of to the DCOM security settings, and *still* "the wizard was interrupted..." looks like I'm downloading 200+Mb of SDK from MS, luckily I have 2Mb Broadband.

[irnbru]

I am also having this problem with installshield, I have tried ALL the fixes listed here with no success.
I am running:

Acer RC900
Intel p4 3200mhz
200gb hd
ATI radeon 9800 pro
Windows Xp sp2

I am having this problem with 3 programs, 1: Rome: Total War, 2: Trust Webcam setup and 3: a DCA-540 mobile phone manager.

Each of these setups get right to the end of the installation and then quits with the afforementioned message.
I had no problems installing Rome: TW previously, but then I did a complete wipe of my hard drive and reinstalled everything (I had a nasty virus i couldnt shake off)
I have created a log of the install for the mobile phone manager, perhaps it will make sense to someone, and I will create logs for the others when i get a chance.

15:42:15 | Log file created 8-7-2006
15:42:15 | Time: 15:42:15
15:42:15 | #############################################################
15:42:15 | # DEBUG INFO #
15:42:15 | #############################################################
15:42:15 | CMDLINE =
15:42:15 | COMMONFILES = C:\Program Files\Common Files\
15:42:15 | DISK1TARGET = C:\Program Files\InstallShield Installation Information\{6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6}
15:42:15 | FOLDER_DESKTOP = C:\Documents and Settings\All Users\Desktop\
15:42:15 | FOLDER_PROGRAMS = C:\Documents and Settings\All Users\Start Menu\Programs\
15:42:15 | FOLDER_STARTMENU = C:\Documents and Settings\All Users\Start Menu\
15:42:15 | FOLDER_STARTUP = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
15:42:15 | INFOFILENAME =
15:42:15 | INSTALLDIR = C:\Program Files\Mobile Phone Manager\
15:42:15 | ISRES = C:\DOCUME~1\Tommy\LOCALS~1\Temp\{6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6}\_isres.dll
15:42:15 | ISUSER = C:\DOCUME~1\Tommy\LOCALS~1\Temp\{6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6}\_isuser.dll
15:42:15 | ISVERSION = 7.7.0.262
15:42:15 | MEDIA = DATA
15:42:15 | PRODUCT_GUID = {6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6}
15:42:15 | SHELL_OBJECT_FOLDER =
15:42:15 | SRCDIR = f:\
15:42:15 | SRCDISK = f:
15:42:15 | SUPPORTDIR = C:\DOCUME~1\Tommy\LOCALS~1\Temp\{6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6}\
15:42:15 | TARGETDIR = C:\Program Files\Mobile Phone Manager\
15:42:15 | TARGETDISK = C:
15:42:15 | UNINSTALLKEY = InstallShield_{6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6}
15:42:15 | UNINSTALL_DISPLAYNAME = Mobile Phone Manager
15:42:15 | UNINSTALL_STRING = C:\PROGRA~1\COMMON~1\INSTAL~1\Driver\7\INTEL3~1\IDriver.exe /M{6BAA26DB-2D4E-42B6-BC3F-3B58144A64B6} /l2057
15:42:15 | WINDIR = C:\WINDOWS\
15:42:15 | WINDISK = C:
15:42:15 | WINSYSDISK = C:
15:42:15 | WINSYSDIR = C:\WINDOWS\system32\
15:42:15 | USERNAME = Tommy
15:42:15 | VersionMsi = 3.01
15:42:15 | ProductVersion = 3.05.28.51.2.0
15:42:15 | found Esi in Setup
15:42:15 | no RIM BBDesktop in Setup
15:42:15 | found GPRS MA in Setup
15:42:15 | BUILD_DATE :08/02/05 21:06:45
15:42:15 | OS: Windows XP
15:42:15 | OS: ServicePack: 2
15:42:15 | OS: user is logged in under NT with administator rights.
15:42:15 | OS: the shell is Explorer.
15:42:15 | OS: the processor is Intel.
15:42:15 | OS: operating system's version: 5.1
15:42:15 | OS: Windows Version: 5.1
15:42:15 | #############################################################
15:42:15 | try to run: cmd /c "f:\pre.bat "
15:42:16 | run: cmd /c "f:\pre.bat "finished Wait
15:42:16 | Debug: ProgDefGroupType is COMMON!
15:42:16 | ### OnBegin() end
15:42:16 | ### OnFirstUIBefore() begin
15:42:16 | check OS
15:42:16 | BUGFIX delete old RegKey: Installer\Products\BD62AAB6E4D26B24CBF3B38541A4466B
15:42:16 | Software\Microsoft\Installer\Products\BD62AAB6E4D26B24CBF3B38541A4466B
15:42:16 | ## begin parseCommand_first()
15:42:16 | Commandline:
15:42:16 | ## end parseCommand_first()
15:42:16 | ### Dlg_SdWelcome
15:42:17 | ### Dlg_ChosePhone
15:42:17 | ## begin GetPhoneDialog()
15:42:17 | TelefonType is set to S65
15:42:17 | ## end GetPhoneDialog()
15:42:17 | ## begin checkCommandlineAllowed
15:42:17 | CMDLINE = ''
15:42:17 | ## end checkCommandlineAllowed
15:42:17 | ### Dlg_SdLicense
15:42:18 | ### Dlg_SdAskDestPath
15:42:18 | ### Dlg_SetupType
15:42:19 | ### Dlg_SdFeatureTree
15:42:19 | ## begin parseCommand_first()
15:42:19 | Commandline:
15:42:19 | ## end parseCommand_first()
15:42:19 | ## begin SetSelectedComponents()
15:42:19 | set to S55/SL55/M55
15:42:19 | TYPICAL
15:42:19 | ## end SetShownComponents()
15:42:19 | ## Begin checkOutlook
15:42:19 | ## End checkOutlook
15:42:19 | ## Begin checkLotusNotes
15:42:19 | ## End checkLotusNotes
15:42:19 | Select SDSSYMBIAN\SDS_SYNC\OutlookExpress
15:42:19 | ### Dlg_SdSelectFolder
15:42:19 | ## begin parseCommand_first()
15:42:19 | Commandline:
15:42:19 | ## end parseCommand_first()
15:42:19 | Dlg_SdSelectFolder
15:42:19 | SHELL_OBJECT_FOLDER = Mobile Phone Manager
15:42:19 | szfolder = Mobile Phone Manager
15:42:19 | ### Dlg_SdStartCopy
15:42:19 | SHELL_OBJECT_FOLDER = Mobile Phone Manager
15:42:20 | SHELL_OBJECT_FOLDER = Mobile Phone Manager
15:42:20 | ### OnFirstUIBefore() end
15:42:43 | ### BEGIN: MPM_PROGRAMM_Installing
15:42:43 | Debug: ProgDefGroupType is COMMON!
15:42:43 | ### END: MPM_PROGRAMM_Installing
15:42:43 | ### launch check_setting (DESSYMBIAN) ###
15:42:43 | ### check_setting () return false ###
15:42:43 | ## get_language() begin
15:42:43 | ## get_language() end
15:42:43 | #### start set_register ####
15:42:43 | try to register key: 2 value: 2057
15:42:43 | register SCfgSrv.exe again..
15:42:43 | try to run: C:\Program Files\Mobile Phone Manager\bin\SCfgSrv.exe /regserver
15:42:43 | Error: starting C:\Program Files\Mobile Phone Manager\bin\SCfgSrv.exe /regserver
15:42:43 | Error: Could not create EnvironmentServer
15:42:43 | #### end set_register ####
15:42:43 | Debug: ProgDefGroupType is PERSONAL!
15:42:43 | BEGIN install GPRS_MODEM
15:42:43 | try to install GPRS MA
15:42:43 | try to run: C:\Program Files\Mobile Phone Manager\GPRS\setup.exe -s -p"C:\Program Files\Mobile Phone Manager\GPRSv2" -m"C:\Documents and Settings\All Users\Start Menu\Programs\Mobile Phone Manager"
15:42:43 | Error: starting C:\Program Files\Mobile Phone Manager\GPRS\setup.exe -s -p"C:\Program Files\Mobile Phone Manager\GPRSv2" -m"C:\Documents and Settings\All Users\Start Menu\Programs\Mobile Phone Manager"
15:42:43 | install GPRS MA -> SUCCEDED
15:42:43 | ## get_language() begin
15:42:43 | ## get_language() end
15:42:43 | ## installDriver
15:42:43 | try to install C:\WINDOWS\inf\SiemensSX1IrDA.inf
15:42:43 | Error: install Driver C:\WINDOWS\inf\SiemensSX1IrDA.inf File do not exists
15:42:43 | ## END installDriver
15:42:43 | ## installDriver
15:42:43 | try to install C:\WINDOWS\inf\mdmirmdm.inf
15:42:43 | Error: install Driver C:\WINDOWS\inf\mdmirmdm.inf File do not exists
15:42:43 | ## END installDriver
15:42:43 | ## installDriver
15:42:43 | try to install C:\WINDOWS\inf\siusbmod.inf
15:42:43 | Error: install Driver C:\WINDOWS\inf\siusbmod.inf File do not exists
15:42:43 | ## END installDriver
15:42:43 | ## installDriver
15:42:43 | try to install C:\Program Files\Mobile Phone Manager\driver\ActSer\device.inf
15:42:43 | Error: install Driver C:\Program Files\Mobile Phone Manager\driver\ActSer\device.inf File do not exists
15:42:43 | ## END installDriver
15:42:43 | ### end install_SymbianMessenger ###
15:42:43 | END istall GPRS_MODEM

It seems to have a problem with

15:42:43 | try to register key: 2 value: 2057
15:42:43 | register SCfgSrv.exe again..
15:42:43 | try to run: C:\Program Files\Mobile Phone Manager\bin\SCfgSrv.exe /regserver
15:42:43 | Error: starting C:\Program Files\Mobile Phone Manager\bin\SCfgSrv.exe /regserver
15:42:43 | Error: Could not create EnvironmentServer
15:42:43 | #### end set_register ####

hope this helps, I will post the other logs when I get a chance

[IQpierce]

Wow it has been so long since I've looked at this thread...

The most consistent way people found to fix this problem was to uninstall Windows XP Service Pack 2 and then try installing again. Did you try doing that, irnbru?

I'm actually not sure how to go about uninstalling SP2. Another solution is to reinstall Windows :o and either hope it never happens again, or else install the programs in question before installing the SP2...


There's nothing worse than a wizard being interrupted. Take it from me... the other day I was interrupted right in the middle of putting on my robe and wizard hat...

[irnbru]

yes, I have tried uninstalling sp2, still no joy. I am really not wanting to have to go down the whole reinstall of windows, I have my HD almost full and its alot of disc burning to back up my important files.

[irnbru]

I think I am gonna bite the big one, reinstall xp... (unless someone come in with a new fix suggestion within the next hour or so) because I have spent the last few days trying various fixes and workarounds to get these to install...

I will post back my results when I get them installed (or not)

[mahara]

I found this: http://www.minitab.com/support/answers/answer.aspx?ID=1848 had solved my problem.

The point is there is something wrong with Microsoft Windows Script 5.6, whether it's corrupted or outdated. All you need to do is reinstalling it. Here are the links:

Microsoft Windows Script for Windows 98 ME and NT (http://www.microsoft.com/downloads/details.aspx?FamilyId=0A8A18F6-249C-4A72-BFCF-FC6AF26DC390&displaylang=en)
Microsoft Windows Script for Windows 2000 and XP (http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en)


Hope helps.

[noabody]

I have a U.S. XP Pro computer recently updated to SP3 (updated not re-installed). This computer also had Microsoft AppLocale and East Asian languages installed for Japanese support. The program in question was a setup.exe that unwrapped it's setup.msi in the %temp% folder during installation.

I figured out how to get a log file using these options: setup.exe /V"/Liwe c:\setuplog.txt" where the /V switch passes command line options through to setup.msi, /L creates a specified log file, i logs status messages, w logs non-fatal warning messages, and e logs any error messages. The relevent information from the logfile was this:

Action start 20:51:37: InstallFinalize.
Error 0x80070003 opening directory D:\localization\espanol
Action ended 20:52:37: InstallFinalize. Return value 3.
Action ended 20:52:48: INSTALL. Return value 3.
Action ended 20:52:48: ExecuteAction. Return value 3.
Action start 20:52:48: SetupCompleteError.
Action ended 20:53:06: SetupCompleteError. Return value 2.
Action ended 20:53:06: INSTALL. Return value 3.

I opened the noted path and found that it was actually D:\localization\español . In fact the installer failed to copy any accented file or folder name.

I went to run applocale and found that it was not properly installed so I uninstalled it. I also removed the East Asian languages and installed Windows Installer 4.5 XP 32-bit edition WindowsXP-KB942288-v3-x86.exe. After doing these three things and rebooting the computer the installation went fine.

I'm not inclined to try to reproduce the problem but it could have been related to the SP3 upgrade, East Asian languages, AppLocale or even the Microsoft installer. Ultimately the way that it failed on the accented characters is the key thing. Perhaps this will be helpful to someone else.