Skip to main content


 

Symptoms


Unable to create SmartObjects for the lists and libraries from SharePoint 2013 site running in SharePoint 2010 mode using SharePoint UI. Upon click on Create button the following error message is being displayed:

VALIDATIONThe SharePoint Service V2 broker only supports SharePoint Server 2010 and 2007. Verify the version of SharePoint you?re connecting to, and if it?s SharePoint 2013, use the SharePoint broker instead.Server was unable to process request. ---andgt Requested value 'PublishingPages' was not found.
 

Diagnoses


Similar error message can be caused by SharePoint environment misconfiguration (e.g. when you have more than one similar environments and see one of them working) or use custom/third party tools to migrate SharePoint site.

Alternatively the same error can also be caused by the installation of SharePoint January 2016 CU. There is a known issue which was introduced since August 2015 CU for SharePoint 2013. As soon as you apply this or any newer update you may see above mentioned error for sites running in SP2010 mode created from Publishing Portal template. This is known issue (internal ID 633594) and coldfix for K2 4.6.11 is available via request to K2 support.

Whenever you upgrade components in your K2 environment confirm that versions you are going to use are supported/compatible with K2 and listed in K2 compatibility matrices:
http://help.k2.com/blackpearl/support-matrix
http://help.k2.com/smartforms/support-matrix

When it comes to SharePoint K2 test its releases on the latest cumulative update available during the release cycle, for both SharePoint 2010 and SharePoint 2013. In this specific case August 2015 CU for SharePoint 2013 is listed as supported for 4.6.11, but still this bug has been identified only after release it seems and you have to have coldfix in this specific scenario (K2 integration with sites running in SP2010 mode created from Publishing Portal template).
 

Resolution

Please make sure that your SharePoint environment is configured correctly and you did not use custom/third party tools to migrate affected SharePoint site. In case you have January 2016 CU or newer CU updated to your SharePoint 2013 environment and facing this issue please contact K2 support to obtain coldfix for this problem (internal ID 633594).




 
Be the first to reply!

Reply