My customer wants to use non-default installatin direcotries but when we get
to that page in the wizard, the first installation path field is disabled and
if you introduce any changes to other installation path you get a phony error
message prompting you to supply some setup command line parameters that don't
exist.

I found the appropriate parameters (/INSTALLSHAREDDIR and
/INSTALLSHAREDWOWDIR), supplied them at the beginning in the command line and
when we get to the appropriate page in the wizard, the field is still
disabled and the supplied parametes ignored.

any ideas about how to fix this?

Thanks!

Camilo

Did you run SP1 or any CUs before the actual cluster installation? CU1 and
all subsequent updates carry a patched install script. You still need to
apply the update after the install as the pre-install run only patches the
installation script.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Camilo" <Camilo (AT) discussions (DOT) microsoft.com> wrote

Yes we did run SP1 before trying the run the setup and the behavior is the
same.

I also ran the Windows Cleanup Utility and saw that there an internal SQL
Server Embedded instance already deployed on the server. It is installed on
C: an it seems to be required for Windows Update.

Can we remove this? Any idea?

Thanks!

Camilo