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

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

After SharePoint 2007 upgrade to SharePoint 2010 issue with custom site(s)

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

With our 2007 site(s) we had a custom module (we developed) to swap out the application.master with our own master page which resembled the site default.master.  This worked great.

After the upgrade, out site's main pages looked fine however when navigating to the admin type pages (settings/viewlists etc.) pages the module stopped working.

1.) I have figured out something things with respect to what is going on but am still at a loss to how best resolve.  We want the layouts/admin pages to have the same master page as the main user pages.   I have read in 2010 this is now possible.  How can I achieve this?


2.) Currently, when navigating to the sites/settings page the site is using template/layouts/layoutsv3.master as the master page.  The settings.aspx page has DynamicMasterPageFile="~masterurl/default.master" .  It was my understanding that when DynamicMasterPageFile was set to default.master it would use the master page from the site.  So, with that said I am confused why it is using layoutsv3.master

any help would be appreciated



View Complete Post

More Related Resource Links

How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

Cannot crawl sharepoint site and mysite after database attach upgrade form sharepoint 2007 to 2010.

After database attach upgrade site and mysite from sharepoint 2007 to 2010 , I have full crawl and get "The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error. ( Error from SharePoint site: HttpStatusCode ServiceUnavailable The request failed with HTTP status 503: Service Unavailable. )" for mysite and get "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." for sharepoint site. The content access account for search is "db_owner" of both of site and mysite. How do I solved this problem ?

SharePoint 2007 upgrade to 2010 without UI update masterpage issue

I have a public facing site on a SharePoint 2007 farm that will be upgraded to 2010.  This site has a very customized look and feel that will not initially be updated to the 2010 UI.    I have run into one small issue with 2010's handling of legacy 2007 UIs.In SharePoint 2007,  to have a different master page for the application pages and dialog boxes we utilized an HTTP Module to switch the master page on the fly.    After migrating the SP2007 into our 2010 beta test environment the HTTP Module no longer worked properly.   I did some debugging and found out that SharePoint 2010 is returning a NULL value for MasterPageFile property on the pages in the _layouts folder.   I would have expected to see the URL pointing to the application.master page (or dialog.master).   Any ideas if this is a bug in SP2010 beta and will be fixed in RTM or is this the intended behavior.If it is the intended behavior in SP2010 how could I update my HTTP Module to allow the site to continue functioning as it did on 2007?   

Reg: Does Custom site definition created in SharePoint 2007 works in Sharepoint 2010



If one has created a custom site definition in sharepoint 2007, Once the whole site is migrated to sharePoint 2010 will that "custom site definition" created in 2007 will work without breaking in SharePoint 2010?

If No, what has to be done to make it work on 2010.






Upgrade Sharepoint 2007 Custom State Machine/Sequential workflow to SharePoint 2010



What's the path for upgrading the SharePoint 2007 Custom State Machine/Sequential workflow to SharePoint 2010 when the current SharePoint 2007 environment is upgraded to SharePoint 2010 by an inplace upgrade?

What's the typical estimate time for upgrading SP2007 custom workflow to SP2010 custom workflow?  My gut says 40 to 80 hrs or even less than that, what’s your thoughts?

FYI...I tried to upgrade the SharePoint custom workflow built using visual studio 2008 in SP2007 environment to visual studio 2010 solution/project in SP2010 environment, I got the error messages to refer the following dll's

Microsoft.SharePoint.dll and Microsoft.SharePoint.WorkflowActions.dll

Even after referring the new dlls still the workflow design doesn't show up in the canvas...still work on this to fix mean while want to know the experts insights on this.

How to add custom list entries to mysite's calendar in Sharepoint 2007 site?


I would like to know below things

(1) How to create MySite for one specific member with other or administrator's access?

(2) Scenario : Administrator have created one SP2007 site. now Administrator have created one calendar (Sample calendar). Administrator have added some entries in calendar. now one user entered in portal site ansd view the calendar and he click on MySite menu. so this sample calendar entries should enter in that user's mysite calendar. How this can be achieved?

