Page History
...
Info | ||
---|---|---|
| ||
In DSpace 7, there are two main places where detailed error messages may be found. It is important to locate these detailed error messages in order to debug any issues you are seeing, as the error which displays in a User Interface error popup is usually a generic message.. (The generic error messages that appear in the User Interface do not provide enough information to debug the problem.)
Once you locate the detailed error, see the section on "Found an error message! Now what?" below. |
...
- Search the DSpace Mailing Lists to see if someone else hit this before. If so, there may be a solution waiting for you.
- If you just recently installed (or reinstalled) DSpace, check to see if this is a Common Installation Issue listed at the bottom of the Install Guide
If neither of these resulted in a solution to your error, proceed to "Reporting the error" below.
Reporting the error
There are a few ways you may choose to report this error. However, we ask that you only choose one, depending on which you prefer.
...
MAKE SURE to include the following information:
- Your environment: Operating system, version Version of DSpace (most important), operating system, version of Tomcat, Java, Node, etc.
- NOTE: on DSpace 4.x or aboveOn the backend, simply running "
./dspace version
" from the command line will provide much of this information for you.
- NOTE: on DSpace 4.x or aboveOn the backend, simply running "
- The exact steps you took to encounter the error, as this will help us in investigating the problem. Often, we need to understand how to replicate the error before we can determine what the underlying cause is.
The error stacktrace / message that you found in your log file or Browser DevTools