Accessing the Multiterm Online login page, the following error message is displayed:
 

HTTP Status 500 – Internal Server Error
Type Exception Report

Message /WEB-INF/views/jsp/home/selectTermbase.jsp (line: [87], column: [8]) [${termbase.default}] contains invalid expression(s): 
[javax.el.ELException: Failed to parse the expression [${termbase.default}]]

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

org.apache.jasper.JasperException: /WEB-INF/views/jsp/home/selectTermbase.jsp (line: [87], column: [8]) [${termbase.default}] 
contains invalid expression(s): [javax.el.ELException: Failed to parse the expression [${termbase.default}]]
	org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:41)
	org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:292)
	org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:98)
	org.apache.jasper.compiler.Validator$ValidateVisitor.getJspAttribute(Validator.java:1443)
	org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1252)
	org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:900)
	org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1558)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2437)
	org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:919)
	org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1558)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2437)
	org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:919)
	org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1558)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2437)
	org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:919)
	org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1558)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2437)
	org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:919)
	org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1558)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2437)
	org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:919)
	org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1558)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2437)
	org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2443)
	org.apache.jasper.compiler.Node$Root.accept(Node.java:471)
	org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2385)
	org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1869)
	org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:224)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:391)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:367)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:351)
	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:605)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:399)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:379)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:327)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
	org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:97)
	org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:247)
	org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:784)
	org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:621)
	com.trados.multiterm.online.web.OnlineDispatcherServlet.doService(OnlineDispatcherServlet.java:116)
	org.springframework.web.servlet.FrameworkServlet.serviceWrapper(FrameworkServlet.java:368)
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:319)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:655)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
	com.trados.multiterm.infrastructure.web.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:169)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/9.0.55

 

For the above issue to get fixed, please perform the following change on the Trados GroupShare application server:

1. Browse to the location where Apache Tomcat X.Y is installed like C:\Program Files\Apache Software Foundation\Tomcat 8.0\conf
2. Open the catalina.properties file in a text editor like Notepad++
3. Add the following  coding line in the file:

org.apache.el.parser.SKIP_IDENTIFIER_CHECK=true

4. Restart the Apache Tomcat X.Y service afterwards.
5. Accessing the Multiterm Online login link should work now.

In some Trados GroupShare/Multiterm Online environments, the skip identifier check = true setting for Java within Apache Tomcat does not have the desired effect.