Share via

7 Appendix B: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft Office 2010 suites

  • Microsoft Office 2013

  • Microsoft Office 2016

  • Microsoft Office 2019

  • Microsoft SharePoint Workspace 2010

  • Microsoft SharePoint Foundation 2010

  • Microsoft SharePoint Foundation 2013

  • Microsoft SharePoint Server 2010

  • Microsoft SharePoint Server 2013

  • Microsoft SharePoint Server 2016

  • Microsoft SharePoint Server 2019

  • Windows 8.1 Update

  • Windows 10 operating system

  • Microsoft Office 2021

  • Microsoft SharePoint Server Subscription Edition

  • Microsoft Office LTSC 2024

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.3.2:  Attribute not supported by Microsoft SharePoint Server 2010.

<2> Section 2.2.3.2:  Attribute not supported by Office 2010.

<3> Section 2.2.3.2:  Office 2010 does not support UserAgent attribute.

<4> Section 2.2.3.2:  Office 2010 does not support UserAgentClient attribute.

<5> Section 2.2.3.2:  Office 2010 does not support UserAgentPlatform attribute.

<6> Section 2.2.3.2:  Office 2010 does not support Build attribute.

<7> Section 2.2.3.2:  Office 2010 and Office 2013 do not support ParentFolderResourceID attribute.

<8> Section 2.2.3.2:  Office 2010 and Office 2013 do not support ShouldReturnDisambiguatedFileName attribute.

<9> Section 2.2.3.2:  Office 2010 and Office 2013 do not support ResourceID attribute.

<10> Section 2.2.3.2:  Office 2010 and Office 2013 do not support UseResourceID attribute.

<11> Section 2.2.3.5:  In SharePoint Foundation 2010 and SharePoint Server 2010, the RequestToken attribute is not present if the RequestToken attribute of the corresponding Request element is an empty string.

<12> Section 2.2.3.5:  SharePoint Server 2010 will return 2 ErrorCode attributes in Response element. SharePoint Server 2013 will not return Response element.

<13> Section 2.2.3.5:  In SharePoint Foundation 2010 and SharePoint Server 2010, the ErrorCode attribute is present if the RequestToken attribute of the corresponding Request element is an empty string.

<14> Section 2.2.3.5:  The SuggestedFileName attribute is not supported by SharePoint Server 2010 and SharePoint Server 2013.

<15> Section 2.2.3.5:  The ResourceID attribute is not supported by SharePoint Server 2010 and SharePoint Server 2013.

<16> Section 2.2.3.6:  The WebUrlIsEncoded attribute is not supported by SharePoint Workspace 2010, SharePoint Foundation 2010, SharePoint Foundation 2013, SharePoint Server 2010, SharePoint Server 2013, and SharePoint Server 2016.

<17> Section 2.2.3.7:  In SharePoint Foundation 2010, SharePoint Server 2010, SharePoint Foundation 2013 and SharePoint Server 2013, the ErrorCode attribute is present if this protocol is not enabled on the protocol server.

<18> Section 2.2.4.8:  SharePoint Server 2010 and SharePoint Server 2013 do not support the ServerCorrelationId attribute.

<19> Section 2.2.5.5:  SharePoint Server 2010, SharePoint Server 2013 and SharePoint Server 2016 will never return this value to the client.

<20> Section 2.2.5.6:  SharePoint Server 2010 and SharePoint Server 2013 do not support this error code type.

<21> Section 2.2.5.6:  SharePoint Server 2016, SharePoint Server 2019 and SharePoint Server Subscription Edition do not support this error code type.

<22> Section 2.2.5.6:  SharePoint Server 2010 does not support this error code type.

<23> Section 2.2.5.14:  SharePoint Server 2010 does not support this simple type.

<24> Section 2.2.8.1:  Microsoft Word 2010 and Microsoft PowerPoint 2010 use the string "29358EC1-E813-4793-8E70-ED0344E7B73C" for the SchemaLockID attribute sent in the different subrequests of type Coauthoring, ExclusiveLock, and SchemaLock.

<25> Section 2.2.8.2:  Servers running Microsoft Office 2010 suites return a time value that is not the current time. The protocol client does not change its behavior because the protocol client uses the difference between ServerTime values, not the difference between ServerTime and the time at the client.

<26> Section 2.2.8.2:  SharePoint Server 2010 will not return CoauthStatus attribute when client tries to join the coauthoring session and the subrequest falls back to an exclusive lock subrequest.

<27> Section 2.3.1.1:  Word 2010 and PowerPoint 2010 use string "29358EC1-E813-4793-8E70-ED0344E7B73C" for the SchemaLockID attribute sent in the different subrequests of type Coauthoring, ExclusiveLock and SchemaLock.

<28> Section 2.3.1.5:  If the CoauthRequestType attribute is not provided, SharePoint Server 2010 returns an "InvalidArgument" error code as part of the SubResponseData element associated with the coauthoring subresponse; SharePoint Server 2013 and SharePoint Server 2016 return "HighLevelExceptionThrown" error code as part of the SubResponseData element associated with the coauthoring subresponse; SharePoint Server 2019 returns HTTP status code 302.

<29> Section 2.3.1.5:  Word 2010 and PowerPoint 2010 use the string "29358EC1-E813-4793-8E70-ED0344E7B73C" for the SchemaLockID attribute sent in the different subrequests of type Coauthoring, ExclusiveLock, and SchemaLock.

<30> Section 2.3.1.7:  SharePoint Server 2010 will not return CoauthStatus attribute when client tries to join the coauthoring session and the subrequest falls back to an exclusive lock subrequest.

<31> Section 2.3.1.9:   If the ExclusiveLockRequestType attribute is not provided, SharePoint Server 2010 returns an "InvalidArgument" error code as part of the SubResponseData element associated with the exclusive lock subresponse; SharePoint Server 2013 and SharePoint Server 2016 return "HighLevelExceptionThrown" error code as part of the SubResponseData element associated with the exclusive lock subresponse; SharePoint Server 2019 returns HTTP status code 302.

<32> Section 2.3.1.9:  Word 2010 and PowerPoint 2010 use the string "29358EC1-E813-4793-8E70-ED0344E7B73C" for the SchemaLockID attribute sent in the different subrequests of type Coauthoring, ExclusiveLock, and SchemaLock.

<33> Section 2.3.1.13:  If the SchemaLockRequestType attribute is not provided, SharePoint Server 2010 returns an "InvalidArgument" error code as part of the SubResponseData element associated with the schema lock subresponse; SharePoint Server 2013 and SharePoint Server 2016 return "HighLevelExceptionThrown" error code as part of the SubResponseData element associated with the schema lock subresponse; SharePoint Server 2019 returns HTTP status code 302.

<34> Section 2.3.1.13:  Word 2010 and PowerPoint 2010 use string "29358EC1-E813-4793-8E70-ED0344E7B73C" for the SchemaLockID attribute sent in the different subrequests of type Coauthoring, ExclusiveLock, and SchemaLock.

<35> Section 2.3.1.18:  Servers running Office 2010 return a time value that is not the current time. The protocol client does not change its behavior because the protocol client uses the difference between ServerTime values, not the difference between the ServerTime and the time at the client.

<36> Section 2.3.1.33:  If the FileOperation attribute is not provided, SharePoint Server 2016 returns "HighLevelExceptionThrown" error code as part of the SubResponseData element associated with the file operation subresponse; SharePoint Server 2019 returns HTTP status code 302.

<37> Section 2.3.2.6:  There is an additional authentication prefix if claim-based authentication mode is enabled. For example: " i:0#.w|contoso\user01".

<38> Section 2.3.3.1:  Servers running Office 2010 save all changes to the underlying store at the end of processing a subrequest, with the following four exceptions:

1. The subrequest is a Put Changes subrequest, as described in [MS-FSSHTTPB] section 2.2.2.1.4, and the Partial bit, as described in [MS-FSSHTTPB] section 2.2.2.1.4, of the Put Changes request is 1. In this case, servers running Office 2010 do not save changes to the underlying store. Instead, the changes are stored in a write cache.

2. Servers running Office 2010 write to an intermediate write cache while processing a subrequest if the subrequest is a Put Changes subrequest, as described in [MS-FSSHTTPB] section 2.2.2.1.4. If writing to the write cache fails, servers running Office 2010 do not save changes to the underlying store.

3. If prior to the current attempt to save changes to the underlying store, there have been from 26 through 73 consecutive failed attempts immediately preceding the current attempt, and the most recent failed attempt is within 60 minutes of the current subrequest, servers running Office 2010 do not save changes to the underlying store. Instead, the changes are stored in a write cache.

4. If prior to the current attempt to save changes to the underlying store there have been more than 73 consecutive failed attempts immediately preceding and the most recent failed attempt is within 24 hours of the current subrequest then servers running Office 2010 will not save changes to the underlying store. Instead the changes will be stored in a write cache.

<39> Section 2.3.3.1:  Attribute not supported by SharePoint Foundation 2013 and SharePoint Server 2013 in Put Changes subrequest, as described in [MS-FSSHTTPB] section 2.2.1.1.4.

<40> Section 2.3.3.2:  Attribute not supported by SharePoint Server 2013.

<41> Section 2.3.3.2:  Attribute not supported by SharePoint Server 2013.

<42> Section 2.3.3.6:  Attribute not supported by Office 2010.

<43> Section 3.1.4.3.1:  SharePoint Server 2010 will return an error code value "FileNotLockedOnServerAsCoauthDisabled", SharePoint Server 2019 and SharePoint Server Subscription Edition will return an error code value "LockNotConvertedAsCoauthDisabled", if the AllowFallbackToExclusive attribute is set to false.

<44> Section 3.1.4.3.2:  SharePoint Server 2013 and SharePoint Server 2016 will return an error code of "InvalidCoauthSession" if there are other clients present in the coauthoring session.

<45> Section 3.1.4.3.2:  SharePoint Server Subscription Edition, SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013, and SharePoint Server 2010 return an error code of "Success" if there is an exclusive lock on the file or if there is a shared lock with a different shared lock identifier and a valid coauthoring session containing more than one client. SharePoint Server Subscription Edition and SharePoint Server 2019 return an error code of "Success" if there is a shared lock with a different shared lock identifier and a coauthoring session containing one client.

<46> Section 3.1.4.3.3:  SharePoint Server 2010 will return an error code value "FileNotLockedOnServerAsCoauthDisabled", SharePoint Server 2019 and SharePoint Server Subscription Edition will return an error code value "Success".

<47> Section 3.1.4.3.6:  SharePoint Server 2010 returns an error code value set to "LockRequestFail" if there is no shared lock.

<48> Section 3.1.4.3.6:  SharePoint Server 2010 returns an error code value set to "LockRequestFail" if there is no coauthoring session for the file.

<49> Section 3.1.4.3.7:  In SharePoint Server 2010, the protocol server returns an error code value set to "InvalidCoauthSession".

<50> Section 3.1.4.4.1:  SharePoint Server 2010 will return an error code value "FileNotLockedOnServerAsCoauthDisabled", SharePoint Server 2019 and SharePoint Server Subscription Edition will return an error code value "LockNotConvertedAsCoauthDisabled", if the AllowFallbackToExclusive attribute is set to false.

<51> Section 3.1.4.4.2:  SharePoint Server 2010 will return an error code of "Success" if there are other clients present in the coauthoring session.

<52> Section 3.1.4.4.2:  SharePoint Server Subscription Edition, SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and SharePoint Server 2010 return error code "Success" if there is an exclusive lock on the file or there is a shared lock with a different shared lock identifier and valid coauthoring session with more than one clients in it. SharePoint Server Subscription Edition and SharePoint Server 2019 return an error code "Success" if there is a shared lock with a different shared lock identifier and a coauthoring session with one client in it.

<53> Section 3.1.4.4.3:  SharePoint Server 2010 will return an error code value "FileNotLockedOnServerAsCoauthDisabled", SharePoint Server 2019 and SharePoint Server Subscription Edition will return an error code value "Success".

<54> Section 3.1.4.7:  Servers running Office 2010 return a time value that is not the current time. The protocol client does not change its behavior because the protocol client uses the difference between ServerTime values, not the difference between ServerTime and the time at the client.

<55> Section 3.1.4.8:  SharePoint Server 2010 does not support this operation.

<56> Section 3.1.4.8:  Servers running Office 2013 automatically add a client to the editors table when it takes a coauthoring or schema lock—if the client protocol version is 2.2 or higher as described in section 2.2.5.10. Editors table subrequests are used by clients running Office 2013 that do not take locks on documents before editing them.

<57> Section 3.1.4.8:  Only 4 key/value pairs can be associated with an editor on servers running Office 2013.

<58> Section 3.1.4.8:  On servers running Office 2013, the editors table partition identifier is the GUID "7808F4DD-2385-49d6-B7CE-37AC-A5E4-3602", and the editors table is represented as a compressed XML fragment.

<59> Section 3.1.4.9:  SharePoint Server 2010 does not support this operation.

<60> Section 3.1.4.10:  SharePoint Server 2010 does not support this operation.

<61> Section 3.1.4.11:  SharePoint Server 2010 and SharePoint Server 2013 do not support this operation.

<62> Section 3.1.4.12:  SharePoint Server 2010 and SharePoint Server 2013 do not support this operation.

<63> Section 3.1.4.13:  SharePoint Server 2010 does not support the AmIAlone operation.

<64> Section 3.1.4.14:  SharePoint Server 2010 and SharePoint Server 2013 do not support the LockStatus operation.

<65> Section 3.1.4.15:  SharePoint Server 2010 and SharePoint Server 2013 do not support the Properties operation.