View Single Post
Old 28-11-2007, 07:30 PM   #13
Jerry Rasmussen
Guest
 
Posts: n/a
Re: Renamed Server - SharePoint stopped

Have you tried installing WSS 3.0 before putting WSS 2.0 on the server.
I have installed WSS 3.0 dozens of times and not once has it required
WSS 2.0. If you can ,I would uninstall WSS 2.0 one more time and try
WSS 3.0 from scratch.

Ellis wrote:
> When running WSS 3.0 download, it said WSS 2.0 SP2 must be present. I did try
> installing WSS 3.0
>
> I am now upto WSS 2.0 SP2 and getting the below error trying to run WSS 3.0
> download. Any ideas to get WSS 3.0 past this error?
>
> "Mike Walsh" wrote:
>
>> 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.
>>>>>
>>>>>

  Reply With Quote