[Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 477
  • Last Modified:

Creating a Sharepoint 2010 Lab out of production

I have a Sharepoint 2010 farm which has:
2 WFE's
2 Application Servers
1 Backend SQL
3 Web Applications (Sharepoint Team Site, Mysites & BI Site)
Security = Kerberos

I am trying to create a lab environment just to test designing the Sharepoint Team Site & Mysites so built a single server with Sharepoint & SQL. Created 2 web applications for Team Site & Mysite. Backed up the content DB's from production, restored to test, changed security to Classic (not using Kerberos in lab) and attached to the 2 web apps.

I can get to the Mysite Web App but no content within the sites seem to work. When clicking on content, I get "You do not have permissions to have lists and pages within My Site." In addition, in Central Admin I see 23 site collections where there should be over 300.

I can't get to the Team Site application at all. Just get page can't be found. The attached content DB shows it has 5 site collections where it should over 30.

Is there an issue creating a lab on a single server when the original was larger or could Kerberos have something to do with it?

1 Solution
So answering your questions:

Q:vIs there an issue creating a lab on a single server when the original was larger or could Kerberos have something to do with it?

but you can't just backup and restore the content databases from one farm to the other and expect to automagically work :) .

Go to the Central administration - > application  management - > content database
delete the content database( that will remove the relationship of the SQL db with your SharePoint , it will not delete the database.)

then reattach it using the Powershell script from the sp powershell console

Mount-SPContentDatabase -Name YourDBname -DatabaseServer YourSQLServer -WebApplication http://YourWebAppName  -Updateuserexperience -ClearChangeLog

give that a shot and see if they comeback online

Best of luck

rparsons1000Author Commented:
Ahhh, I did not think about using the powershell command. This server was actually used for pre migration testing from 2007 to 2010 so I also suspect it had some issues. I went ahead and just built another server, attached the DB and all is good. I will award full points though, this is good info.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now