/build/static/layout/Breadcrumb_cap_w.png

AppDataFolder pointing to C?

I'm creating an MST for Open Text eDocs DM5.3. I'm trying to place some files in the AppData\Roaming folder, using the Property AppDataFolder.

Unfortunatley, my files end up installed at the root of C: instead of in my roaming folder.

Any idea why AppDataFolder points to C? It is supposed to point to \%userprofile%\AppData\Roaming.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367565(v=VS.85).aspx

0 Comments   [ + ] Show comments

Answers (8)

Posted by: anonymous_9363 12 years ago
Red Belt
0
What exactly does the Directory table entry you're using look like?
Posted by: whenriksen 12 years ago
Yellow Belt
0
These are the row entrys I've created in the directory table:










DIRECTORY
DIRECTORY_PARENT
DEFAULTDIR
TARGET_PATH
SOURCE_PATH

DM_OpenText
OpenText
DM
AppDataFolder\OpenText\DM
OpenText\DM

OpenText
User_Roaming
OpenText
AppDataFolder\OpenText
OpenText

Settings_DM_OpenText
DM_OpenText
Settings
AppDataFolder\OpenText\DM\Settings
OpenText\DM\Settings

User_Roaming
<null>
AppDataFolder
AppDataFolder
<null>

I browsed the msi install log and AppDataFolder is set to the expected userpath:
"Property(S): AppDataFolder = C:\Users\%UserProfile%\AppData\Roaming\"

However, the file is installing to C.
"MSI (s) (40:90) [16:07:55:495]: File: C:\OpenText\DM\Settings\SaveUIConfig.xml; To be installed; Won't patch; No existing file"
Posted by: whenriksen 12 years ago
Yellow Belt
0
Hmm... that paste pivoted when I posted the reply.
Posted by: jmaclaurin 12 years ago
Third Degree Blue Belt
0
I've seen this on corrupted user profiles. It could be a problem with a system/user environment variable. Open a cmd and enter SET to see what the environment variables are. It could also be a problem with how you are getting an environmental variable in to a value you are creating, if you happen to be doing that.
Posted by: whenriksen 12 years ago
Yellow Belt
0
I deleted the profile that I've been installing with but that did not change anything.

The SET command lists "AppData = C:\Users\[username]\AppData\Roaming , but AppDataFolder is not listed. I tried AppData in the MST, but the install failed with an undefined root property error.
Posted by: anonymous_9363 12 years ago
Red Belt
0
"Property(S): AppDataFolder = C:\Users\%UserProfile%\AppData\Roaming\"Properties listed in the log file should show resolved folders, so the problem is here. I suspect that you have it being set somewhere like this:

AppDataFolder = C:\Users\%UserProfile%\AppData\Roaming

whereas it should be like this:

AppDataFolder = [%UserProfile]AppData\Roaming

or, much better:

AppDataFolder = [%AppData]

This last resolves correctly in XP, Vista and Windows 7.
Posted by: whenriksen 12 years ago
Yellow Belt
0
To clarify, Win7 shows the AppData environment variable to be "C:\Users\whenriksen\AppData\Roaming", which is correct. Property AppDataFolder does not exist.

If I use AppData in the directory table, I receive an error indicating it is not a valid property. According to Microsoft, AppDataFolder is supposed to point to "C:\Users\whenriksen\AppData\Roaming", but is only point to "C:". When I build my directory string to add additional folders, e.g. AppDataFolder\Open Text\DM, the file is delivered to C:\Open Text\DM instead of the roaming folder.

Has anyone used AppDataFolder in the directory table to point to the \%userprofile\AppData\Roaming folder?
Posted by: jmaclaurin 12 years ago
Third Degree Blue Belt
0
I'm pretty sure that VBScab answered your question if you have a look at it again.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