Skip to main content
Hi Peter,

although very good your solution doesn't work because some, or all, classes used by k2 are not serializable and I get the error [quote user=3.13603.1.0, Culture=neutral, PublicKeyToken=10ba86d4fd9ffdf3 is not marked as serializable.

I was avoiding to use the solution posted by Eric because there are several apps using the same sharepoint portal, and because it isn't depent on my application. So if someone moves the application to another server/portal probably won't remember that special setting, but I think I'll give it a try.
Hi everybody,

I have a problem regarding the use of K2 Smartforms in a load balanced envrironment. I've seen a topic discussed here in this forum (http://forum.k2workflow.com/viewtopic.php?t=1218) where someone has a similar problem but in a 1 server environment.

One of the answers in that topic posted by Adam states:
In a multiple IIS server environment, session state by default is not shared between the multiple IIS machines. Therefore someone can request a smartform on one IIS server, set up their k2 connection in their ASP.net session on that IIS box. Then on their next request, they hit a different IIS box in your LB cluster, and the session state is missing, and most importantly so is the k2 connection.
This I already knew, but what makes worried is the next statement
If this is the issue, there isn't a workaround as far as I know.

Is this last statement true? I can't use Smartforms in load balanced envrionment? :shock:

I've updated recently the production servers with SP3... Does any of this recent service packs solve my problem?

My client is giving me a hard time about this, since they want the application to be deployed in a load balanced environment. I've done a workaround by deploying the application in 1 server a refering in Sharepoint that path, but my client wants the application to be deployed in the Sharepoint servers.

Thanks in advance,
Nuno Figueiredo
If session state is the only issue ASP .NET allows you to use SQL Server to store your session state.

http://idunno.org/dotNet/sessionState.aspx
http://www.eggheadcafe.com/articles/20021016.asp
http://www.ondotnet.com/pub/a/dotnet/2003/03/24/sessionstate.html
Thanks Peter

I think I'll give it a try since no better solution is posted

I was expecting Sourcecode would have solved this "problem" by now.

In my opinion the Smartform object should handle this situation... It doesn't make sense, to me, otherwise.

Thanks again,
Nuno Figueiredo
The NLB setup should allow you to define "Sticky" session states so that that the user's second request would automatically go to the server where the first request was made and thus maintain the session state/K2 connection.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings