I have an app - CSFB Holt
It has a netsetup.exe file that I needed to capture.

On running the netsetup.exe, it asks to browse on the network to reference the application server
I have to point it to the servername\VS7 share and click on OK
At this point, a install screen comes up and installs the app in C:\Program files\HOLT\VS7\NetSetup

On compiling and installing the app, I got the 2704 error. directory

I looked in the directory table and the error points to this line:
directory directory_parent DefaultDir
----------- ----------------- ------------
servername INSTALLDIR2 servername

The installdir2 was red.

I can understand that it is looking for installdir2, but how do I define a servername in installdir2 and what would be values in the directory_parent and default dir?

I hope, I am able to explain the question.
How would I define the servername?

It seems the application is referencing the network share during install
0 Comments   [ + ] Show 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.


If it helps:
I looked in the registry of the wsi capture and it shows:

2 keys

Dat: \\servername\share\

In the Directory table:
INSTALLDIR shows (directory) ; VS7(diretory_parent) ;
Netsetup (DefaultDir)
VS7 - points to INSTALLDIR1 (parent), VS7 (defualtdir)
INSTALLDIR1 point to ProgramFilesFolder(parent), Holt (defaultdir)
ProgramFilesFolder points to TARGETDIR (parent), Program Files(default directory)
TARGETDIR shows (directory), no parent (blank), SOURCEDIR (defaultdir)

Servername points to INSTALLDIR2 (in RED), servername (defaultdir)

INSTALLDIR2 is not defined. How do I define that? Do I need to define a rootdir?
Answered 01/12/2009 by: aek
Purple Belt

Please log in to comment
OK. Re-Learned an old lesson. It appears I was reading too much into the package.

Essentially, the package needed to call a batch file on the server. The batch file had folders and refferences to the needed Java libs.

The error that I was getting was because of the Installdir2. Installdir2 was referencing to the server location and that was missing a parent__directory entry.

Here is what I did to get over my issue:
- Manually installed the package on a test machine and copied the created shortcut to my packaging share.
- Re-captured the installation, but this time, removed any shortcuts that were getting created via my setup captured msi.
- Deleted any reference to the Installdir2 in the directory table
- I added the shortcut file in the wsi directly in the Files section
- Added an active setup command in my wsi (to re-create any HKCU regkeys for every user)
Answered 01/12/2009 by: aek
Purple Belt

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