Error 1606

[Guest]

I'm getting the error message when installing my application "Error 1606
Could not access network location %49600%\Internet Explorer", and then fails.
I believe it uses the regular windows installer. I was able to install
another program that uses InstallShield with no problem.

Background:
I recently did an XPe build. This is my second try on this build. They
both booted fine after FBA. I had problems with the this recent build so I'm
trying again, with some added components (not that they would help, but just
thought they were useful in general). I did have a build of the O/S that had
no problems with the installs. That was done many months ago, and these
latest builds had 45 or more components added for functionality improvements.
I compared the components in the old builds vs. these recent ones, and it's
nothing obvious. The Windows Installer Service component is in both the old
builds and these recent builds (same version). I also installed QFE's for
these latest builds.

What I've searched on regarding this has to do with the registry key Common
Adminstrative Tools (HKLM\SOFTWARE\Microsoft\Windows\Explorer\User Shell
Folders & ...\Shell Folders). I wouldn't be surpirsed if it's a registry key
problem (possibly created by one of those QFE's), but not necessarily that
key. I would hate to think the QFE's caused the problem.

TIA for any help.

 

[KM]

Jeff,

This is likely your app installer problem. You better off turning on the MSI log.

Try to follow the steps mentioned here: http://www.umetrics.com/UmetricsKB/articledetails.asp?ArticleID=321

 

[Guest]

OK, I tried the %systemroot%\msiexec.exe /I "" /L*V "" command, except I had
to modify it. %systemroot% resolved to c:\windows, not c:\windows\system32,
which is where my msiexec.exe is located. It came back with "Incorrect
command line parameters." Just in case it should have been in the directory
%systemroot% resolved to, I made a copy of msiexec.exe in the c:\windows
directory, and it didn't help at all. That link you provided says it should
come back with the Error 1606 message, and it doesn't.

I thought maybe that 49600 number was something of significance, so I
searched the registry for this number. It's in only one place,
HKLM\SOFTWARE\Microsoft\Windows\App Paths\IEXPLORE.EXE->Path =
"%49600%\Internet Explorer". In the same area, I noticed the msinfo32.exe
app had a similar reference (also only in this one place):
\HKLM\SOFTWARE\Microsoft\Windows\App Paths\msinfo32.exe->Path =
"%49930%\MSInfo". I don't know if this is important or not. I don't even
know what those references mean. If it's supposed to resolve to something,
then there should be another key somewhere else that tells it what it means,
like %systemroot% does.

 

[KM]

Jeff,

Forget about the previous link. That was only example on how to turn on the MSIExec logging. You don't have to move msiexec
binaries.
Grab the necessary switched from here: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/msiexec.mspx


IIRC, the 49600 path is a custom one and you either have to set it up from within the INF file of your install package or by calling
SetupAPI before the install.

What application you are trying to install? Did you try it on XP Pro?
Does the app have INF file?

 

[Guest]

I went with my hunch and changed that 49600 reference in the registry to the
path to the short cut for Internet Explorer (not sure why the installer even
needs it). That worked. I'm sure it's not the proper way to fix it, but it
got the job done. Now I can go back and see the proper way to fix it. I
don't know why Target Designer did it fine many months ago, and not so fine
these last couple of times.

The app is a custom one we did using LabView and their Application Builder,
which provides an installer for the app. There is an .ini file, but it has
nothing in it except the program title. It hadn't had a problem before these
last XPe builds. I didn't try it on XP Pro. The app. would not work, as it
is meant for the specific hardware in the embedded system.

Thanks for your help.

 

[Guest]

Let me add that I just checked the registry of my previous working build, and
the
HKLM\SOFTWARE\Microsoft\Windows\App Paths\IEXPLORE.EXE->Path key had a
hardcoded path, not a referenced path. So I think I must have done something
wrong in TD that changed that.

 

[KM]

Jeff,

I am wondering what current IE component you've got in your image?
"Internet Explorer - Hotfix Q870669" (if SP1) ?

Also, if you happened to include "Outlook Express" component in your last build. That could overwrite the App Path for iexplore.exe.

 

[KM]

Jeff,

See my previous reply and please check if you included Outlook Express in your latest build.
If you did, please remove it, rebuild and deploy the image to test.

 

[Guest]

I tried to take out Outlook Express, but after doing a dependency check, it
gets put back in. Like regular Windows, it appears to be tied to IE (also
has the same Hotfix number as IE). My IE Hotfix is Q837009 (not SP1). If
there's a way to remove OE, that would be great. I don't want it. I do want
IE though. It has several uses besides web browsing. I'm now trying to just
remove OE and then not do a dependency check, then just build it. I'll see
how this works out.

 

[KM]

Jeff,

Trun off Auto Resolve Dependencies option in TD.
And don't resolve the dependency to bring in OE.

KM

 

[Guest]

Thank you KM. The combination of removing OE component and not doing a
dependency check was the trick. My app. installs fine now with me having to
change the IE registry key, (not a refenced path, but a hard path).
Although, the key for msinfo32.exe still has a referenced path of
%49930%\MSInfo in the registry key. I don't know if that's going to cause a
problem with something else, or if it'll ever be needed. If it is a problem,
I wouldn't know what component it's associated with.

Jeff

 

[KM]

Jeff,

Glad you fixed the problem.

The other key you worried about (the value %49930%\MSInfo) is coming either from Outlook Express component (which you deleted from
the Configuration) or from Internet Explorer component. You can go to the Internet Explorer component's registry section, find the
key there [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msinfo32.exe] and change its value to whatever you prefer
(something like %CommonProgramFiles%\Microsoft Shared\MSInfo"). Then you won't hit same installer problems later on.