Fixing error 2704

Hello guys,

Looking at the error list at http://itninja.com/question/help-with-msi-161845 and a couple of other threads i spotted this error is to do with an invalid directory. But im having trouble working out how to fix it.

The directory i think is the problem has the error "Directory 'EJAY' is an invalid root directory. It or one of its children contains files. Only TARGETDIR or its children can have files" after i ran a validation.

It looks to me like the "EJAY" folder has an incorrect path in the MSI. The install dir is "\Program Files\Dance2005", and the "EJAY" folder in a regular install is located at "\Program Files\Dance2005\ejay\eJay".

Here is a screenshot of the the InstEd window with the error http://www.zshare.net/image/506793722f8e8009/

I thought about correcting the path for the "EJAY" folder, but im not sure how to edit that in the MSI. If anyone knows how to go about fixing this error that would be very helpful.

FYI the MSI was created with the Appdeploy packager. But i did prior to that run a capture with the Wise MSI packager and got an MSI with the same error.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: AngelD 12 years ago
Red Belt
The EJAY directory entry is pointing the parent directory to it-self (Directory_Parent) so that is why you get the error.
You need to find a valid Directory entry for the Directory_Parent column of the EJAY entry.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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