elver
Posts: 29
Joined: Thu Oct 11, 2007 9:50 am

custom actions and vista DEP

Wed Jan 16, 2008 7:45 pm

Hi,

I use the backup_restore.vbs script available on the site. It works fine except that under vista it causes the failure of the installer because of DEP!
An article on microsoft site (link hereunder) explains that custom actions must be "compatible with DEP" without further explaination. What does it mean and why the backup_restore script is not compatible?

http://support.microsoft.com/?scid=kb%3 ... &x=14&y=13

regards
laurent

Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact:  Website

Wed Jan 16, 2008 7:59 pm

Hi,

Please note that the custom actions have been updated and they are compatible with Windows Vista. You can download the updated version from here:
http://www.advancedinstaller.com/exampl ... estore.zip
http://www.advancedinstaller.com/user-g ... le-ca.html

If you are using the updated version and you are encountering this behavior please send us the AIP to support at advancedinstaller dot com so we can investigate the problem.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

elver
Posts: 29
Joined: Thu Oct 11, 2007 9:50 am

Thu Jan 17, 2008 9:19 am

Hi,

I was already working with the latest version of the script. But I had to make a modification. In the restore function, the script uses copyFolder to restore from temporary folder to the new one. In my case, copyFolder failed because of read-only attribute on destination folder/files. So I replace copyFolder by an invocation to windows xcopy command:

Set oShell = CreateObject("WScript.Shell")
oShell.Run "XCOPY.EXE " & tempFileOrFolder & " " & dest & " /R /Y"

Like this, I have no longer failure because of read-only attribute, but the script fails (strangely, if fails time to time, but sometime it does not!) because of DEP. I guess it's due to xcopy, but I'm not sure.

What do you think of that?

regards
Laurent

Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact:  Website

Thu Jan 17, 2008 3:13 pm

Hi Laurent,

Please generate a verbose log when the script fails using the following command:

Code: Select all

msiexec /I package.msi /L*V C:\package.log
Send the log file, the AIP file and the scripts you are using to our support email address in order to investigate this issue.

Regards,
Ionut
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”