During an excel export in client environment, I systematically get an error. This error is traced in the semarchy log file like this:
The error is the following:
An exception has been caught - status: 500 (Internal Server Error), logref: aee8c621-f169-4329-8684-21cc7b36dbdc (Message reported by logger com.semarchy.mdm.dataui.infra.jaxrs.DataUIExceptionMapper, current authenticated user: 'semadmin')
We are currently on version 5.3.9 in the client environment and using CentOS8, and I cannot reproduce this error on our local environments.
Best Answer
S
Subham Dixit
said
about 2 years ago
I think this procedure is what's missing on the client side if everything else looks the same in your environment:
Subham Dixit
During an excel export in client environment, I systematically get an error. This error is traced in the semarchy log file like this:
The error is the following:
Subham Dixit
-
xDM Compatibility with Java 17?
-
xDM on Docker
-
How to Upgrade Apache Tomcat?
-
Application Server Gives 404 Error
-
Amazon Aurora support
-
Change Prod Repository Type Without Reinstallation
-
Is It Possible to Import a V5.1.1 Data Model to V5.2.8?
-
"500 Internal Server Error" While Opening with Localhost
-
Enable Access to Azure File Storage?
-
Why am I getting Status 404 -- Not Found Error on Azure?
See all 28 topics