locked
SharePoint 2007 Max Url Length RRS feed

  • Question

  • Hi,

    I have SharePoint 2007 with SP3, version 12.0.0.6608 (and content DB have the same version too). The link below says the max URL length for path in SharePoint 2010 is 260 characters. I'm assuming the limits are same for SharePoint 2007 (at least that's what people said in posts related to same issues)

    http://technet.microsoft.com/en-us/library/ff919564.aspx

    However, when I try to create a site under following structure (which has URL length of about 128 characters), the creation fails

    http://server/sitecollection/loooong_uuur_one/looooooong_uuurl_two/looooooooong_url_threee/looong_url_fooour/long_url_five/long_url_six/

    the error message is

    Exception from HRESULT: 0x80040E14   at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
       at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)  
     
    Also, there are sites which have been created few years back under http://server/sitecollection/loooong_uuur_one/looooooong_uuurl_two/looooooooong_url_threee/looong_url_fooour/long_url_five/long_url_six/ and we are now unable to modify them, the error message is the same as above. However, it is possible to move the sites in site structure and modify them after that. It is also possible to create sites with short url under site http://server/sitecollection/loooong_uuur_one/looooooong_uuurl_two/looooooooong_url_threee/looong_url_fooour/long_url_five/ but immediately, after the total length reaches 128 characters, it fails.

    Is there any setting somewhere which could be changed, or why the max URL length has dropped from 260 characters to 128? Making URL shorter is not a solution, since it has worked before, and there hundreds of sites with URL longer than 128 characters.

    Tuesday, December 18, 2012 12:57 PM

All replies

  • Summary:

    THIS WORKS (path url length under 128)

    http://server/rootsite_name/subsite_one_name/subsite_two_name/subsite_three_name/subsite_four_name/subsite_five_name/subsite_six_name/site_7/

    THIS DOES NOT WORK (path url length over 128)

    http://server/rootsite_name/subsite_one_name/subsite_two_name/subsite_three_name/subsite_four_name/subsite_five_name/subsite_six_name/subsite_seven_name/

    THIS WORKS (path url length under 128)

    http://server/rootsite_name/subsite_one_name/subsite_two_name/subsite_three_name/subsite_four_name/subsite_five_name/subsite_six_long_name/

    THIS DOES NOT WORK (path url length over 128)

    http://server/rootsite_name/subsite_one_name/subsite_two_name/subsite_three_name/subsite_four_name/subsite_five_name/subsite_six_a_little_bit_longer_name/

    How can this be fixed to support the length of 260 characters like before?


    • Edited by ericmeister Tuesday, December 18, 2012 6:41 PM
    Tuesday, December 18, 2012 6:35 PM
  • Hi,

    I have a test based on your description, it works when the URL length reaches 128 character. So you need to check the error log for  more detailed information. The error log is located : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs. And also check the event viewer for other error messages about database.

    Try to add an item to a list under http://server/sitecollection/loooong_uuur_one/looooooong_uuurl_two/looooooooong_url_threee/looong_url_fooour/long_url_five/long_url_six/ to see whether you will receive the same error message.

    I have seem similar error caused by low disk space on Database Server. You can go to Sql Server management studio and check the remaining space for the content database.

    Thanks,

    Entan Ming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttnmff@microsoft.com.


    Entan Ming
    TechNet Community Support

    Wednesday, December 19, 2012 5:58 AM
    Moderator
  • Thanks for the reply Entan,

    There are plenty of space on SQL servers, and the problem is on three different environments, development, staging and production. Also, it is possible to create sites elsewhere in the site structure, but immediately when I try to create a subsite, which url length reaches 128, it produces the HRESULT: 0x80040E14 error mentioned above. The subsites which already exists unders site "long_url_six", have "Edit Page" option grayed out, and when I try to click "Show all site content", it produces the HRESULT error mentioned above. Also, I created another site structure from the beginning as well starting from the rootsite, and subsite creation worked well, until i created a site which reached url length of 128.

    The error message in the log-file says

    Windows SharePoint Services       Database  Unexpected    Unexpected query execution failure, error code 102. Additional error information from SQL Server is included below. "Incorrect syntax near 'FOR'." Query text (if available): "{?=call proc_EnumLists(?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"    

    Event viewer gives following error

    Event log message was: 'Failed to create the 'Workflow Tasks' library.'. Exception was: 'Microsoft.SharePoint.SPException: Exception from HRESULT: 0x80040E14 ---> System.Runtime.InteropServices.COMException (0x80040E14): Exception from HRESULT: 0x80040E14
       at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
       at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
       at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName)
       at Microsoft.SharePoint.SPListCollection.EnsureListsData(String strListName)
       at Microsoft.SharePoint.SPListCollection.GetListByName(String strListName, Boolean bThrowException)
       at Microsoft.SharePoint.SPListCollection.get_Item(String strListName)
       at Microsoft.SharePoint.Publishing.Internal.Store.GetListIfExists(SPListCollection lists, String listName)
       at Microsoft.SharePoint.Publishing.Internal.ProvisioningHelper.GetUniqueListTitle(SPListCollection lists, String originalTitle)
       at Microsoft.SharePoint.Publishing.Internal.ProvisioningHelper.AddList(SPListCollection lists, String urlName, String title, String description, Guid featureId, Int32 templateType, Boolean& newListCreated)
       at Microsoft.SharePoint.Publishing.Internal.ProvisioningHelper.AddList(SPListCollection lists, String urlName, String title, String description, Guid featureId, SPListTemplateType templateType, Boolean& newListCreated)
       at Microsoft.SharePoint.Publishing.Internal.ProvisioningHelper.CreateApprovalTaskList(SPListCollection lists)'

    Log Name: Application
    Source: Office SharePoint Server
    Event ID: 4965
    Level: Error
    User: N/A
    Task Category: Publishing Provisioning
    Keywords: Classic
    Computer: servername.domainname.local


    • Edited by ericmeister Wednesday, December 19, 2012 8:27 AM
    Wednesday, December 19, 2012 8:10 AM
  • Hi,

    Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support.

    Thanks,

    Entan Ming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttnmff@microsoft.com.


    Entan Ming
    TechNet Community Support

    Wednesday, December 19, 2012 9:55 AM
    Moderator
  • Hi,

    Please see this thread: http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopmentlegacy/thread/e09fc8c1-b5f4-4ac6-9bd5-3ff8ebe06190

    For a good explanation.


    Regards, Savoeurn Va Microsoft Online Community Support

    Thursday, December 20, 2012 1:16 AM
  • Thanks for the reply Savoeurn,

    What I understood from the thread, they say

    - max url length for subsite (path) is 237 characters
    - max length for a single site name is 128 characters

    Example:
    http://servername/sites/subsite1/subsite2/Pages/default.aspx

    Protocol http://
    Server Name   servername/
    Path sites/subsite1/subsite2/Pages/   Max length: 237 characters
    File default.aspx
    Site Name This is my subsite 2 Max length: 128 characters

    My problem is, that the site creation fails when max url length of path reaches 128 characters.  Also, all the existing sites which have more than 128 characters in path, have now "Edit Page" grayed out, and produce error when trying to access "Show all site content".




    • Edited by ericmeister Thursday, December 20, 2012 10:59 AM
    Thursday, December 20, 2012 10:53 AM
  • Hi,

    I know there was some changes to the product a while back but don't recall exactly which one it was where we did something with the URL length check.  I'd recommend you open a support ticket to discuss with an engineer about this to see if there is another workaround. 


    Regards, Savoeurn Va Microsoft Online Community Support


    Sunday, January 6, 2013 6:03 PM