Cumulonimbus
Cumulonimbus
As the described behavior of the customer was that it is working sometimes and sometimes not (mostly not), we came to the conclusion that it seems to be related to the persistence configuration. Therefor we enabled only one poolmember on each Loadbalancer instance and the error wad gone. Then we tried it with two poolmembers on each Loadbalancer separately to verify if the persistence breaks only on the internal or external Loadbalancer. The result was that only the internal persistence, where the "real" Sharepoint servers are balanced, was somehow not working correctly.
As already mentioned we are using default Cookie insert persistence with a Session Cookie.
The solution for this problem was to change the Session Cookie (which will only be stored in memory on the client) to a file-based Cookie, by specifying a dedicated expiration time.
Currently I still have no clear picture of this very strange behavior, but maybe someone of you can explain it to me.
Thank you!
Ciao Stefan :)