1) 'OutOfMemoryError' problem
The error is logged in WebOffice because a problem occurred in WebOffice FTS-Index (i.e. Solr) and the request could not be processed correctly.
In the Solr-Log (..\WebOffice FTS-Index\server\logs\solr.log) you will find the cause of the problem:
2018-05-30 11:30:11.462 ERROR (qtp1911006827-317) [ x:OOE] o.a.s.h.RequestHandlerBase org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
Caused by: java.lang.OutOfMemoryError: Java heap space
The current memory settings can be viewed in the Solr Web-Admin ("Dashboard" -> entry at the bottom of the list):
-Xms<xxx>m ==> initial size of the JVM’s memory heap: xxx MB
-Xmx<xxx>m ==> maximum size of the JVM’s memory heap: xxx MB
Current memory settings in Solr Web-Admin
These parameters can be set in the '..\WebOffice FTS-Index\bin\solr.in.cmd' file:
REM Increase Java Min/Max Heap as needed to support your indexing / query needs
set SOLR_JAVA_MEM=-Xms512m -Xmx1012m
Adjusting the Values for Heap Memory Settings
The default values for the memory heap are a minimum of 512 MB and a maximum of 1024 MB (that is 1 GB).
Note: Changed values become active by restarting the Windows service WebOffice FTS Index.
2) Proxy settings problem
When upgrading from WebOffice FTS-Index the connection to WebOffice FTS-Index is no longer established.
Error: No connection to the FTS-Index '%1'. Please check the configured FTS-Index address, the proxy settings and the proxy exceptions in the WebOffice application config.
The cause is an existing proxy because the WebOffice FTS-Index standalone runs on a different port (8983) than Tomcat.
Defining the exception 'localhost:8983' in the proxy settings in the Application Configuration can solve the problem.
Note: See chapter Proxy-Server for HTTP Requests for more information about the configuration of a proxy exception.