WSS 3.0 igration to New Server SQL and IIS- From 32bit Server 2003 and SQL 2005 to 64bit Server 2008 and SQL 2008
I have an instance where I have to move a site running IIS 6.0 on one server and SQL 2005 on another, and migrate them to 2 servers IIS running 64 bit Server 2008 and the other server running 64 bit SQL 2008. I have not been able to get this working everytime. I had followed many technet posts but nothing is specific about 32 to 64bit and Server 2003 and Server 2008. Can someone get me some detailed steps on how to do this that might be specific to 64bit transition. I had this working correctly but the only issue was that centeral website home page web parts were erroring. I can not seem to fix this issue. But there might be a step i am not completing. I followed this procedure for database move http://technet.microsoft.com/en-us/library/cc512723.aspx I also did the backup and restore method in http://technet.microsoft.com/en-us/library/cc263441.aspx . Please help this is a time sensitive issue..
February 4th, 2010 6:47am

Hi, As you said you get errors on CA sites, could you please let me know the detailed error message? For your information, the articles mentioned in your thread is the recommended steps. -lambertSincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2010 8:53am

When I am restoring the sharpoint_admin database after this i get 400 errors of bad request when i try to load the SP site and centeral admin site loads but i get errors on the main screen web parts but all other functions of the centeral site work ok. Nothing in error log or in the logs that is related to the site. It is strange. I have done this before with 32bit to 32bit and had no issues.
February 5th, 2010 4:33pm

I normally don't move over anything other than the content dbs for the various sites. Central Admin content db, SSP dbs, Search db, and Config I just use the new ones that get installed on the new farm.How complex is this setup? Normally in these types of situations I build a clean SP farm in the new environment, reconfigure SP, then move the content dbs (not system dbs) over. Seems to work every time.You can always run STSADM -o Preupgradecheck on the old server which will give you a good idea of what you'd need to move and reconfigure on the new server.Not sure how realistic that option is but thought I'd toss it out there as another option. JohnSharePoint911: SharePoint ConsultingBlog: http://www.rossonmoss.comTwitter: JohnRossJrMOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2010 4:56pm

John thanks that is correct. I was listening to the client on what should be copied over and they were incorrect. Just the content was needed. Thanks guys for the quick responses.
February 10th, 2010 9:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics