.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Script to migrate content from one sharepoint We application to another sharepoint Web Application

Posted By:      Posted Date: October 15, 2010    Points: 0   Category :SharePoint

Hello Everybody,


I have a requirement where in I will have to move content from one web app to another web app in the same far. Well this migration process has to be automated and scheduled at midnight everyday.


My thoughts for this requirement are:

1. Have a batch script scheduled. And basically this script is gary lapointe extensions where in it will copy the content from one list to another list.


2. have a Workflow running at background (this is tedious and I am convinced by this approach)




3. Content Deployment path in central admin


Can somebody suggest me a better approach for this or if any of the above approaches are correct then let me know pros and cons of that method.


thanks in advance



View Complete Post

More Related Resource Links

Application Vs. Content Pages in SharePoint

SharePoint has two types of ASPX pages. One type is the application page, also known as a _layout page. The other type of ASPX page is a content page, also known as a site page. Each of these page types is stored in a different location in SharePoint. When developers create custom ASPX pages, they must decide on the page type.

How to develop Common Content or Application pages in Sharepoint 2010, with respect to the customiz

  I have a top level site and subsites (which might be around 10). Where as the top level site represents a common landing page and each sub site represents a client site to which user will be directed upon login. This is a PUBLISHING web site. I need to design to start with common pages across all clients and if there is a need let the client to customize the common page accroding to their need. This is a PUBLISHING site so all these common pages should have Web parts zones with authoring capabilities. What is the best way of achieving this?    

SharePoint 2010 Search Service Application: "All Content" scope contains 0 items?

I've encountered a nasty bug in our setup. Our Search Service Application manages to crawl all content just fine. However, the scopes don't work. We've got a total of 570 items currently in our crawl database. 350 of these are of class 'People', and appear in the 'People' scope. The remaining 220 items should appear in 'All Content' as part of the intra (sites, documents etc), however the 'All Content' scope reports 0 items. I've tried the following: -Creating custom scopes (still 0 items) -Recreating the Search Service Application twice -Tried different accounts as the content access account. -Ensuring that the content access accounts do have 'full read policy' -Checked the crawl log for successful content (such as sites and documents). However, despite my efforts I still get 0 items for 'All Content'.  Has anyone else encountered this problem, or do you have any recommendation for us? Currently I don't see any other option than to reinstall everything.

"Fields and Content Types for the Windows SharePoint Services Application Templates"


Installation of Server Admin "Fabulous 40" Templates -

I saw a new feature appear after the templates were installed by our farm administrator. I didn't see anything in the documentation about it, but it seems like I should activate it.

Should I activate the "Fields and Content Types for the Windows SharePoint Services Application Templates" feature?

Are there any drawbacks?

Any other words of wisdom?


Migrate an ASP.NET application to SharePoint


We have a requirement where we need to migrate an existing ASP.NET application to SharePoint(MOSS 2007). The current ASP.NET application uses different BAL and DAL layers to talk to backend systems, there around 300 dynamic pages for different kind of forms and to display data from backend, 100 static aspx pages, around 20 user contorls. It also uses the a custom build javascript library for AJAX functioanlity.

Whats should be startgies to migrate a typical ASP.NET 2.0 application to MOSS 2007 portal?

This is what I thought of:
  1. Convert all the dynamic ASPX pages to Web Parts(WPs). Should I do this or use the existing aspx pages in sharepoint, i.e. copying the exising aspx pages in _layout folder
  2. Use the same BAL and DAL components without any change. Should I write wrapper components for exisitng BAL & DAL components and use the wrapper components in SharePoint application?

    Access denied when Searc Service Application tries to crawl Sharepoint content


    I have just set up a new SP2010 environtment(3 servers: WFE, App, SQL).

    When I try to get my Search Service Application to crawl my main SP site and my MySite location, I get the following error in the crawl log:

    "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled."

    Things I have checked:
    I have ensured that the default access account has "Full Read" on the web application
    -I set up crawl rules for both sources specifying a service account that has admin access to the content on those sites
    -I logged in to the SP sites using the service account that the Service Application is using to crawl
    -I even created a brand new search service application from scratch and got the exact same results

    The only difference between this environment and my test environment, where search works just fine, is that this is the production environment and so it uses FQDN with a host header: http://portal.company.org.


Migrate Sharepoint 2007 DB to 64-bit Windows Application Error


Hi All,

I am in the process of migrating my companies MOSS environment to 64bit.

I am following the directions on the technet article here: http://technet.microsoft.com/en-us/library/dd622865(office.12).aspx

Phase 1 of the plan is to migrate the databases to their new server first.

I have followed the given instructions, and all databases are on the new server (and deleted off the old) but something in Sharepoint is still pointing to the old SQL server. On the application servers, I am getting the following windows event every few seconds:

Cannot connect to SQL Server. SOMSQL01\MOSSTEST not found. Additional error information from SQL Server is included below.

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Central Admin also says that the SQL server is the old one. I know that it is actually using the new server because the old server has been switched off and all the sites are still functioning correctly.

Central Admin also shows that the main database server is still the old one, but has the new one listed under Operations - Servers in Farm.

Trying to remove the old server using the 'Remove Server' link under Operations - Servers in Farm simply reloa

Integrating a Legacy Web Application in SharePoint

This month we will continue with the theme of deploying Microsoft's SharePoint as a company intranet by describing a method for integrating a legacy Web application inside a SharePoint site.

In many companies the intranet site is not just a home page with announcements. It houses Web applications used by many different departments. In last month's article, I built a page to search the employee table in Northwind (the sample database included in Microsoft's SQL Server). This month, I will move the Web pages used to add/remove records from the table into the SharePoint intranet.

SharePoint Application and Site Pages - Part 1 of 2

In this first part of the two part series, Steven covers the differences between Site and Application pages in SharePoint 2007, why each may be used in various circumstances, and prepares for the construction of a menu located application page. After a brief introduction he examines the concept of Site Pages and Application Pages separately in detail with supported screenshots.

SharePoint Application and Site Pages - Part 2 of 2

As the second article in a two part series, Steven examines the attributes and details of a SharePoint 2007 application page, including the construction and feature deployment of the same page based project. Since this is a WSS level objective, as opposed to MOSS, you will not need MOSS to work with the code included in this project. Windows Server 2003, WSS, and Visual Studio 2005 are all that is needed, with no additional add-ons. He provides a detailed analysis of each step involved in the creation and deployment of the project.

Integrating a Legacy Web Application in SharePoint

This month we will continue with the theme of deploying Microsoft's SharePoint as a company intranet by describing a method for integrating a legacy Web application inside a SharePoint site.

Using SharePoint Search feature in ASP.Net Application

Integrating ASP.Net application in to MOSS 2007 to utilize SharePoint Enterprise Search Feature can be done by using Business Data Search.

Resume SharePoint Services Web Application and returns code 1387 error


Hello everyone! Newbie here. I would like to ask how to start the SharePoint Services Web Application on (WSS3.0,internal database, stanalone users) without getting error 1387 ?

I would love to provide more information regarding this issue but what I got is error 1387 displayed in the browser.

I look forward to seeing you guys feedback from your expertise angle.



SharePoint 2010: Application Lifecycle Management (ALM) Resource Center

Are you looking for information about BCS? BCS enables users to read and write data from external systems-through web services, databases, and .NET assemblies.

Managing Custom Configuration Options for a SharePoint Application

Learn how to store configuration data in various ways, including inside the web.config file on front-end Web servers, by using the property bag on various Windows SharePoint Services objects, storing configuration data within SharePoint lists, and by using the hierarchical object storage.

Overview of the Fluid Application Model in SharePoint Foundation 2010

Discover how the Fluid Application Model, new in SharePoint Foundation 2010, gives you the power to add non-SharePoint applications to your Web Parts.

Video: Accessing SharePoint 2010 Data from a .NET Application

This demonstration shows how to use the client object model from a Windows Presentation Foundation application. (Length: 5:26)
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend