I don't know where you found that info.
It might well be necessary to have SP2 installed on an *existing* WSS
2.0 installation before you upgrade that in site to WSS 3.0, BUT it is
perfectly possible (and normal) to install WSS 3.0 without any copy of
WSS 2.0 being on the server.
(and you did say that you installed WSS 2.0; then WSS 2.0 SP2 and then
WSS 3.0 - so it sounded as if you were installing from scratch)
Mike Walsh
Ellis wrote:
> Because WSS 3.0 required 2.0 SP2 to be present before it would install.
>
> "Mike Walsh" wrote:
>
>> Why did you install WSS 2.0 and then WSS 3.0 ?
>>
>> Mike Walsh
>> WSS FAQ http://www.wssfaq.com
>> no questions by e-mail please
>>
>>
>>
>> Ellis wrote:
>>> I have taken off WSS completely, installed WSS 2.0 then SP2 then WSS 3.0.
>>>
>>> Now I get the 'ConfiguratioN Failed' screen on the Config Wizard,
>>>
>>> An exception of System.ServiceProcess.TimeoutException was thrown.
>>>
>>>
>>> "Jerry Rasmussen" wrote:
>>>
>>>> I've tried the option in the past. Most things worked be we would get
>>>> odd errors now and then. If possible I would recommend uninstall and
>>>> reinstall WSS 3.0
>>>>
>>>> SSA wrote:
>>>>> Have you tried the stsadm renameserver option?
>>>>>
>>>>> http://technet2.microsoft.com/Office....mspx?mfr=true
>>>>>
>>>>> "Ellis" wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am running WSS 3.0 on SBS 2003.
>>>>>>
>>>>>> I have renamed the server to prepare for it entering the network - renamed
>>>>>> it and SharePoint has stopped with SQL errors.
>>>>>>
>>>>>> It all still seems to point to the old name, how do I update all the
>>>>>> SharePoint settings and SQL settings to use the new name??
>>>>>>
>>>>>> thanks for your help