The Problem
I have some legacy Meeting Workspaces imported over from SharePoint 2010 that are still in use. Recently I enabled the Navigate Up button on a test site collection using this guide because users are really missing that feature. After applying the new master page to all subsites, I observed that the meeting workspace is no longer working. If I click on a meeting from a different date, a Page Not Found error is displayed on the site.
The logs:
20635 08/22/2013 15:56:05.84 w3wp.exe (0x15D0) 0x2EDC SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:https://spdevsrv:443/sites/dev1/WeeklyStatus/undefined?InstanceID=20130710&Paged=Next&p_StartTimeUTC=20130703T120000Z&View=%7bFEF87B6F%2d54D6%2d44CD%2d8055%2dFA404C0A5B50%7d) 57843b9c-4d5d-80a3-b6fd-c40b260782c1 20636 08/22/2013 15:56:05.84 w3wp.exe (0x15D0) 0x2EDC SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\user, ClaimsCount=43 57843b9c-4d5d-80a3-b6fd-c40b260782c1 20637 08/22/2013 15:56:05.85 w3wp.exe (0x15D0) 0x58E8 SharePoint Foundation General af71 Medium HTTP Request method: GET 57843b9c-4d5d-80a3-b6fd-c40b260782c1 20638 08/22/2013 15:56:05.85 w3wp.exe (0x15D0) 0x58E8 SharePoint Foundation General af75 Medium Overridden HTTP request method: GET 57843b9c-4d5d-80a3-b6fd-c40b260782c1 20639 08/22/2013 15:56:05.85 w3wp.exe (0x15D0) 0x58E8 SharePoint Foundation General af74 Medium HTTP request URL: /sites/dev1/WeeklyStatus/undefined?InstanceID=20130710&Paged=Next&p_StartTimeUTC=20130703T120000Z&View=%7bFEF87B6F%2d54D6%2d44CD%2d8055%2dFA404C0A5B50%7d 57843b9c-4d5d-80a3-b6fd-c40b260782c1 20640 08/22/2013 15:56:05.85 w3wp.exe (0x15D0) 0x58E8 SharePoint Foundation Files aise3 Medium Failure when fetching document. 0x80070002 57843b9c-4d5d-80a3-b6fd-c40b260782c1 20641 08/22/2013 15:56:05.87 w3wp.exe (0x15D0) 0x5198 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:https://spdevsrv:443/sites/dev1/WeeklyStatus/undefined?InstanceID=20130710&Paged=Next&p_StartTimeUTC=20130703T120000Z&View=%7bFEF87B6F%2d54D6%2d44CD%2d8055%2dFA404C0A5B50%7d)). Execution Time=37.2469 57843b9c-4d5d-80a3-b6fd-c40b260782c1
The Solution
You need to apply the mwsdefaultv15.master page to all Meeting Workspace sites. Since the SharePoint Server Publishing feature is not enabled (and cannot be enabled) on this type of site, you have to do the job in PowerShell.
$web = Get-SPWeb -Identity "https://spdevsrv:443/sites/dev1" $web.MasterUrl = "/sites/dev1/_catalogs/masterpage/mwsdefaultv15.master" $web.CustomMasterUrl = "/sites/dev1/_catalogs/masterpage/mwsdefaultv15.master" $web.Update() $web.Dispose()
If you have a bunch of Meeting Workspaces then the script below might come in handy. For the sake of safety please back up your Site Collection first.
$site = Get-SPSite -Identity "https://spdevsrv:443/sites/dev1"
$webs = $site.AllWebs
$CorrectMasterPage = "/_catalogs/masterpage/mwsdefaultv15.master"
foreach($web in $webs)
{
if (($web.WebTemplate -eq "MPS") -and ($web.WebTemplateId -eq 2))
{
write-host "Updating" $web.Url
$MasterPageURL = $web.ServerRelativeUrl + $CorrectMasterPage
$web.MasterUrl = $MasterPageURL
$web.CustomMasterUrl = $MasterPageURL
$web.Update()
}
$web.Dispose()
}
that works fine, so great, thx very much :-)
ReplyDelete