Working with multiple drives/partitions
Hello guys,
I'm having some problems with an application which needs to install database files on another partition.
All the files install into the programfiles folder (normally C:\progfiles...) and the database files are placed on a D:\ or E:\ drive. I got this working to the point where I can manually edit that drive. So far this is still working and it places the files on the drive I want it to.
The next step is to try and automate this. If there is no E:\ drive on the computer, I want the database files installed on the D:\ drive. If E:\ exists it can go on the E:\ drive.
I tried the following wise script:
This will give me an error (messagebox) if the E:\ drive doesn't exist
which works if I run the wisescript:
When I have an E:\ drive there is no error :-)
I think the problem is my property, named: DATABASE-DRIVE won't change during the install with this wisescript.
this is a piece of my logfile during installation:
Action start 14:54:52: INSTALL.
MSI (s) (AC:D4) [14:54:52:453]: Running ExecuteSequence
MSI (s) (AC:D4) [14:54:52:453]: Doing action: set_database_drive
Action 14:54:52: set_database_drive.
Action start 14:54:52: set_database_drive.
MSI (s) (AC:34) [14:54:52:453]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI6.tmp, Entrypoint: g1
MSI (s) (AC:6C) [14:54:52:453]: Generating random cookie.
MSI (s) (AC:6C) [14:54:52:468]: Created Custom Action Server with PID 1172 (0x494).
MSI (s) (AC:BC) [14:54:52:515]: Running as a service.
MSI (s) (AC:E4) [14:54:52:515]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (AC!E4) [14:54:53:765]: PROPERTY CHANGE: Modifying DATABASE-DRIVE property. Its current value is 'D:\'. Its new value: 'E:\'.
Action ended 14:54:54: set_database_drive. Return value 1.
MSI (s) (AC:D4) [14:54:54:109]: Doing action: WiseStartup
Action 14:54:54: WiseStartup.
Action start 14:54:54: WiseStartup.
The custom action is placed directly under the "normal execute immediate/deferred" sequence.
Any advice on how to solve this?
Thanks guys! :-)
I'm having some problems with an application which needs to install database files on another partition.
All the files install into the programfiles folder (normally C:\progfiles...) and the database files are placed on a D:\ or E:\ drive. I got this working to the point where I can manually edit that drive. So far this is still working and it places the files on the drive I want it to.
The next step is to try and automate this. If there is no E:\ drive on the computer, I want the database files installed on the D:\ drive. If E:\ exists it can go on the E:\ drive.
I tried the following wise script:
This will give me an error (messagebox) if the E:\ drive doesn't exist
which works if I run the wisescript:
When I have an E:\ drive there is no error :-)
I think the problem is my property, named: DATABASE-DRIVE won't change during the install with this wisescript.
this is a piece of my logfile during installation:
Action start 14:54:52: INSTALL.
MSI (s) (AC:D4) [14:54:52:453]: Running ExecuteSequence
Action 14:54:52: set_database_drive.
Action start 14:54:52: set_database_drive.
MSI (s) (AC:34) [14:54:52:453]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI6.tmp, Entrypoint: g1
MSI (s) (AC:6C) [14:54:52:453]: Generating random cookie.
MSI (s) (AC:6C) [14:54:52:468]: Created Custom Action Server with PID 1172 (0x494).
MSI (s) (AC:BC) [14:54:52:515]: Running as a service.
MSI (s) (AC:E4) [14:54:52:515]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (AC:D4) [14:54:54:109]: Doing action: WiseStartup
Action 14:54:54: WiseStartup.
Action start 14:54:54: WiseStartup.
The custom action is placed directly under the "normal execute immediate/deferred" sequence.
Any advice on how to solve this?
Thanks guys! :-)
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
tds
13 years ago
Ok, apparently this seems to work.
I'll explain how I did this for other users who might have the same problem :-)
I did this with wise package studio.
First of all you need to create a property, in my example I will use the property DATABASE-DRIVE and give it the value C:\ or whatever you prefer.
Now go to the directory table and create a new row with your Drive.
Then add a file to your root:
now go back to your directory table and alter the path of the file you just added to the root computer. Change this to your property!
when you go back to your file management you will see that the drive now exists :-)
If you want to automate this, you can alter the drives during setup with the script in my post above. This seems to work :-)
Hope this is usefull for some of you.
Greets
I'll explain how I did this for other users who might have the same problem :-)
I did this with wise package studio.
First of all you need to create a property, in my example I will use the property DATABASE-DRIVE and give it the value C:\ or whatever you prefer.
Now go to the directory table and create a new row with your Drive.
Then add a file to your root:
now go back to your directory table and alter the path of the file you just added to the root computer. Change this to your property!
when you go back to your file management you will see that the drive now exists :-)
If you want to automate this, you can alter the drives during setup with the script in my post above. This seems to work :-)
Hope this is usefull for some of you.
Greets
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.