none
DeviceChannelMapings.aspx prevents enabling Publishing in a new site

    Question

  • I inherited an environment in which Publishing is enabled everywhere, so creating a new site template is problematic. I have created a new template based on the Blank template and then partially configured the site (with publishing not yet enabled).  I successfully create a new site with that template, but in subsequent new sites Publishing cannot be enabled.

    "The URL '_catalogs/masterpage/_DeviceChannelMappings.aspx' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.'

    Doesn't matter what I do with that file, which DOES exist in the site. Publishing cannot be enabled from the GUI. And what little I have found online has not addressed the problem.

    Any thoughts?


    David

    Friday, December 1, 2017 1:46 PM

Answers

  • Due to some intrepid troubleshooting by our Microsoft PFE, we found the problem.

    Some Visual Studio features employing templates modified the default schema associated with certain key fields (Author, Editor, owshiddenversion).

    Running a modified version of the script in this page reset the field schema and everything now works.

    https://social.technet.microsoft.com/Forums/office/en-US/3bc3d677-6678-4d63-a430-aa8251603f0b/useragent-not-available-the-url-is-invalid-when-uploading-documents?forum=sharepointadmin

    Also affected https://social.technet.microsoft.com/Forums/en-US/976d00e0-fb12-4656-8988-13cb0865cbdc/office-upload-center-in-sp2013-is-malfunctioning?forum=sharepointadmin

    David

    Thursday, February 8, 2018 6:41 PM

All replies

  • Hi David,

    Whether you can reproduce this issue when you create a new site with another default template?

    If not, make sure the custom template is configured correctly.

    You can check the ULS log based on the correlation ID to find more detailed information. ULS log is at:

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

    Besides, here are some similar posts for your reference:

    https://richardstk.com/2014/04/11/error-creating-publishing-sites-in-sharepoint-2013/

    http://www.learningsharepoint.com/2013/11/17/using-sharepoint-2013-design-package-do-not-remove-it/

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, December 4, 2017 7:17 AM
  • ULS logs don't show any errors.

    I inherited this farm, no idea if my predecessor used Design Packages or not. But there are none attached to the template I created, so why does this entry keep showing up?


    David

    Monday, December 4, 2017 7:07 PM
  • Hi David,

    Try to clear the browser cache and SharePoint configuration cache:

    https://gallery.technet.microsoft.com/office/SharePoint-2010-2013-21f55320

    If the issue exists, go to master page gallery->Library settings->Indexed columns, check if you add Version column to this list. If so, remove it and try again.

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, December 5, 2017 9:24 AM
  • Browser cache cleared - no change.

    I will have to pick my time to clear the SP config cache. Good idea.


    David

    Tuesday, December 5, 2017 3:19 PM
  • Hi David,

    Is there any update?

    If it’s feasible for your issue to clear the SharePoint configuration cache?

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, December 7, 2017 8:02 AM
  • Came in early to do that this morning. Cache cleared.

    No change as far as the issues go. Oh, well.


    David

    Thursday, December 7, 2017 1:15 PM
  • Hi David,

    Try to use PowerShell command to activate the Publishing Feature in both site collection level and site level, check if you can activate publishing feature.

    Run the SharePoint 2013 Management Shell as an administrator and refer to the command in the article below:

    http://www.sharepointdiary.com/2016/03/activate-publishing-feature-using-powershell-in-sharepoint.html

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, December 8, 2017 2:51 AM
  • I found that if I used PowerShell to activate the PublishingWeb feature, I had to use the -force argument to get it to work. But then I was unable to create pages in the Pages library, unless I downloaded a page from another location and uploaded it. And then I had to fuss with the library settings to get that uploaded page to work. So something is still amiss, even though I can find workarounds.

    David

    Friday, January 12, 2018 6:36 PM
  • Due to some intrepid troubleshooting by our Microsoft PFE, we found the problem.

    Some Visual Studio features employing templates modified the default schema associated with certain key fields (Author, Editor, owshiddenversion).

    Running a modified version of the script in this page reset the field schema and everything now works.

    https://social.technet.microsoft.com/Forums/office/en-US/3bc3d677-6678-4d63-a430-aa8251603f0b/useragent-not-available-the-url-is-invalid-when-uploading-documents?forum=sharepointadmin

    Also affected https://social.technet.microsoft.com/Forums/en-US/976d00e0-fb12-4656-8988-13cb0865cbdc/office-upload-center-in-sp2013-is-malfunctioning?forum=sharepointadmin

    David

    Thursday, February 8, 2018 6:41 PM