![]() |
|
|
#11 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
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 |
|
|
|
#12 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
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. > >>> > >>> > >>> "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 > |
|
|
|
#13 |
|
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. >>>>> >>>>> |
|
|
|
#14 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
I have taken off WSS 2.0, that went fine. Installed WSS 3.0, that went fine.
Running the Config Wizard I get the following error: Failed to start the database service MSSQL$Microsoft##SSEE. Repair this product using Add / Remove Programs. There is nothing in Add / Remove Programs!! Any ideas?? Many Thanks "Jerry Rasmussen" wrote: > 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. > >>>>> > >>>>> > |
|
|
|
#15 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
Hoping I beat Jerry ...
When removing WSS 2.0 you also need to remove the built-in WMSDE that comes with it. (Ditto WSS 3.0 and WID) Now maybe Jerry can tell you how ![]() Mike Walsh Ellis wrote: > I have taken off WSS 2.0, that went fine. Installed WSS 3.0, that went fine. > > Running the Config Wizard I get the following error: > > Failed to start the database service MSSQL$Microsoft##SSEE. Repair this > product using Add / Remove Programs. > > There is nothing in Add / Remove Programs!! Any ideas?? > > Many Thanks > > "Jerry Rasmussen" wrote: > >> 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. >>>>>>> >>>>>>> |
|
|
|
#16 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
How do I remove Microsoft##SSEE ?
I have tried this command: psconfig -cmd configdb -create -database <databasename> But I get 'Failed to start database service MSSQL$Microsoft##SSEE' Thanks "Mike Walsh" wrote: > Hoping I beat Jerry ... > > When removing WSS 2.0 you also need to remove the built-in WMSDE that > comes with it. (Ditto WSS 3.0 and WID) > > Now maybe Jerry can tell you how ![]() > > Mike Walsh > > > Ellis wrote: > > I have taken off WSS 2.0, that went fine. Installed WSS 3.0, that went fine. > > > > Running the Config Wizard I get the following error: > > > > Failed to start the database service MSSQL$Microsoft##SSEE. Repair this > > product using Add / Remove Programs. > > > > There is nothing in Add / Remove Programs!! Any ideas?? > > > > Many Thanks > > > > "Jerry Rasmussen" wrote: > > > >> 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. > >>>>>>> > >>>>>>> > |
|
|
|
#17 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
How do I remove Microsoft##SSEE ?
I have tried this command: psconfig -cmd configdb -create -database <databasename> But I get 'Failed to start database service MSSQL$Microsoft##SSEE' Thanks "Mike Walsh" wrote: > Hoping I beat Jerry ... > > When removing WSS 2.0 you also need to remove the built-in WMSDE that > comes with it. (Ditto WSS 3.0 and WID) > > Now maybe Jerry can tell you how ![]() > > Mike Walsh > > > Ellis wrote: > > I have taken off WSS 2.0, that went fine. Installed WSS 3.0, that went fine. > > > > Running the Config Wizard I get the following error: > > > > Failed to start the database service MSSQL$Microsoft##SSEE. Repair this > > product using Add / Remove Programs. > > > > There is nothing in Add / Remove Programs!! Any ideas?? > > > > Many Thanks > > > > "Jerry Rasmussen" wrote: > > > >> 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. > >>>>>>> > >>>>>>> > |
|
|
|
#18 |
|
Guest
Posts: n/a
|
Re: Renamed Server - SharePoint stopped
Ellis, while i certainly don't mind lending a hand i,t is a reasonable
expectation that you will do some work on your own. I could give the answer but in stead I will give you the Google query that I used and let you find the answer. Query "how to remove Microsoft##SSEE" with out quotes. Ellis wrote: > How do I remove Microsoft##SSEE ? > > I have tried this command: > > psconfig -cmd configdb -create -database <databasename> > > But I get 'Failed to start database service MSSQL$Microsoft##SSEE' > > Thanks > > "Mike Walsh" wrote: > >> Hoping I beat Jerry ... >> >> When removing WSS 2.0 you also need to remove the built-in WMSDE that >> comes with it. (Ditto WSS 3.0 and WID) >> >> Now maybe Jerry can tell you how ![]() >> >> Mike Walsh >> >> >> Ellis wrote: >>> I have taken off WSS 2.0, that went fine. Installed WSS 3.0, that went fine. >>> >>> Running the Config Wizard I get the following error: >>> >>> Failed to start the database service MSSQL$Microsoft##SSEE. Repair this >>> product using Add / Remove Programs. >>> >>> There is nothing in Add / Remove Programs!! Any ideas?? >>> >>> Many Thanks >>> >>> "Jerry Rasmussen" wrote: >>> >>>> 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. >>>>>>>>> >>>>>>>>> |
|
|
|
#19 |
|
Newbie
Join Date: Feb 2008
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Rep Power: 0
![]() |
Re: Renamed Server - SharePoint stopped
I was searching google for some other reasons and stumbled across this post.
It's one thing to rename a server with WSS on it but you said you were running on an SBS server. Was it already installed and already a Domain COntroller with exchange running? If so you must be having some serious problems. that is totally unsupported. The only supported way to install WSS V 3 on SBS is to do a fresh side-by-side install of WSS V 3 or you will torch the SBS admin console. |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|