Error 1606. Could not access network location 1

[Jonathan Gilbert]

Hello,

Has anyone seen the following error, and been able to fix it?

"Error 1606. Could not access network location 1"

Thanks

[Rob Hamflett]

I can't remember the error number, but I use to get "Could not access network location dummy" when I
would use 'dummy' as a temporary value for a directory until I could fill it in with a custom
action. I had to change it to C:\dummy to make the installer happy. Maybe it's related to that?
Are you setting a location yourself with a CA and using some value as a filler until then?

Rob

[Jonathan Gilbert]

Hi Rob,

Thanks for the reply, I am setting a directory with a custom action, but
when i changed it, it didn't help. I have this in another msi, and it was
working. Still hunting i guess...

thanks

jonathan

"Rob Hamflett" <r...@snsys.com> wrote in message
news:%23fMdY9H...@TK2MSFTNGP09.phx.gbl...

[Phil Wilson]

Doing the install with a log might help - you might see the property or
directory value that isn't working. The general problem tends to be that
locations that don't start with a drive letter are interpreted as network
shares.

You can get this error if a system has an error in the specs for folders.
Here's an example that can happen during any install:

http://support.microsoft.com/default.aspx?scid=kb;en-us;330766
--
Phil Wilson [MVP Windows Installer]
----
"Jonathan Gilbert" <jonathan...@autodesk.com> wrote in message
news:elPm5yHE...@TK2MSFTNGP15.phx.gbl...

[Jonathan Gilbert]

thanks, turns out i had a directory and property as the same name, i was
creating a new install using an older one i wrote, and i didn't know about
the conflict, as you can guess the property was set to '1', so the directory
was getting set to that too, oops.

i feel sheepish

"Phil Wilson" <Phil....@unisys.spamcom> wrote in message
news:%23J%231OgKE...@TK2MSFTNGP14.phx.gbl...