Hi again,

I have yet another error I'm experiencing on Win 2008 64 bit server... 1606 - Could not access network location %SystemDrive%\Inetpub\wwwroot.

It seems that on this OS, the System Drive Evnironment Variable is handled weird, incorrectly or something. Even from the command prompt I can't change to this directory using this Env. Var.

If I change the following (hard code the system drive) the install proceeds past this problem point.


HKLM\Software\Microsoft\InetStp\PathWWWRoot (had value of %SystemDrive%Inetpub\wwwroot changed to c:\inetpub\wwwroot)
The same change had to be made in the 64 bit hive as well.

I'm wondering if this is a known problem on this platform and what I'm going to be able to do about it.

I'm going to reproduce the problem here, log the install and see where it is failing. I guess that might give me a better idea on a course of action. If anyone has any experience with this, let me know.

Thanks much as always!!!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
IIRC, you can get the root path from the registry. Is it HKLM\SOFTWARE\\Microsoft\\INetStp\PathWWWRoot?
Answered 11/16/2009 by: VBScab
Red Belt

Please log in to comment
0
I'm not quite sure I know what you mean by that reply but that is the key we are checking and it is populated with %SystemDrive%\inetpub\wwwoot when it errors.
Answered 11/16/2009 by: Superfreak3
Black Belt

Please log in to comment
0
That'll teach me to read the whole post, won't it? :)

I think you're going to have to add a Custom Action to parse the value you get from that registry entry and "convert" it into the format which indicates to the Windows Installer engine that it's an environment variable, i.e. [%SystemDrive]. So your CA needs to strip the trailing % sign and enclose the whole shebango with square brackets.
Answered 11/16/2009 by: VBScab
Red Belt

Please log in to comment
0
I can make a custom action to grab the registry entry and parse and set as you say, but what am I then going to do with that value. Is it blowing up on a Windows Installer action of setting some type of property? I'm still not quite sure how to fix, or I should say work around this.

Here's a snippet of the log when the error happens...


MSI (c) (7C:4C) [07:03:29:528]: PROPERTY CHANGE: Adding INSTALLDIR2 property. Its value is 'C:\Adept7\'.
MSI (c) (7C:4C) [07:03:29:528]: PROPERTY CHANGE: Adding app_code property. Its value is 'C:\Adept7\app_code\'.
MSI (c) (7C:4C) [07:03:29:528]: PROPERTY CHANGE: Adding app_data property. Its value is 'C:\Adept7\app_data\'.
MSI (c) (7C:4C) [07:03:29:528]: PROPERTY CHANGE: Adding bin property. Its value is 'C:\Adept7\bin\'.
MSI (c) (7C:4C) [07:03:29:528]: Note: 1: 1314 2: %SystemDrive%\inetpub\wwwroot\
MSI (c) (7C:4C) [07:03:29:528]: Note: 1: 1606 2: %SystemDrive%\inetpub\wwwroot\
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
Internal Error 2835. ErrorIcon, ErrorDialog
Error 1606. Could not access network location %SystemDrive%\inetpub\wwwroot\.
MSI (c) (7C:4C) [07:03:32:010]: Product: Synergis Adept Explorer 8.1 -- Error 1606. Could not access network location %SystemDrive%\inetpub\wwwroot\.
MSI (c) (7C:4C) [07:03:32:010]: Note: 1: 1606 2: %SystemDrive%\inetpub\wwwroot\
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
Internal Error 2835. ErrorIcon, ErrorDialog
Error 1606. Could not access network location %SystemDrive%\inetpub\wwwroot\.
MSI (c) (7C:4C) [07:03:33:353]: Product: Synergis Adept Explorer 8.1 -- Error 1606. Could not access network location %SystemDrive%\inetpub\wwwroot\.
Action ended 7:03:33: CostFinalize. Return value 3.

Answered 11/16/2009 by: Superfreak3
Black Belt

Please log in to comment
0
Use the parsed string to change the value in your package from %SystemDrive%\inetpub\wwwroot to [%SystemDrive]\inetpub\wwwroot.

When the engine runs the package, it sees the square brackets, so it knows this is a property to be resolved and the leading % sign indicates that it needs to resolve it using an environment variable.
Answered 11/17/2009 by: VBScab
Red Belt

Please log in to comment
0
That's the thing, I can't find SystemDrive in my package anywhere. I don't know if this is a Wise action trying to resolve this path or something else, but I can't find it. Looking at the log snippet and my package, it looks as though it has something to do with the Directory table.

I was thinking of maybe seeing if I can detect/parse this from the registry and hard code that value to the actual System Drive. Then possibly revert it back at some point.
Answered 11/17/2009 by: Superfreak3
Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity