Default folder locations on Windows XP

[Swan]

We've trying toi figure out where files should be installed when using AI Enterprise (v4.5).

There are three folders of interest in the Files and Folders pane: (1) Application Data, (2) Common Application Data, and (3) Local Application Data. We created three text files each with a unique name and dropped them into these three folders in our installer. The installer built without a problem. We then ran the installer on a Windows XP SP2 machine, the installation ran without a problem. However, we searched for the three unique text files and none of them appeared *anywhere* on the target machine.

This leads to two questions:

1) Why didn't our unique files get installed? Every file in our Application Folder got installed and various ActiveX controls got registered so it's clear most of the installation was fine.

2) What is the exact path these files should be installed for each of the three folders listed above on a Windows XP target? I'd expect the Common Application Data to be installed in C:\Documents and Settings\All Users\Application Data (which is normally hidden). Is this correct? What about the other two?

Thanks for your time. We love your product!

[gigi]

Hi,

Here is to what folders those properties point to:

Application Data: "C:\Documents and Settings\currentuser\Application Data"
Common Application Data: "C:\Documents and Settings\All Users\Application Data"
Local Application Data: "C:\Documents and Settings\currentuser\Local Settings\Application Data"

However, we searched for the three unique text files and none of them appeared *anywhere* on the target machine.

I test this and on my computer the files gets installed without problems. Please try to run the package on other computer to see if you get the same behavior.

Also you can run the package with "Run and Log" option from AI main menu and see to what folders those properties point to.

If the problem persist please sent the AIP file (if not contain any confidential informations) or test project that exhibits this behavior to support at advancedinstaller dot com so we can take a look. Also please sent the log file.

Best Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Thanks for your reply, Gigi.

I have another related question. We need to install some files in the CSIDL_COMMON_DOCUMENTS folder, which normally maps to "C:\Documents and Settings\All Users\Documents" (or "C:\Documents and Settings\All Users.WINDOWS\Documents" on some machines). I don't see this listed in the standard "System Folder Properties" options. Is there some AI Install Parameters Property I can define and use? How do I get AI to recognize this common documents folder as a target folder?

[gigi]

Hi,

I have another related question. We need to install some files in the CSIDL_COMMON_DOCUMENTS folder, which normally maps to "C:\Documents and Settings\All Users\Documents

This folder is valid only for Windows NT systems and Microsoft Windows 95 and Windows 98 systems with Shfolder.dll installed. Does not exist on AI predefined folders list.

To create such a folder create a property in the "Install Parameters" page, name it COMMON_DOCUMENTS for example. Now create a "Property Set With Formatted" custom action under "InstallExecuteSequence->CostFinalize" section. In the "Property Name" field type COMMON_DOCUMENTS, in the "Formatted Text" field type [%ALLUSERSPROFILE]\Documents.

Now switch to "Files and Folders" and create a "New Folder->Property Based" and select the property below.

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Thanks again, Gigi, for your reply.

We've tried several combinations of what you suggested below. We're probably making a silly mistake so perhaps you can set us straight. Here's exactly what we did:

1. Under Install Parameters>Properties we created a new property: Name is CommonDocuments, Value is [|COMMON_DOCUMENTS]. (We tried several combinations of the Value including COMMON_DOCUMENTS and [COMMON_DOCUMENTS]).

