8 Appendix C: 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 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 2.2.4:  This type is available only in SharePoint Foundation 2013.

<2> Section 2.2.4:  This type is available only in SharePoint Foundation 2013.

<3> Section 2.2.4.8:  This attribute is only available in SharePoint Foundation 2013.

<4> Section 2.2.4.12:  This type is available only in SharePoint Foundation 2013.

<5> Section 2.2.4.14:  Windows SharePoint Services 3.0 does not support this attribute.

<6> Section 2.2.4.18:  This type is available only in SharePoint Foundation 2013.

<7> Section 2.2.4.21:  Windows SharePoint Services 3.0 does not contain the SiteSubscriptionId attribute.

<8> Section 2.2.4.21:  Personal sites are supported in Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010. They are not supported in Windows SharePoint Services 3.0 and SharePoint Foundation 2010.

<9> Section 2.2.4.22:  ID attribute is required for SharePoint Foundation 2010, but not supported by Windows SharePoint Services 3.0.

<10> Section 2.2.4.22:  Version attribute is required for SharePoint Foundation 2010, but not supported by Windows SharePoint Services 3.0.

<11> Section 2.2.4.22:  URLZone attribute is required for SharePoint Foundation 2010, but not supported by Windows SharePoint Services 3.0.

<12> Section 2.2.4.22:  URLIsHostHeader attribute is required for SharePoint Foundation 2010, but not supported by Windows SharePoint Services 3.0.

<13> Section 2.2.4.23:  Windows SharePoint Services 3.0 does not support this attribute.

<14> Section 2.2.4.25:  Windows SharePoint Services 3.0 does not support the AllowedInRoot attribute.

<15> Section 2.2.4.27:  Windows SharePoint Services 3.0 does not return the LogoURL attribute.

<16> Section 2.2.4.27:  Windows SharePoint Services 3.0 does not return the LogoDescription attribute.

<17> Section 2.2.4.27:  This attribute is available only in SharePoint Foundation 2013.

<18> Section 2.2.4.27:  This attribute is available only in SharePoint Foundation 2013.

<19> Section 3.1.3:  For this protocol, SharePoint Foundation 2010 and Windows SharePoint Services 3.0 servers use for the port with standard address location being http://root/_vti_bin/SiteData.asmx where root denotes a root URL of a site (or some subsite thereof).

<20> Section 3.1.4.2.2.2:  In SharePoint Foundation 2010, the error string for this condition is "List does not exist. The page you selected contains a list that does not exist. It may have been deleted by another user." The error code is 0x82000006.

<21> Section 3.1.4.2.2.2:  In SharePoint Foundation 2010, the error string for this condition is "Item does not exist. It may have been deleted by another user."

<22> Section 3.1.4.2.2.2:  In SharePoint Foundation 2010, the error string for this condition is "List does not exist. The page you selected contains a list that does not exist. It may have been deleted by another user." The error code is 0x82000006.

<23> Section 3.1.4.3.2.4:  In Windows SharePoint Services 3.0, if the file (attachment) is inside a list, the server will set this element to "unchanged". In SharePoint Foundation 2010, if the file (attachment) is inside a list and the change is not deleting, the server will set this element to "unchanged".

<24> Section 3.1.4.3.2.8:  SharePoint Foundation 2010 Service Pack 1 provides information about whether the site collection is present in the farm in the delete change notification. Windows SharePoint Services 3.0 and other versions of SharePoint Foundation 2010 do not provide the present in farm information in the change notification.

<25> Section 3.1.4.3.2.9:  SharePoint Foundation 2010 returns the Message element only when the change could not be properly processed. Unlike SharePoint Foundation 2010, Message will appear in GetChangesResponse even when there is no exception during change processing for Windows SharePoint Services 3.0.

<26> Section 3.1.4.3.2.9:  Message from Windows SharePoint Services 3.0 does not follow this XML schema. Instead, it is represented with a string containing tokens delimited with spaces. Below is an example of the Message value:

1;1;f9945c20-f2d4-4aea-be7e-1d89a73efe2d;634190155384170000;125328 Microsoft.SharePoint.SPChangeItem Add Exception Specified method is not supported.

The first token represents the ChangeToken attribute of the Message element. The second token represents the ChangeObject attribute of the Message element. The third token represents the ChangeType attribute. The first three tokens are required. There can be multiple additional tokens in the string after the three required tokens. They are:

•          "*RETRY ATTEMPT*": This means process the previous change over again.

•          "SiteAdminChange": This is a site admin change notification. Only present when the change is updating the site admin user.

•          "Unknown change type": The change type is unknown.

•          "Done": The change has been processed successfully.

•          "Exception": There is an exception during the change processing. Detailed exception message follows.

<27> Section 3.1.4.3.5:  Windows SharePoint Services 3.0 does not support the SequenceNumber attribute.

<28> Section 3.1.4.3.5.1:  Windows SharePoint Services 3.0 and SharePoint Foundation 2010 do not return this value for this condition.

<29> Section 3.1.4.3.5.1:  Windows SharePoint Services 3.0 does not support the UpdateSecurityScope value for the change attribute in GetChanges.

<30> Section 3.1.4.3.5.11:  SharePoint Foundation 2010 sets this value to "False".

<31> Section 3.1.4.3.5.13:  This attribute is available only in SharePoint Foundation 2013.

<32> Section 3.1.4.4.2.3.6:  This behavior applies only to SharePoint Foundation 2013.

<33> Section 3.1.4.4.5.1:  Windows SharePoint Services 3.0 and SharePoint Foundation 2010 both support UpdateSecurityScope value for the change attribute in GetChangesEx.

<34> Section 3.1.4.5.2.9:  Windows SharePoint Services 3.0 does not support the Servers element.

<35> Section 3.1.4.6:  This operation is available only in SharePoint Foundation 2013.

<36> Section 3.1.4.10.3.1:  Personal sites are supported in Office SharePoint Server 2007 and SharePoint Server 2010. They are not supported in Windows SharePoint Services 3.0 and SharePoint Foundation 2010.

<37> Section 3.1.4.11.2.2:  SharePoint Foundation 2010 returns the error message "Value cannot be null. Parameter name: strUrl".

<38> Section 3.1.4.13:  In SharePoint Foundation 2010, the string comparison is case insensitive. In Windows SharePoint Services 3.0, the string comparison is case sensitive.

<39> Section 3.1.4.13:  In SharePoint Foundation 2010, the string comparison is case insensitive. In Windows SharePoint Services 3.0, the string comparison is case sensitive.

<40> Section 3.1.4.13:  In SharePoint Foundation 2010, the string comparison is case insensitive. In Windows SharePoint Services 3.0, the string comparison is case sensitive.

<41> Section 3.1.4.13:  In SharePoint Foundation 2010, the string comparison is case insensitive. In Windows SharePoint Services 3.0, the string comparison is case sensitive.