Re: Migrate SharePoint Portal 2003 and it DB Server to another ser



I do know that both make up the solution, but wanted to include even the most
seemingly obvious details.

I first applied WSS sp3, then rebooted (per the screen request) then applied
SPS 2003 and rebooted again. I have not rebooted my SQL server.

I do have the option to uninstall from my test environment and redo it.
ALso, in my haste to type quickly, my current production environment is SQL
Server 2000 (not windows 2000)

"Mike Walsh" wrote:

You actually have a SPS 2003 installation only but never mind that.
(Saying you have "SharePoint Portal 2003, and Windows SharePoint
Services V2" is like saying you have a car and tires/tyres)

Which order did you do the two SP3 installations ?

Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please



SP Consultant wrote:
I have SharePoint Portal 2003, and Windows SharePoint Services V2. The
database runs on a separate box, on Windows 2000.

I am trying to migrate the entire solution to two new boxes. One box will
run SharePoint Portal 2003 and SharePoint Services v2, and the other box runs
SQL Server 2005 SP2.

I used http://www.sharepointtips.com/Lists/FAQ/DispForm.aspx?ID=653
as a base for refrence, and it is copied all over the web as the definitive
successful process.

I have been following the instructions in article KB894164 (moving databases
to another server) and KB917446 Installing service pack 2, which is required
for SQL server 2005)

I installed the SQL 2005 client and backward compatibility components, on
the new SharePoint Portal 2003 box.

My variation is that I have installed SharePoint Portal 2003 and SharePoint
services SP3 on both boxes. All version numbers match on all components, both
on the control panel and the virtual server views, and they all correspond
with what the KB articles say they should be, or are at a later number. (The
KB suggests using the post sr2 hot fix, but SP3 includes all of the hot
fixes.)

I continue to get the following message in my SQL Server Logs on the restore:
The database 'sitename_Site' is marked RESTORING and is in a state that does
not allow recovery to be run.

Other background:

I am backing and restoring using the SharePoint backup and restore utility.
My backup was done after applying SP3
'sitename_Site' has full recovery mode set. I don't know if that makes a
difference.
I successfully created a site on the new web server for testing, then
removed the content databases using the remove portal sites dialog from
SharePoint portal 2003 central admin (not the WSS option)

Any suggestions would be greatly appreciated.


.



Relevant Pages

  • Re: Re-installing SQL Server
    ... Yes, you can backup and restore master, model, everything... ... Wayne Snyder, MCDBA, SQL Server MVP ... I support the Professional Association of SQL Server and it's ... > I tried reinstalling sp3 twice and both time it won't go through. ...
    (microsoft.public.sqlserver.server)
  • Re: SharePoint V3 Install Error
    ... WSS FAQ:www.wssv3faq.com/wss.collutions.com ... Event Source: WindowsSharePointServices3Search ... whatever you are installing WSS as sufficient rights to the SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint V3 Install Error
    ... But it our case it had to do with Group Policies that forbid the account of ... WSS FAQ:www.wssv3faq.com/wss.collutions.com ... Event Source: WindowsSharePointServices3Search ... whatever you are installing WSS as sufficient rights to the SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • RE: WSS install locked into MSDE DB - Can not install for SQL Serv
    ... such a point is started to effect other programs (SQL Server). ... Actually we prepped our install ... WSS just didn't work. ... > end up in WMSDE by mistake. ...
    (microsoft.public.sharepoint.windowsservices)