We have a SBS 03 R2 server with SQL server 2005 installed. We're attempting
to install CRM4. CRM4 required 2 things to be installed, SP2 and a cumulative
update patch 7. We've installed both of these and the installed passed this
stage. The installed now asks to have the following SQL components installed;

The word breaker for language 1033 is not installed.
The full-text component is not installed on the specified SQL server.

When i try to add these from the add/remove bit, it asks me to put the
oringinal cd in. (from the premium bit of SBS). It then does a quick check
and comes up with the following error;

- Edition Change Check (Warning) Messages
Edition Change Check

To change an existing instance of Microsoft SQL Server 2005 to a different
edition of SQL Server 2005, you must run SQL Server 2005 Setup from the
command prompt and include the SKUUPGRADE=1 parameter.


I presume this is because we've upgraded the install to SP2 and the CD is a
previous version, it does allow me to continue, But dont want to break
anything.

Could anyone provide advice on where to head with this?

Many thanks,
Nathan

"Nathan Thirlby" <Nathan Thirlby@discussions.microsoft.com> wrote in message
news:1F679773-B22E-40B5-9B7C-1585B3E7593B@microsoft.com...
> We have a SBS 03 R2 server with SQL server 2005 installed. We're
> attempting
> to install CRM4. CRM4 required 2 things to be installed, SP2 and a
> cumulative
> update patch 7. We've installed both of these and the installed passed
> this
> stage. The installed now asks to have the following SQL components
> installed;
>
> The word breaker for language 1033 is not installed.
> The full-text component is not installed on the specified SQL server.
>
> When i try to add these from the add/remove bit, it asks me to put the
> oringinal cd in. (from the premium bit of SBS). It then does a quick check
> and comes up with the following error;
>
> - Edition Change Check (Warning) Messages
> Edition Change Check
>
> To change an existing instance of Microsoft SQL Server 2005 to a different
> edition of SQL Server 2005, you must run SQL Server 2005 Setup from the
> command prompt and include the SKUUPGRADE=1 parameter.
>
>
> I presume this is because we've upgraded the install to SP2 and the CD is
> a
> previous version, it does allow me to continue, But dont want to break
> anything.
>
> Could anyone provide advice on where to head with this?
>
> Many thanks,
> Nathan
>

Hi

If this is the only application that is to run on the instance, then you may
as well go back and re-install from scratch to be ultra safe, otherwise
carry on and re-apply the service pack/patches.

John

firstly, thanks for your quick reply. I'll be honest here and say that im
pretty weak at SQL so please bare with me.

I'm just trying to add the components that the CRM installer wants, but the
sql install is newer than the sql media i have. Is there anyway around this?

Many thanks,
Nathan

"John Bell" wrote:

>
> "Nathan Thirlby" <Nathan Thirlby@discussions.microsoft.com> wrote in message
> news:1F679773-B22E-40B5-9B7C-1585B3E7593B@microsoft.com...
> > We have a SBS 03 R2 server with SQL server 2005 installed. We're
> > attempting
> > to install CRM4. CRM4 required 2 things to be installed, SP2 and a
> > cumulative
> > update patch 7. We've installed both of these and the installed passed
> > this
> > stage. The installed now asks to have the following SQL components
> > installed;
> >
> > The word breaker for language 1033 is not installed.
> > The full-text component is not installed on the specified SQL server.
> >
> > When i try to add these from the add/remove bit, it asks me to put the
> > oringinal cd in. (from the premium bit of SBS). It then does a quick check
> > and comes up with the following error;
> >
> > - Edition Change Check (Warning) Messages
> > Edition Change Check
> >
> > To change an existing instance of Microsoft SQL Server 2005 to a different
> > edition of SQL Server 2005, you must run SQL Server 2005 Setup from the
> > command prompt and include the SKUUPGRADE=1 parameter.
> >
> >
> > I presume this is because we've upgraded the install to SP2 and the CD is
> > a
> > previous version, it does allow me to continue, But dont want to break
> > anything.
> >
> > Could anyone provide advice on where to head with this?
> >
> > Many thanks,
> > Nathan
> >
>
> Hi
>
> If this is the only application that is to run on the instance, then you may
> as well go back and re-install from scratch to be ultra safe, otherwise
> carry on and re-apply the service pack/patches.
>
> John
>

"Nathan Thirlby" <NathanThirlby@discussions.microsoft.com> wrote in message
news:0A15B84A-3B8A-42A2-BF1A-55E0FE9B5847@microsoft.com...
> firstly, thanks for your quick reply. I'll be honest here and say that im
> pretty weak at SQL so please bare with me.
>
> I'm just trying to add the components that the CRM installer wants, but
> the
> sql install is newer than the sql media i have. Is there anyway around
> this?
>
> Many thanks,
> Nathan
>
Hi

If you don't have any databases installed then you may as well start again
and that will be the safest option. Even if you do have databases, but you
can easily re-create logins and jobs then it is probably easier to start
again as well. If there is alot on the system, then you could either create
a new instance or try to upgrade what is there and then re-apply the service
packs and hotfixes.

John

Sorry for the delay in replying, i've been on holiday. This is running on
SBS2003 so there's a fair bit in there already. I'll have a look at what
instances are running.

Many thanks for your .

Nathan

Hello John,

> "Nathan Thirlby" <NathanThirlby@discussions.microsoft.com> wrote in
> message news:0A15B84A-3B8A-42A2-BF1A-55E0FE9B5847@microsoft.com...
>
>> firstly, thanks for your quick reply. I'll be honest here and say
>> that im pretty weak at SQL so please bare with me.
>>
>> I'm just trying to add the components that the CRM installer wants,
>> but
>> the
>> sql install is newer than the sql media i have. Is there anyway
>> around
>> this?
>> Many thanks,
>> Nathan
> Hi
>
> If you don't have any databases installed then you may as well start
> again and that will be the safest option. Even if you do have
> databases, but you can easily re-create logins and jobs then it is
> probably easier to start again as well. If there is alot on the
> system, then you could either create a new instance or try to upgrade
> what is there and then re-apply the service packs and hotfixes.
>
> John
>