2. Under Custom Actions>InstallExecuteSequence, we added a CostFinalize action with PropertySource (created with New Custom Action>Property Set with Formatted. The Property Name is CommonDocuments, the Formated Text is [%ALLUSERSPROFILE]\Shared Documents. The Custom Action resolved value appears to be correct and the "Shared Documents" folder does exist.

3. Under Files and Folders, we were able to create a CommonDocuments folder using New Folder>Property Based and selecting CommonDocuments ([|COMMON_DOCUMENTS]). We dragged several files into this folder.

We then executed Project>Run and Log. Unfortunately, we got an error associated with our new folder. An alert box was displayed with the following text: Could not access network location [COMMON_DOCUMENTS].

Here is the output from the Run Log:
MSI (c) (28:6C) [10:18:46:535]: PROPERTY CHANGE: Modifying SHORTCUTDIR property. Its current value is 'C:\Documents and Settings\All Users.WINDOWS\Start Menu\Programs\LANsurveyor'. Its new value: 'C:\Documents and Settings\All Users.WINDOWS\Start Menu\Programs\LANsurveyor\'.
MSI (c) (28:6C) [10:18:46:567]: Note: 1: 1314 2: COMMON_DOCUMENTS
MSI (c) (28:6C) [10:18:46:582]: Note: 1: 1606 2: COMMON_DOCUMENTS
Error 1606. Could not access network location COMMON_DOCUMENTS.
MSI (c) (28:6C) [10:34:33:775]: Product: LANsurveyor -- Error 1606. Could not access network location COMMON_DOCUMENTS.

MSI (c) (28:6C) [10:34:33:791]: Note: 1: 1606 2: COMMON_DOCUMENTS
Error 1606. Could not access network location COMMON_DOCUMENTS.
MSI (c) (28:6C) [10:34:35:150]: Product: LANsurveyor -- Error 1606. Could not access network location COMMON_DOCUMENTS.

Action ended 10:34:35: CostFinalize. Return value 3.
MSI (c) (28:6C) [10:34:35:213]: Doing action: FatalError
Action 10:34:35: FatalError.
Action start 10:34:35: FatalError.

[gigi]

Hi,

Under Install Parameters>Properties we created a new property: Name is CommonDocuments, Value is [|COMMON_DOCUMENTS]

The value field for a property in the "Install Parameters" page is interpreted as plain text not as formatted or pseudo formatted.

The error you get is because windows installer try to access that resource and a folder ([|COMMON_DOCUMENTS]) does not exist.

To solve this you can type a valid initial value for the "CommonDocuments" property (for example: C:\) or you can schedule the custom action "Property Set with Formatted" under "InstallUISequence->Begin" section with same parameters (recommended).

Best Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Thanks, again, for your reply Gigi.

Sorry to be dense, but could you be more specific about your answer as both of the solutions you presented are not untuitive to me.

If I schdule the custom action "Property Set with Formated" under "InstallUISequence->Begin" with the same parameters, what exactly would the Property Name and Formated Text values be? And, if I use this solution, do I need the CommonDocuments property at all and, if so, what Value would I use?

If I type an initial value for the "CommonDocuments" property (for example: C:\", that will cause a problem if the user's Windows installation is on a volume other than C:\ so this seems kind of dangerous to me.

[gigi]

Hi,

If I schdule the custom action "Property Set with Formated" under "InstallUISequence->Begin" with the same parameters, what exactly would the Property Name and Formated Text values be? And, if I use this solution, do I need the CommonDocuments property at all and, if so, what Value would I use?

What I was trying to say is to create the "Property Set With Formatted" custom action under "InstallExecuteSequence->Begin" not under "InstallExecuteSequence->CostFinalize" (you can drag it from "CostFinalize" and drop it in the "Begin" section). In the "Property Name" field type "CommonDocuments", in the "Formatted Text" field type [%ALLUSERSPROFILE]\Documents.

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Thanks, again, Gigi.

We're closer but still not there.

I moved the InstallExecuteSequence->CostFinalize property to "InstallExecuteSequence->Begin". I also editted the CommonDocuments property Value to be "C:\".

The installer ran, but installed the items in the Files & Folders CommonDocuments folder into C:\, rather than C:\Documents and Settings\All Users.WINDOWS\Documents.

I then editted the CommonDocuments property value to be "[%ALLUSERSPROFILE]\Documents" but the installer failed because that location couldn't be found.

I'm still missing something basic.

[gigi]

Hi,

Hmm, sorry I made a mistake. In my last post I say "InstallExecuteSequence->Begin", but you need to move the custom action to "InstallUISequence->Begin".

Kind Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Hi Gigi,

I moved the custom action to "InstallUISequence>Begin". The same thing happens: the items in the CommonDocuments folder get put into C:\ rather than C:\Documents and Settings\All Users.Windows\Shared Documents. (By the way, in previous posts I wrote "Documents" when I really meant "Shared Documents" as the destination folder.)

The problem seems to be the CommonDocuments custom property value. It is "C:\" now and that's causing the problem. When I look at the Run Log, I see my CommonDocuments custom property correctly set to "C:\Documents and Settings\All Users.Windows\Shared Documents" but during the FinalCost step, it gets changed to "C:\" and I think that's what causes the installer to install to "C:\".

How do I get the FinalCost step to do the right thing?

[Swan]

To summarize the solution which Gigi provided me in an email:

1. Create a property in the "Install Parameters" page name it COMMON_DOCUMENTS (upper cases).
2. Switch to "Custom Actions" page and create a new "Property Set With Formatted" custom action under "InstallUISequence->Begin". Use following options for the custom action:
- Property Name: COMMON_DOCUMENTS
- Formatted Text: [%ALLUSERSPROFILE]\Documents (not Shared Documents)
3. Now drag & drop (while the "Shift" key is pressed) this custom action to "InstallExecuteSequence->Begin".
4. Switch to "Files and Folders" page and create a "New Folder->Property Based", select the COMMON_DOCUMENTS property. Add your files in this folder.

Note: regarding step #1 -- it doesn't seem to matter what the Value field contains in the COMMON_DOCUMENTS custom property. I simply typed the text "undefined".

[ssearles]

Ok, sorry to ressurect an old post, but I'm having a somewhat similar issue I believe with some ActiveX DLL I'm trying to install. I have created a standard folder "Windows\Downloaded Program files" under files and folders. Places all my dll's I need in that folder, and set them to Auto Register.

what I'm seeing is on the target machine, the registry entries for the DLL regiatration are there, and are correct. but when I go to the folder, I absolutely do not see any files. All I'm trying to do at this point is verify that the files payload is indeed installed to the target machine, and that the registration of the DLL's (which seem to be working and I can see them in the registry) are complete and correct.


Has anyone else seen this or have a suggestion on what I can do?


TIA

[Cosmin]

Hi,

I'm not sure why you are encountering this behavior. Does it happen on multiple machines? If so, can you please send us the .AIP (project) file you are using and a verbose log of the installation process to support at advancedinstaller dot com so we can investigate them?

Regards,
Cosmin

[ssearles]

Sure thing, just need to get a log for you... do you want the ICE validations too or just the core build log?