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.

  • Windows SharePoint Services 2.0

  • Windows SharePoint Services 3.0

  • Microsoft SharePoint Foundation 2010

  • Microsoft SharePoint Foundation 2013

  • Microsoft SharePoint Server 2016

  • Microsoft SharePoint Server 2019

  • Microsoft SharePoint Server Subscription Edition

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 3.1.4.1:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, and Microsoft Office SharePoint Server 2007 do not support this method.

<2> Section 3.1.4.2:  Windows SharePoint Services 2.0 does not support this operation.

<3> Section 3.1.4.2:  Windows SharePoint Services creates a file that contains the result of the export operation in the server location specified in the request message. The file includes a status code indicating the success of the operation or an error code. If the export operation succeeds, this file also includes the list of the content migration package files created. The client retrieves the file when it is created and parses the file to discover the result of the operation.

<4> Section 3.1.4.2.2.1:  If the value of cabSize is less than zero, Windows SharePoint Services 3.0, SharePoint Foundation 2010, and SharePoint Foundation 2013 return a value of 1 or 7 but the server does not successfully complete the operation. The return code is not deterministic.

<5> Section 3.1.4.3:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, and Office SharePoint Server 2007 do not support this method.

<6> Section 3.1.4.4:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, and Office SharePoint Server 2007 do not support this method.

<7> Section 3.1.4.5.2.2:  SharePoint Foundation 2010, SharePoint Foundation 2013, SharePoint Server 2016 and SharePoint Server 2019 do not return the SOAP fault. A successful GetSiteTemplatesResponse with an empty TemplateList element will be returned.

<8> Section 3.1.4.5.3.2:  Windows SharePoint Services 3.0 and Office SharePoint Server 2007 do not use the values defined for FilterCategories.

<9> Section 3.1.4.6:  Windows SharePoint Services 2.0 does not support this operation.

<10> Section 3.1.4.6:  Windows SharePoint Services 3.0 and SharePoint Foundation 2010 default to a 30-minute security validation time period.

<11> Section 3.1.4.6.2.2:  The Windows SharePoint Services implementation of the security validation consists of two values separated by a comma. The first value is a security validation token also known as message digest, and the second value is a time stamp in Coordinated Universal Time (UTC) format.

The Windows SharePoint Services implementation of the digest includes validation specific to the user, site, and time period. When the client sends a page to the server, Windows SharePoint Services verifies that the security validation has not changed. This security validation expires after a configurable amount of time, causing Windows SharePoint Services validation to fail. Clients can use the Sites.GetUpdatedFormDigest operation to refresh the security validation so that validation will succeed.

<12> Section 3.1.4.7:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, and Office SharePoint Server 2007 do not support this method.

<13> Section 3.1.4.8:  Windows SharePoint Services 2.0 does not support this operation.

<14> Section 3.1.4.8:  Windows SharePoint Services creates a file that contains the result of the import operation in the server location specified in the request message. The file includes a status code indicating the success of the operation or an error code. The client retrieves the file when it’s created and parses the file to discover the result of the operation.

<15> Section 3.1.4.8.2.1:  This parameter is optional. In SharePoint Foundation 2010 and SharePoint Foundation 2013, ImportWeb returns an error if logPath is set to an empty string.

<16> Section 3.1.4.9:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, and Office SharePoint Server 2007 do not support this method.

<17> Section 3.1.4.9.2.1:  If anonymous authentication is not allowed for the subsite, the online presence information will be enabled on SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2013 Service Pack 1 (SP1).

<18> Section 3.1.4.10:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, and Office SharePoint Server 2007 do not support this method.

<19> Section 3.1.4.11:  Only SharePoint Foundation 2013 supports this method.

<20> Section 3.1.4.12:  Only SharePoint Server 2019 supports this method.