Skip to main content

Hi,

 

I'm running a SharePoint site in compatibility mode 2013 in a SharePoint 2013 farm.

And I get an error when I try to create a smartobject from the K2 settings.

 

11042iACD38D128A351B44.png

 

13529i03B6E9F72318CAE9.png

 

Have you seen this error ?

 

My K2 version : 4.6.11

 

Regards


16670iE91C0129B48F9AFD.png
11482iF5C4BF716688F1DB.png
14569i40797D71B4FEADD4.png
10819i4CBDB03E77EADE72.png

Hello Alex,

 

Have you checked if the "Sharepoint Server Publishing" option is deactivated? This is located in Sharepoint under settings > site settings > Site Collection Features >

SharePoint Server Publishing Infrastructure. It should be deactivated. 

 

Evan

 


Why the "SharePoint Server Publishing Infrastructure" should be deactivated ?

By the way, if I deactivate this feature, I still have the issue.

 

If I try to create a smartobject with the service "SharePoint Content", it works but I have another issue :

17121iEF559584558B591B.png

16992i53E215D5CE98453C.png

 

This is the results of 'Get List items' with no parameters, it's fine :

 

12319i981EFEBDF12D00C4.png

 

16431iAAC52938A03C5753.png

 

Why this simple request does not work ?

 

Regards


Alex,

 

I had seen someone with a similar issue to your first one, (not the one with the checkboxes) and they seemed to solve their issue by disabling SharePoint Server Publishing Infrastructure and then refreshing the service instance. That doesn't seem to be the solution here though. You're just going to need to use the Sharepoint Content Service Instance, even though you are technically working in Sharepoint 2010.

 

My guess on the issue with check boxes is that it is probably related to running your sharepoint in 2010 compatibility mode. Tested this in Sharepoint 2010 and 2013 with no issues. You have tried to recreate the service instance, did it in sharepoint as well as manually in the smart object services tester tool. Sounds like a possible bug relating to compatibility mode. 

 

Probably going to want to log a support ticket with K2. 


Reply