We recently have been experiencing an issue when loading the ServerRelativePath property of the Web object. This was previously working yesterday and for the last 4+ years but suddenly has stopped.

This seems like it's working in our SharePoint instances now! An update must be rolling out

Hi @ AdamMurchison-0306 , Since we can't reproduce your situation, we need to narrow down the problem and try some things. It's possible that a recent update or patch to the SharePoint environment introduced a change in how certain properties or methods behave. Check the version of SharePoint you're running and whether any recent updates were applied. Verify that your application or user context has the correct permissions. A change in user permissions or roles could prevent the ServerRelativePath property from being accessed correctly. If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment" . Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hi @ AdamMurchison-0306 , Maybe the truth is as you say. This could be an update issue, and for now, we'll just have to be patient and wait for an update to fix the problem. It seems as though you've found a temporary solution to the problem. I would make a brief summary of this thread: Issue Symptom: CSOM Microsoft.SharePoint.Client.Web throws exception when loading ServerRelativePath. Current status: A workaround seems to be using Web.RootFolder.ServerRelativePath . The latest version of the CSOM package https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM (16.1.25611.12000) still provides the property on the Web object. You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

CSOM Microsoft.SharePoint.Client.Web throws exception when loading ServerRelativePath

AdamMurchison-0306 80

We recently have been experiencing an issue when loading the ServerRelativePath property of the Web object.
User's image

This was previously working yesterday and for the last 4+ years but suddenly has stopped.

Xyza Xue_MSFT 29,356 Reputation points Microsoft External Staff

2025-02-12T01:45:39.9266667+00:00

Hi, Thank you for your question. We are currently looking into this issue and will give you an update as soon as possible.
E. Smith 21 Reputation points

2025-02-13T01:20:56.3266667+00:00
@Xyza Xue_MSFT :

Could you please provide an update on this breaking SharePoint Online bug?

Where else can we report this so it gets worked on by Microsoft?
Jason Wassel 5 Reputation points

2025-02-13T21:53:45.4133333+00:00

I am also seeing this issue on multiple client tenants.
AdamMurchison-0306 80 Reputation points

2025-02-16T20:09:10.2033333+00:00

Hi @Xyza Xue_MSFT ,

Thanks for getting back.

This isn't a solution considering the property is specified in the documentation, https://learn.microsoft.com/en-us/dotnet/api/microsoft.sharepoint.client.web.serverrelativepath?view=sharepoint-csom

Would be good to get an answer on why this occurred as this caused significant impact to our business and customers.

We need some certainty and confidence around this, we also need to be assured other properties will continue to work as we rely on this and the documentation to be accurate.

3 answers

AdamMurchison-0306 80 Reputation points

2025-03-03T20:09:51.43+00:00

This seems like it's working in our SharePoint instances now! An update must be rolling out
Please sign in to rate this answer.

2 people found this answer helpful.
Felix Heinicke 5 Reputation points

2025-03-06T09:35:36.7033333+00:00

Can confirm that server version 16.0.25812.12010 and up has the bug fixed.

I was notified today by MS support in my support ticket that the product team deployed a fix for the issue.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Xyza Xue_MSFT 29,356 Reputation points Microsoft External Staff

2025-02-12T05:49:00.7+00:00
Hi @AdamMurchison-0306 ,

Since we can't reproduce your situation, we need to narrow down the problem and try some things.

It's possible that a recent update or patch to the SharePoint environment introduced a change in how certain properties or methods behave. Check the version of SharePoint you're running and whether any recent updates were applied.

Verify that your application or user context has the correct permissions. A change in user permissions or roles could prevent the ServerRelativePath property from being accessed correctly.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

1 person found this answer helpful.
Zink, Florian 20 Reputation points

2025-02-12T06:47:58.97+00:00

It looks like that there is a SharePoint update rolling out which causes this issue to appear on more and more tenants. A few days ago we saw errors for one tenant, the next days on another and so on. @Xyza Xue_MSFT that you can not replicate the issue could be related to that fact, that the update might have not reached the tenant you tested on.

There is definitely an issue where SharePoint responds with the error Field or property "ServerRelativePath" does not exist. when you try to use Web.ServerRelativePath. A workaround seems to be using Web.RootFolder.ServerRelativePath. The latest version of the CSOM package https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM (16.1.25611.12000) still provides the property on the Web object, but that is not surprising because the version is from 2024-12-19 and the issue just appeared about a week ago.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Xyza Xue_MSFT 29,356 Reputation points Microsoft External Staff

2025-02-12T10:05:27.4966667+00:00

Hi @AdamMurchison-0306 ,

Maybe the truth is as you say. This could be an update issue, and for now, we'll just have to be patient and wait for an update to fix the problem. It seems as though you've found a temporary solution to the problem. I would make a brief summary of this thread:

Issue Symptom:

CSOM Microsoft.SharePoint.Client.Web throws exception when loading ServerRelativePath.