Thanks in advance.
Regards, Praful Udade

Sharepoint 2007 - Wiki site - New Pages Not Inheriting Custom Master Page


I am working on a SP site (MOSS not WSS) which is heavily customised away from the OOTB layout. I need to create a Wiki site, which was going well - I've created a master page which displays the miniconsole (this was not visible with our customised layout), and made it the default master page for the site. This has been applied to the two standard pages that come with the Wiki site, however when a new page is created, it seems to inherit the default.master, rather than my custom master page - thus not showing the miniconsole.

When I have created a new page, I am able to use SharePoint Designer to attach my custom master page to it, which works perfectly, however this will not be a viable option going forward as end-users create their new wiki pages.

How can I get the new pages to inherit my master page when they are created?


Adding a custom control to the SharePoint 2010 Team Site Wiki Page Template ( wkpstd.aspx ) programm

Topic This is maybe my last post about the Team Site Wiki Page customization with the aim of exceeding its limitations. This time we are going to customize the unique template ( wkpstd.aspx) by replacing the control that renders the editable content by a custom one. In this post example, we will take advantage of the use of this custom control to render not editable additional contents, for instance, a header and a footer that could be the same for a specific Wiki Page Library. Of course, we are not going to really customize the template, but we are going to use a delegate control to replace the control at runtime. Here are the screen shots of the result: We can see a non editable Header and Footer on the Team Site Wiki Page In edit mode these additional contents are not rendered, but we can add new content as usual And of course, after having saved the page, the new content is rendered wtih the non editable Header and Footer. Steps required   If you look at the Team Site Wiki Page template, wkpstd.aspx, you can see the control that is rendering the editable content/ <SharePoint:EmbeddedFormField ID="WikiField" FieldName="WikiField" ControlMode="Display" runat="server" /> We are first going to create a custom EmbeddedFormField control Then, we are going to use a delegate control to replace the native EmbeddedFor

SharePoint 2010 - noticed a possible bug with regard to custom site templates.

Hi All, I'm wondering has anyone else noticed this behaviour in relation to custom site templates. I wanted to move an site A ( content included ) from site collection A to site collection B. I saved site A as a site template ( content included ) I uploaded the site template to site collection B's solution gallery. I created Site B on site collection B using this site template. unfortunately the top links to site A have been preserved causing major confusion to the users. i.e. the shared documents document library link and the tasks link both link to Site A! the links to documents within the document library on the other hand are to site B!? Is this a known issue ? Is this something that I should have expected to happen? look forward to hearing other folks experience with this functionality. thanks and regards, Counie  

Best Way to Convert MOSS 2007 Site Templates to SharePoint 2010 Templates

