Skip to main content







Normal
0




false
false
false

EN-US
X-NONE
AR-SA








































































































































































Greetings,


I have a K2 BlackPearl server deployment that connects to an
old installation of SharePoint 2007 which contains some legacy systems; both
SharePoint and K2 are using SQL 2005 which is also shared with another systems, and because it is a farm implementation K2 requires Kerberos authentication. note that my solution consists of a few simple straight forward processes built over InfoPath,
with a web service connect.


the issue is that the solution respond time is extremely
slow, it takes around 30 - 60 seconds to open the Worklist, and the InfoPath sometimes
doesn’t save at the end of the process, knowing that I added a step to save the
document, the email notification should contain attachment but also it is not
working, Another odd behavior is after you instantiate the process it takes
time to show on the worklist (around 1 minute), note that the solution is
tested before and all of these behaviors didn’t use to come up.


I tried to narrow the possibilities in which the issue maybe
caused, i found out that it could be one of 2 either Kerberos or the DB, and I’m
90% sure it is Kerberos, because the DB is serving more than one application
and none of the others is facing performance issue, also the SharePoint server
and sites that is built on the environment with regular NTLM authentication is
working fine.


Thanks for helping.


OQ

Hi Omarqas,


 


Kerberos is not known for causing performance issues, without knowing the details of your environment I suspect that it has to-do with K2’s SharePoint Group Providers. See the following thread as reference: http://k2underground.com/forums/p/12752/37357.aspx#37357. My suggestion would be to open a support ticket for this, the support guys will be able to help you troubleshoot and rectify the performance issues. Feel free to post the resolution once resolved for other readers of this thread.


It will be difficult to pin point the system causing the delay without proper analysis. Please do a SQL trace when opening the worklist and check the execution times. If the issue is related to SharePoint Group providers as Renier mentioned, log a support ticket and you can get a workaround.


Reply