Unattended install of SSAS keeps installing into c:\data despite specifying directories

Question

Unattended install of SSAS keeps installing into c:\data despite specifying directories

doodlingdba

Hall of Fame

Points: 3164
More actions
July 11, 2018 at 8:04 am

#358342

Hi all
I'm working on automating our SQL installs through unattended install via cmd line. All working well for the DB Engine and SSRS installs. When it comes to SSAS, i'm having a frustrating issue. I want to be able to install the Data, Log, Temp and Backup directories onto the I: drive, as such:
I:\<instance>\Data
I:\<instance>\Temp
I:\<instance>\Backup
I:\<instance>\Log
This is specified within my configuration.ini file. I have also tried adding as install parameters in the setup.exe command (i'm using a batch file).These are the install parameters i'm using:
/ASDATADIR
/ASLOGDIR
/ASTEMPDIR
/ASBACKUPDIR
I'm doing a similar thing for the DB Engine install so i know this should all work. But after the install runs, everything is installed in C:\Data. There was no folder called Data in the C: drive prior to the install, the install process creates it. It's not specified anywhere (config.ini etc) but just keeps defaulting to this.
Any thoughts? I'm going mad!
Thanks in advance
Doodles

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Sue_H SSC Guru Points: 90860 More actions · Answer 1

doodlingdba - Wednesday, July 11, 2018 8:04 AM
Hi all
I'm working on automating our SQL installs through unattended install via cmd line. All working well for the DB Engine and SSRS installs. When it comes to SSAS, i'm having a frustrating issue. I want to be able to install the Data, Log, Temp and Backup directories onto the I: drive, as such:
I:\<instance>\Data
I:\<instance>\Temp
I:\<instance>\Backup
I:\<instance>\Log
This is specified within my configuration.ini file. I have also tried adding as install parameters in the setup.exe command (i'm using a batch file).These are the install parameters i'm using:
/ASDATADIR
/ASLOGDIR
/ASTEMPDIR
/ASBACKUPDIR
I'm doing a similar thing for the DB Engine install so i know this should all work. But after the install runs, everything is installed in C:\Data. There was no folder called Data in the C: drive prior to the install, the install process creates it. It's not specified anywhere (config.ini etc) but just keeps defaulting to this.
Any thoughts? I'm going mad!
Thanks in advance
Doodles

Maybe try running through the install GUI, set all your parameters, check the path for the ini file, then cancel on the ready to install page and review what's in the ini file.

Sue

doodlingdba Hall of Fame Points: 3164 More actions · Answer 2

Hi Sue... thanks for the response. That's how I generated the ini - when through a GUI install. It has saved the right settings for the installation parameters so no idea why it decided to put everything into a new C:\data folder.... it's bizarre....

Sue_H SSC Guru Points: 90860 More actions · Answer 3

doodlingdba - Thursday, July 12, 2018 7:05 AM
Hi Sue... thanks for the response. That's how I generated the ini - when through a GUI install. It has saved the right settings for the installation parameters so no idea why it decided to put everything into a new C:\data folder.... it's bizarre....

That is weird...that's how I have always found issues with the unattended installs. You may know if setup.exe spawns another process or not - I don't. I would probably monitor what it is doing using Process Monitor to find whatever file, registry or whatever it is hitting to find the C:\Data. Not sure if the process setup.exe would be enough though.

Sue