Ok, I just treid to do something that I didn't really think would work, but now that I've seen it fail, I get to ask the question. Is there a best practice on converting site templates built for MOSS 2007 to SharePoint 2010. We have several projects that used the Visual Studio Extensions (v1.3) and the SharePoint Solution Generator to build custom site templates and the .wsp packages. I can add and deploy the solution packages using the STSADM tool, but when I try to create a sub-site based on that template, I get an Object Not Set to an Oject Reference Error. In case anyone is wondering, it works fine in MOSS 2007. I have not tried Visual Studio 2010 yet (it's downloading in the background). I'm just wondering if anyone has run into this and what they did to fix it. TIA, John.

MOSS 2007 upgrade to Sharepoint 2010 across domains

I recently did an upgrade at a customer site. I migrated their content successfully as well as their Mysites. Their MOSS farm was situated on a domain, let's say "domain 1". Due to a merger, their domain had to change to "Domain 2". The Sharepoint 2010  farm was set up on new domain. We now need to change the existing user logins from the upgraded content db to the new domain. domain1\user to Doamin2\user.  We considered a manual process, but it is simply not a viable option. Furthermore, the migrated mysites works fine, but the problem is, the users need to login with their old login details to view the content. Which is unacceptable. The mysite content now needs to be associated with the users on the new domain. Bear in mind that the users already have logins and permissions as per the previous configuration (domain1\user) I consideredd using the stsadm migrate user command, but that could also be laborious. The other concern is the SID associated to each login. I am not sure if the -ignoresidhistory switch will help, or if this command is even usable in SP 2010. I there possibly another, more effective method to accomplish these tasks, say a Powershell script or a magic wand?   Regards,   Warren  

Upgrade from MOSS 2007 Trial to Sharepoint Server 2010

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?

MOSS 2007 to SharePoint Server 2010 Hybrid Upgrade Approach on Windows Server 2003 x64

There's some guidance circulating about upgrading to 2010 with a mix of In-Place and Database Attach upgrade methods. My Central Admin and SharePoint Web App are on a 64 bit server, but it's running on Windows server 2003 x64 and not on Windows Server 2008 or 2008 R2. SharePoint Team Blog says Server 2008 or 2008 R2 is required for SP2010. If I want to do the hybrid upgrade approach, is it possible to first upgrade the OS to Server 2008 R2 on the server where my Central Admin and SP Web App runs?  Or will this break MOSS 2007?

How to migrate sharepoint site in 2007 with custom solution package and its content to sharepoint 20

Hi Experts, Recently, my organization is planning for SharePoint 2010 upgrade. We decide to go with Database content migration as it is less impact with down time due to hardware and software requirement (64 bit) in SharePoint 2010. We have a sub-site which contains a lot of customization such as master page, custom list, web parts and a lot of content. There is also a solution was built for that sub-site as well. However, as the time past by there quite a few update and manual creating from power users which concern to me that the solution package that we have does not up to date that can be use for SharePoint 2010 upgrade. I am planning to re-package the solution for the upgrade with all the changes users made for SharePoint 2010. But the question is how do I migrate the content of existing site when we upgrade to 2010? It is also possible that they want to change the sturction of the site when migrate eg: make this new upgrade site as top site collection instead of sub-site. Another concern is what happen after I finish making re-package the solution but during the re-package period users might make more change to the existing site? I would greatly appreciate for any ideas, suggestions as well as best methodology I should take.   Thanks praneth

Creating a new site sharepoint 2010 under parent site with my custom template Programatically using

Hi, I have a parent website under which i want to create subsites on the fly using visual studio 2010. The subsites which i want to create have a common stuructre(in temrs of lists & custom). So i saved the template in sharepoint 2010,it becomes wsp and goes into soution gallery. Now how do i use this template say mytemplate.wsp,to create site in visual studio. i tried this using (SPSite site = new SPSite ("http://infml01132:5566/sites/VRND " ))             {                 using (SPWeb web = site.OpenWeb())                 {                                       SPWebTemplateCollection myTemplates = site.GetCustomWebTemplates(Convert .ToUInt32(web.Locale.LCID));                     //SPWebTemplateCollection temlates1 = site.GetCustomWebTemplates(1033);                     //SPWebTemplateCollectio

SharePoint 2007 to 2010 Upgrade AND Farm Merge


Hello all,

I'm curious to see if anyone has done this.  Currently, my environment has 3 seperate SharePoint 2007 server farms.  I'm currently evaluating SharePoint 2010 and so far like what I see.  I'm wondering though what would be the steps I would need to go through to actually upgrade and then merge them all to one SharePoint 2010 farm?  The steps I can think of are the following:

1. Make sure all 2007 farms are on the lastest (or at least similar) version

2. Upgrade each farm to SharePoint 2010

3. Create new 2010 farm

4. Copy upgraded farms' site collections to NEW 2010 farm.

OR can I do this:

1. Make sure all 2007 farms are on the same version

2. Create a copy of each current SharePoint 2007 site collection that I want

3. Create NEW 2007 Farm

4. Copy content to new farm

5. Upgrade new farm to 2010


Any and all help would be greatly appreciated, thanks!


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