Back to Community Threads
1
with multiple load balanced servers, document viewer control throws "Session has expired" error
Problem reported by Vinay B R - 5/20/2017 at 1:02 AM
Resolved
Hi,
 
I am trying to use the document viewer control in my website. The control works fine on a single server but fails when i tried with 2 load balanced webservers "session has expired, the page will be refreshed in 10 seconds" message and keeps refreshing a few times till it eventually fails with "Invalid XPZ file: Zip end header data is wrong size!" error message. 
 
Server details -
Windows Server 2012 with iis8.1
Asp.Net 4.6.2 in SessionStateMode SQLServer
 
Can you please let me know what needs to be done to get the control working. 

3 Replies

Reply to Thread
0
Cem Alacayir Replied
6/3/2017 at 11:00 AM
Employee Post
FYI this is fixed in v3.1.0:
 
Added: Load balancer support. DocumentViewer can now work properly in multi-server environments or cloud (e.g. Azure) where in-memory session is not available. Session serialization is fixed to support all session modules. You still need to have a shared cache folder between multiple instances/servers.
0
Cui Yansong Replied
10/24/2018 at 3:58 AM
Hi, I still have the problem in multi-service environment, it shown the counting down popup. So, my question is how can I share the session in multi-service environment? if there is any configuration in DocumentUltimate?
0
Cem Alacayir Replied
10/24/2018 at 4:32 AM
Employee Post
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Version History of FileVistaFileVista
Version History of FileUltimateFileUltimate
Using DocumentViewer on multi-server or cloud like AzureDocumentUltimate > Troubleshooting
Cross domain, same origin issues with DocumentViewerDocumentUltimate > Troubleshooting
EULA for DocumentUltimateDocumentUltimate