error 1608

when it asks to check the permissions, when I access the Computer Management, the Local Users and Groups doesn't show up anywhere at all.

that one in itself is not tremendously unusual. i don't have one either on my XP Home box.

... okay, continuing to work through the exotica.

is your PC showing any signs of the symptoms described in the following KB doc?

Systems that have changed the default Access Control List permissions on the %windir%\registration directory may experience various problems after you install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC

(never seen this problem linked to a 1608 before. but it does take out the Windows Installer, which would cause the generalised problems with InstallShield you're getting.)

love, b

b noir, that post on the MS website does not seem to relate to WindowsXP, so how is it relevant?
Oops, sorry, misread it, I'll get back once I try the solution.

hmmmm.

don't beat yourself up about it. on looking at it again, i reckon it's actually a bit unclear on various levels. under "symptoms" it's saying XP (home or pro unspecified), but under "applies to" it's saying only XP Pro.

... on the other hand, it's saying XP Pro twice under "applies to" ... perhaps one of them is supposed to be XP Home ...

love, b

b,

if it's a Home box, check through this
InstallShield KB doc again:

Configure the DCOM Settings on Your
Computer

I went through this doc again, and it finally worked. It turns out that I couldn't just "Add" the "Everyone" user manually, as I did in the past (obviously, didn't work). I had to pulldown the list of available domains, and select my own PC as the domain. Within that domain, there was an "Everyone" user/group that I could assign an "Always Allow" setting to.

Okay, just to clarify, this is not for the iTunes 6.0.x upgrade -- I've abandoned that notion. This was to get 4.8 running again, including the iTunesHelper.exe which had failed.

well done Orbitflinger, and many thanks for the report!

I went through this doc again, and it finally worked. It turns out that I couldn't just "Add" the "Everyone" user manually, as I did in the past (obviously, didn't work). I had to pulldown the list of available domains, and select my own PC as the domain. Within that domain, there was an "Everyone" user/group that I could assign an "Always Allow" setting to.

interesting. i've noticed that other InstallShield advice pages are a bit behind the times when it comes to Windows references. i wonder if the way DCOM settings are set-up on Windows PCs has changed "out from under" the InstallShield advice?

not sure precisely how to go about checking on that. if you've got the time and inclination, InstallShield does have a "report your error" feedback channel:

InstallShield: submit your error

... not sure how effectual that avenue is in practice (with regard to asking about the InstallShield advice, or describing alternate techniques to them), though.

everyone else with the recalcitrant 1608s here ... does Orbitflinger's technique help for any of y'all?

love, b

Just a follow-up. After I was successful in getting 4.8 iTunes and Quicktime 6.5.2 and it has been running smoothly, I thought I needed more challenges in life, and decided to see if I could install Quicktime 7.0.2. I used the stand-alone installer, and guess what?

When I hit the installing ISShield11 it bonked out with our infamous error 1608.

Andrew

this is with the correct DCOM settings? they haven't "changed back" of their own accord to the funny ones again, have they?

(never heard of that happening before, but this has been such a weird beast so far ...)

love, b

b,

this is with the correct DCOM settings? they haven't
"changed back" of their own accord to the funny ones
again, have they?

I checked the DCOM settings and both me (user) and Everyone had "Always Allow" settings, so they seemed to have been retained.

(never heard of that happening before, but this has
been such a weird beast so far ...)

It is definitely at the point after the Install Shield extracts the Quicktime setup, then goes into installing ISShield11.msi and fails before this is accomplished. I followed the instrutions for manually installing the v11 of the ISShield and it looked like it sort of half worked -- I have a new directory with files:

C:\Program Files\Common Files\InstallShield\Professional\RunTime\11\00

but in this directory:

C:\Program Files\Common Files\InstallShield\Driver

I only have a "7" directory and an "8" directory. I would have expected an "11". No dice.

Andrew

Compaq Evo Windows 2000 5GB 2G iPod (mysteriously self deletes lame music)

hi Andrew!

I only have a "7" directory and an "8" directory. I would have expected an "11". No dice.

yep. i just checked mine and there's a 7, an 8 and an 11 in there. (i never had 4.8, but i did have both flavors of 4.7, and 4.9.)

so that's more evidence that the InstallShield Engine update is karking out in these weird 1608s.

hmmmmm. has that folder been set to "read only"? how about any other folders further up the path?

love, b

b,

hmmmmm. has that folder been set to "read only"? how
about any other folders further up the path?

I just checked... nope. No "read only" directories on the path.

Andrew