June 2008
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          
Search

 
Catagories
Archives
Recent Entries
Links
RSS
windows installer error 1606
Catagory: programming · This Entry · Comment(1) · eMail entry · Google
March 16, 2004 09:25 PM

programming

Error 1606 is a Windows Installer error message displayed in the following format:

Error 1606. Could not access network location

Cause :
The MSI Standard Action, CostFinalize, is unable to resolve a value of an entry defined in the directory table of the MSI package due to an invalid path.


Example of an invalid path = \My Pictures
Example of a valid path = C:\My Pictures

i ran into this when it was trying to resolve a network path!

Possible Causes :

1) An invalid path has been hard coded into the Destination field of a feature or component.

2) An invalid path has been assigned to the value of INSTALLDIR under General Information | Product Properties.

3) The Windows Installer has defined some of its own properties, such as the MyPicturesFolder property. At run time, the Window Installer tries to resolve this property to the location of the MyPictures folder for the Current User. The registry values used to resolve these properties are located at the following location:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders.

One of these values may have been changed to an invalid path.

4) A property listed in both the Property table and Directory table has been assigned an invalid path in the Property Manager.

Resolutions :

Resolution for Cause 1

Select the Setup Design view.

Verify that the Destination field for each component or feature is valid.

If any destinations are not valid, change this value to reflect a valid path.

Rebuild the release after any modifications have been made.
Resolution for Cause 2

Select the General Information | Product Properties view in the IDE.

Verify that the path specified in the INSTALLDIR field is valid.

If the path is invalid, change this value to reflect a valid path.

Rebuild the release after any modifications have been made.
Resolution for Cause 3

Verify that the values under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders all have valid paths. If the paths point to a remote computer or mapped drive, verify and establish a connection to the remote computer to which the target location refers.

To access this key, use these steps:

Click Start and click Run.

In the Open box, type regedit and click OK.

Locate and click the key shown in Step 1.

In the right pane of the registry editor window, check the value of each folder key referenced here.

If there are invalid paths referenced, these values must be changed to point to valid drives.

Close the Registry Editor and Reboot the machine.

Rerun the installation.
Resolution for Cause 4

Open the Property Manager.

Verify that one of the properties is also listed in the Directory table, which can be accessed via the Direct Editor. If no properties in the property table match any of the Directory table listings then Cause 4 is not the source of the issue.

If a property in the Property Manager does match one listed in the Directory table, verify that the property has been assigned a valid path.

If the path is invalid, the property must be deleted or a valid path must be assigned to it.

Rebuild the release after any modifications have been made.





Comments

I hope this doesn't seem rude, but I couldnt' find an e-mail anywhere on your site. I'd like to talk to you about sevenhertz.com. if you could, please e-mail me. Or IM me


AIM: BoobsIndeed
ICQ:146266666

Posted by Chris Kau at March 20, 2004 10:33 PM


Post a comment
Name:


Email Address:


URL:


Comments: