I am not able to install the Full Text Search component in an existing SQL
Server 2005 Standard Edition clustered instance using the instructions in
Books Online (How to: Change Components in an Existing Instance of SQL Server
2005 (Setup)).

I go to Add/Remove Programs and select the default instance (only instance),
Database Services, and Advanced and choose to install Full Text Search. I
get to a screen that says "The following components that you shose to install
are already installed on the machine. To view a report of available options
and alternatives click on Details". Clicking on Details produces the
following:

~~~~~~~~
Name: MIDASSQLVP
Reason: Your upgrade is blocked. For more information about upgrade support,
see the "Version and Edition Upgrades" and "Hardware and Software
Requirements" topics in SQL Server 2005 Setup or SQL Server 2005 Books
Online.

Build version check:
Your upgrade is blocked because the existing component is a later version
than the version you are trying to upgrade to. To modify an existing SQL
Server component, go to Add or Remove Programs in Control Panel, select the
component you would like to modify, and then click Change/Remove.

Edition check:
Your upgrade is blocked because of edition upgrade rules. For more
information about edition upgrades, see the Version and Edition Upgrades
topic in SQL Server 2005 Setup or SQL Server 2005 Books Online.
~~~~~~~~

This instance has been patched with SP2a so I wonder if the install is
choking on that.

Anyone else experience this?

Thanks.

Are you doing a remote install? I experinced that when i was tring to
install regular tools on my computer. I had to copy the setup files off the
network to my computer for it to work and reboot my computer few times for it
work.

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005


"David" wrote:

> I am not able to install the Full Text Search component in an existing SQL
> Server 2005 Standard Edition clustered instance using the instructions in
> Books Online (How to: Change Components in an Existing Instance of SQL Server
> 2005 (Setup)).
>
> I go to Add/Remove Programs and select the default instance (only instance),
> Database Services, and Advanced and choose to install Full Text Search. I
> get to a screen that says "The following components that you shose to install
> are already installed on the machine. To view a report of available options
> and alternatives click on Details". Clicking on Details produces the
> following:
>
> ~~~~~~~~
> Name: MIDASSQLVP
> Reason: Your upgrade is blocked. For more information about upgrade support,
> see the "Version and Edition Upgrades" and "Hardware and Software
> Requirements" topics in SQL Server 2005 Setup or SQL Server 2005 Books
> Online.
>
> Build version check:
> Your upgrade is blocked because the existing component is a later version
> than the version you are trying to upgrade to. To modify an existing SQL
> Server component, go to Add or Remove Programs in Control Panel, select the
> component you would like to modify, and then click Change/Remove.
>
> Edition check:
> Your upgrade is blocked because of edition upgrade rules. For more
> information about edition upgrades, see the Version and Edition Upgrades
> topic in SQL Server 2005 Setup or SQL Server 2005 Books Online.
> ~~~~~~~~
>
> This instance has been patched with SP2a so I wonder if the install is
> choking on that.
>
> Anyone else experience this?
>
> Thanks.
>
>

I copied the install files to the local disk.

I also tried running setup to install FTS from the command line, which I've
successfully done to install SSIS, and the command line setup failed with the
same results.

Thanks.

David

Sorry David, I was going to try to reproduce this. But I don't have a free
server to test this on. Question do you get any warnings in the check
before the install?

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005


"David" wrote:

> I copied the install files to the local disk.
>
> I also tried running setup to install FTS from the command line, which I've
> successfully done to install SSIS, and the command line setup failed with the
> same results.
>
> Thanks.
>
> David
>