Current status:

A workaround seems to be using Web.RootFolder.ServerRelativePath. The latest version of the CSOM package https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM (16.1.25611.12000) still provides the property on the Web object.

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!
Please sign in to rate this answer.

1 person found this answer helpful.
Felix Heinicke 5 Reputation points

2025-02-12T13:25:17.6933333+00:00

I see the same issue happening on many customer tenants in a growing number.

Requesting the ServerRelativePath for Web works up to server version 16.0.25722.12007 and started breaking with version 16.0.25729.12006.

I saw the first tenants being hit on 2025-02-10, while other tenants received the update up to today.

Both File.ServerRelativePath and Folder.ServerRelativePath seem to not have the issue, but only Web.ServerRelativePath at the moment.

Philipp Eisner 15 Reputation points

2025-02-12T14:09:14.9933333+00:00

we are facing the same issues since yesterday, Web.ServerRelativePath is unable to load.

Vahe 51 Reputation points

2025-02-12T14:36:08.7033333+00:00

Same here. Many of our customers are affected now. I wonder if this was a planned change or a mistake. If it was a planned change, was there any announcement about it that we missed?

Raghunandan S 11 Reputation points

2025-02-12T15:28:38.0533333+00:00

We have observed that numerous clients of ours are affected by this issue which began following the web server update from version 16.0.25722.12007 to 16.0.25729.12006, as mentioned previously in this post.

I have the following questions:

Rollback Plans: Are you planning to roll back the recent update (update to version 16.0.25729.12006)? If yes, when can we expect this to happen? Will the rollback be permanent or you are still planning to deprecate the Web.ServerRelativePath property at some point (this will give us an idea if we should stick to the Web.ServerRelativePath property or switch to Web.RootFolder.ServerRelativePath property or find another solution)? If no, are you planning to fix the issue with the Web.ServerRelativePath property, or should we continue using the Web.RootFolder.ServerRelativePath property?

Fix Timeline: If you are planning to fix the issue with the Web.ServerRelativePath property, when can we expect this fix?

Change Planning: Was this change planned or unplanned?

Communication: Why was there no communication regarding this update?

Xyza Xue_MSFT 29,356 Reputation points Microsoft External Staff

2025-02-13T06:18:39.4466667+00:00

Hi, After my internal and external searches, I have not found any relevant information at this time. If this issue is urgent for you. For your better experience with efficient problem solving, we suggest you can create a new service request in M365 admin center as an admin, and more professional will help you.

(Microsoft 365 admin center ->> Support ->> Help & support)

Zink, Florian 20 Reputation points

2025-02-13T08:48:34.0666667+00:00

An update update about the workaround Web.RootFolder.ServerRelativePath: Accessing the property will fail with an Access Denied error if the principal (user or application) has not enough permissions on the target web. Because of that we involuntary switched to Web.ServerRelativeUrl.

Vahe 51 Reputation points

2025-02-13T08:57:18.5533333+00:00

Exactly, we've been seeing the same behavior with the workaround during our tests yesterday. Unfortunately, Web.ServerRelativeUrl is not a solution either since it doesn't support paths containing % and # characters (https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/supporting-and-in-file-and-folder-with-the-resourcepath-api).

Vahe 51 Reputation points

2025-02-13T09:41:35.4333333+00:00

We need some solution for this ASAP.

KeepLearning-6869 15 Reputation points

2025-02-14T15:08:12.11+00:00

@Xyza Xue_MSFT All our customers are seeing the same BREAKING issue!
Microsoft has removed this SPWeb.ServerRelativePath on server side with no warning whatsoever and any application using CSOM Client and the Web.ServerRelativePath property is broken!!!
The CSOM Client is still listing the Web.ServerRelativePath as a valid property: https://learn.microsoft.com/en-us/previous-versions/office/sharepoint-csom/mt807038(v=office.15)
And please, don't just update the documentation and remove Client Web.ServerRelativePath (while all worldwide applications are broken), but roll back the Server side and add back the SPWeb.ServerRelativePath to fix the mess.

AdamMurchison-0306 80 Reputation points

2025-02-16T18:59:11.78+00:00

Hi @Xyza Xue_MSFT ,

Thanks for getting back.

This isn't a solution considering the property is specified in the documentation, https://learn.microsoft.com/en-us/dotnet/api/microsoft.sharepoint.client.web.serverrelativepath?view=sharepoint-csom

Would be good to get an answer on why this occurred as this caused significant impact to our business and customers.

We need some certainty around this, we also need to be assured other properties will continue to work as we rely on this and the documentation to be accurate.

E. Smith 21 Reputation points

2025-02-22T14:11:53.1266667+00:00

@Xyza Xue_MSFT , what is the status of this? There seems to be nothing from Microsoft (last Microsoft message was from you) in this discussion for nine days.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

CSOM Microsoft.SharePoint.Client.Web throws exception when loading ServerRelativePath

3 answers

Your answer