web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / How to change the Abso...
Customer experience | Sales, Customer Insights,...
Suggested Answer

How to change the Absolute URL of a SharePoint Site?

(3) ShareShare
ReportReport
Posted on by JenDV 181

I wanted to change the absolute URL but saving it causes an SQL timeout to expire

I also tried to deactivate it but got this error: 

pastedimage1652213820353v3.png

I have the same question (0)
  • CW-11121959-0 Profile Picture
    CW-11121959-0 51 on at
    Did you find a solution to this SQL timeout issue? I'm having the same issue with one of my SharePoint sites.
    Thanks,
    Craig
  • Suggested answer
    Daivat Vartak (v-9davar) Profile Picture
    Daivat Vartak (v-9d... 7,835 Super User 2025 Season 2 on at
    Hello JenDV,
     

    You're encountering an "SQL Server timeout expired" error when trying to change the absolute URL of a SharePoint site and also when trying to deactivate it. This strongly suggests an issue with the underlying SharePoint content database or the SQL Server that hosts it.

    Changing the absolute URL of a SharePoint site collection is a significant operation that involves updating numerous references within the content database. If this process takes too long, it can lead to SQL Server timeouts. Deactivating a site collection also involves database modifications, which can similarly time out.

    Here's a breakdown of potential causes and troubleshooting steps:

    Possible Causes for the SQL Timeout:

    • Large Site Collection: Very large site collections with a lot of content (documents, lists, libraries) can take a significant amount of time to update the URL or deactivate.

    • Database Performance Issues:

      • SQL Server Load: The SQL Server hosting your content database might be under heavy load from other applications or processes.

      • Database Fragmentation: The content database might be highly fragmented, leading to slow read/write operations.

      • Insufficient Resources: The SQL Server might have insufficient CPU, memory, or disk I/O resources.

      • Slow Storage: The storage where the database files reside might be performing poorly. 

    • Network Latency: While less likely to cause a timeout during a local database operation, significant network latency between the SharePoint server and the SQL Server could contribute.

    • Blocked Processes: Other long-running SQL Server processes might be blocking the URL change or deactivation operations.

    • Database Corruption (Less Likely but Possible): In rare cases, database corruption could lead to performance issues and timeouts.

    • Throttling (If SharePoint Online, but you mentioned on-premises): This is more relevant for SharePoint Online, but if there are unusual throttling mechanisms in place, it could theoretically contribute. However, the error message points to an SQL Server timeout.


      •  

    Troubleshooting Steps:

    1. Check SQL Server Performance:

       

      • Monitor SQL Server: Use SQL Server Management Studio (SSMS) or Performance Monitor on the SQL Server to check CPU utilization, memory usage, disk I/O, and wait statistics during the URL change or deactivation attempt. Look for high values in any of these areas.

      • Identify Blocking Processes: In SSMS, use Activity Monitor or run sp_who2 or sp_lock to identify any long-running or blocking SQL Server processes that might be interfering. Kill any non-essential blocking processes with caution.

    2. Optimize the SharePoint Content Database:

      • Defragment the Database: Use SQL Server Management Studio to analyze and defragment the indexes of your SharePoint content database. Highly fragmented indexes can significantly slow down database operations. Right-click on the database, go to Tasks > Shrink > Database, and then right-click again, go to Tasks > Index > Reorganize and Rebuild. Consider rebuilding indexes during off-peak hours.

      • Update Statistics: Ensure that the statistics on your content database are up-to-date. In SSMS, right-click on the database, go to Tasks > Update Statistics.

        •  

    3. Increase SQL Server Timeout Values (Use with Caution):

       

      • PowerShell for SharePoint: You can try increasing the command timeout values when performing SharePoint administrative operations via PowerShell. For example, when using Set-SPSite, you might be able to specify a higher timeout. However, this only masks the underlying problem if the operation is genuinely taking too long due to performance issues.

      • Web Application Timeout: Check the timeout settings for your SharePoint web application in IIS. While this is more related to user sessions, very low timeouts could potentially interfere with long-running administrative tasks.

    4. Perform the Operation During Off-Peak Hours: Schedule the URL change or deactivation for a time when the SQL Server and SharePoint environment are under less load (e.g., late at night or on a weekend).

    5. Reduce the Scope (If Possible): If you're dealing with a very large site collection, consider if there's any way to break down the operation or if the entire site collection needs its URL changed at once. (This might not be feasible depending on your requirements).

    6. Check SharePoint Health Analyzer: Review the SharePoint Health Analyzer rules for any warnings or errors related to database performance or site collection health.

    7. Verify Sufficient Resources: Ensure your SQL Server has adequate CPU, memory, and disk I/O resources to handle the database operations. If necessary, consider upgrading the server or optimizing resource allocation.

    8. Examine SQL Server Error Logs: Check the SQL Server error logs for any specific errors or warnings that might provide more insight into the timeouts.

    9. Test in a Staging Environment: If you have a staging or test environment that mirrors your production environment, try performing the URL change or deactivation there first to identify potential issues without impacting your live system.

       


      10.  

    Specific Considerations for Changing the Absolute URL:

    • Planning: Changing the absolute URL requires careful planning as it can impact existing links, bookmarks, and integrations. Ensure you have a comprehensive plan for updating these after the change.

    • DNS Records: You'll likely need to update DNS records to reflect the new URL.

    • Alternate Access Mappings (AAM): Ensure your Alternate Access Mappings are correctly configured for the new URL.


      •  

    Specific Considerations for Deactivation:

    • Impact on Users: Understand the impact of deactivating the site collection on users who might be accessing it.

    • Backup: Always perform a full backup of your SharePoint environment and content database before attempting significant operations like URL changes or deactivations.


      •  

    In summary, the SQL timeout error indicates a performance issue preventing the completion of the URL change or deactivation. Focus on investigating and resolving potential SQL Server and database performance bottlenecks. Start with monitoring SQL Server performance during the operation and optimizing the content database. Perform these actions during off-peak hours and consider testing in a staging environment first. If the issue persists, you might need to involve your database administrator or Microsoft support for further assistance in diagnosing and resolving the underlying performance problems.

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,538 Super User 2025 Season 2 on at
    Good morning, afternoon, or evening depending on your location!
     
    The error you're encountering suggests that the process of changing the absolute URL of your SharePoint site is being blocked due to an SQL timeout. This can happen when the operation takes too long to complete, often due to the size of the site or the number of dependencies involved.
    1. Check for Active Connections:
      • Ensure there are no active connections or ongoing operations on the site. This can help reduce the load during the URL change process.
    2. Increase SQL Timeout Settings:
      • If you have access to the SQL Server, consider increasing the timeout settings temporarily to allow the operation to complete. However, this should be done cautiously and ideally with the help of a database administrator.
    3. Use PowerShell for URL Changes:
      • PowerShell can be a more efficient way to change the URL of a SharePoint site. Use the Set-SPSiteUrl cmdlet to update the URL. For example:
        Set-SPSiteUrl -Identity "        http://oldurl" -Url "http://newurl"
      • Ensure you have the necessary permissions to execute this command.
    4. Deactivate Features Carefully:
      • If deactivating features is necessary, ensure that all dependent features and services are stopped or disabled to avoid conflicts.
    5. Check for Custom Solutions or Integrations:
      • Custom solutions or third-party integrations might be causing the timeout. Review and temporarily disable any customizations before attempting the change.
    6. Consult SharePoint Logs:
      • Review the SharePoint ULS logs and SQL Server logs for more details about the timeout error. This can help identify specific bottlenecks.
    Hope this helps some!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Pallavi Phade Profile Picture

Pallavi Phade 98

#2
Tom_Gioielli Profile Picture

Tom_Gioielli 60 Super User 2025 Season 2

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 43 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans