Migrated sites not showing subsites
I have a sharepoint server running on windows 2003 enterprise. The sharepoint server is version 12.0.0.4518. Everything has been running fine.We built a new sharepoint server running on Windows 2008 R2. The sharepoint server is version 12.0.0.6421To migrate a site - I used SQL 2005 to backup the database, then restored on a new SQL 2005 server.I then created a new web application on the new 2008 R2 server and, pointed at the restored database.If I bring up the site, the default page looks fine.However, if I go to http:\\sitename\subsite - I just get an error.I have deleted and restored multiple times but, just get an error. The error just says "an unexpected error occured"Does anyone have any ideas?Thanks!Steve
February 27th, 2010 5:06am

Hi Steve, AssumptionsAfter restoring the BAK to the new server you Mapped the application pool identity to the ContentDb and gave it the Role of DBO. Also, after you created the new web app and before you added the restored ContentDb, you removed the Content Db that was created when you created the WebApp... -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2010 6:58am

Ivan,have you been reading too many old-fashioned mystery books ? (:))Is there a clue in your text as to what he should have done as compared to why he might have done ?FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.
February 27th, 2010 11:14am

Mike, Dude, I know \\ I was making a joke, maybe a bad one but still; AND I know exactly what you mean, How many times have I had similar occurances.... Hey, I did have one more assumptiom lol... Steve, when you built the new SharePoint Server should I assume you installed SP2 as Part of the installation either Slipstreamed, Downloaded from technet, MSDN, VL Licensing or from a DVD? If you installed SP2 seperately did you install in the following order 1. Service Pack 2 for Windows SharePoint Services 3.0 http://www.microsoft.com/downloads/details.aspx?FamilyID=79bada82-c13f-44c1-bdc1-d0447337051b&displaylang=en 2. Service Pack 2 for Windows SharePoint Services 3.0 Language Pack (if applicable) 3. Service Pack 2 for Office SharePoint Server 2007 http://www.microsoft.com/downloads/details.aspx?familyid=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en 4. Service Pack 2 for Office SharePoint Server 2007 Language Pack (if applicable) 5. Run SharePoint Products and Technologies Configuration Wizard on one server at a time, starting with CAMike, thank you and again my apologies I gotta get some rest c ya tomorrow...-IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2010 1:11pm

No apologies needed.I have a question on the new assumption.If you have a single server, it does no harm to run the wizard after every step. It's pointless but it does no harm.So the question is, would it be bad to run the wizard after each step in a farm environment or is it just the same thing - that it's a waste of time and effort?Mike(I also knew the "giving me grief" comment wasn't particularly serious coming from you but I thought other readers might think it was so I'd better reply)FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.
February 27th, 2010 2:54pm

Mike, Ivan - Thanks for the pointers. Although I have created some sharepoint sites in the past, and have been working with servers for 30 years, Im clueless to managing sharepoint servers. It all seems like black magic some how. I unfortunately dont have the time to spend learning it to manage it better.I think Mikes steps might be the clue. I think the old server is an Office 2007 Sharepoint Server. The new one apparently is not. I will try these steps above.The other thing I thought about and is a possibility is to first start by just moving the content to a new SQL server. That would buy me some time to get the new sharepoint server running.However, when I followed a procedure I found on the web, the test site no longer works - or I missed a step.The auther of the article said,1. using the content management, remove the content database,2. Move the database to the new sql server,3. Attach the new content database using content management.When I tried that, the sharepoint content manager shows the database attached but, "Sites" = 0.How do I tell it to point the website to the new content location?Thanks for the help.Steve
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2010 10:12pm

Hi Steve,Mike, I took a break and just focused on getting a WSPBuilder VS2008 solution migrated to VS2010 and deployed to ShasrePoint 2010... I was obviously not focusing enough, though I now have Canada vs USA for the Gld in Hockey, its not too mny tasks at once I hope.The first question does it matter in a multiple server environment whether you run psconfig in between the WSS and MOSS Updates updates on each server... Iy sgouldnt the ConfigDb is already marked as Upgraded and all that your doing isd setting the appropriate permissionson the resources. My question is would it be enough to run psconfig.exe -cmd secureresources or I suppose since psconfig reads the Config db to check thats all its doing anyway...Steve, Im a little confused are you saying that the new server is not Office 2007 Sharepoint Server 2007? FYI you cannot move a ContentDb from MOSS to WSS... Also, extending the web application will not resolve anything at the moment and would add complexity... The easiest way to move SharePoint to a new server is to have both SharePoint Servers at the same patch level servers patched the same in your case either 12.0.0.4518 or 12.0.0.6341, add the new server to the farm, stop the services on the old server one at a time, and starting them on the new serverIf I move the database to a new server, create a new sharepoint site on the new IIS server and, connect it to the database, is this correct?1. Restore ContentDB2. Map User Roles3. Create WebApp (Not Extend)http://technet.microsoft.com/en-us/library/cc287954.aspx4. Remove Content Dbstsadm -o deletecontentdb -url "http://YourWebApp" -databasename YourDbNamehttp://technet.microsoft.com/en-us/library/cc262449.aspx5. Add restored Content Db to new WebAppstsadm -o addcontentdb -o "http://YourWebApp" -databasename YourRestoredDb -databaseserver YourNewDbServerNamehttp://technet.microsoft.com/en-us/library/cc288692.aspx6. IISResetThere are a few pretty cool books for someone with your experience, I have been fortunate enough to work with in one capacity or another the following folks..Bill English - SharePoint Administrators Companionhttp://www.amazon.com/Microsoft-Office-SharePoint-Administrators-Companion/dp/0735622825Mike Walsh - Sams Teach Yourself SharePoint 2007 in 24 Hours: Using Windows SharePoint Services 3.0http://www.amazon.com/Sams-Teach-Yourself-SharePoint-Hours/dp/0672330008/ref=sr_1_8?ie=UTF8&s=books&qid=1267399021&sr=1-8Mike Noel, Colin Spence - SharePoint Server 2007 Unleashedhttp://www.amazon.com/Microsoft-SharePoint-2007-Unleashed-Michael/dp/0672329476/ref=sr_1_1?ie=UTF8&s=books&qid=1267399287&sr=1-1I dont know if its relevant for you, when add the restored content db to the new web app and fat finger the name of the content db, it will appear as added and not give you an error other than 0 sites... Also, please list the steps (details) you are taking to perform create the WebApp and add the content dbCheers,-IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.
March 1st, 2010 2:51am

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

Other recent topics Other recent topics