Hi there Ed,
I've found one similar thread with some suggestions - in case you haven't seen it:
We most commonly see this type of error when there are unexpected characters in the metadata. For example, including angle brackets (like < and >) in your metadata can cause rendering issues, as these are reserved characters in XML. See:
Similarly, non UTF-8 content can cause this issue, which can occur if you've copied and pasted content from a non UTF-8 source, such as an MS Word document. In the thread linked above, the issue was likely caused by the non UTF-8 "curly quotes" used in Word being copied into the description, causing transformation issues during parsing.
You said you created a test fonds - was this test fonds created in the user interface manually by typing? Did it include any reserved special characters?
Does your AtoM installation include any code customizations, such as a custom theme or other custom plugins, that might affect basic functionality?
What is the full version number of your AtoM installation, as shown in Admin > Settings > Global, or returned in the command-line when running the following?
- php symfony tools:get-version
You might also want to check the webserver logs and the atom-worker logs to see if there's any further information available. Assuming you've followed the recommended installation instructions for the latest version, try:
- sudo journalctl -f -u atom-worker
- sudo tail -f /var/log/nginx/error.log
Finally, since the error occurs so early (line 2 it sounds like), the problem may be with the EAD header. Is your AtoM instance able to connect to the internet, or is it behind a firewall? We've previously seen issues where AtoM's attempt to fetch the EAD 2002 DTD from the Library of Congress URI in the header fails when AtoM is firewalled from the internet. An older workaround that I have not personally tested is described here:
There are also similar issues being reported accessing LoC, but these typically result in a different error message (a 403 Forbidden error). We have implemented a solution for this in the upcoming AtoM 2.7 release - you can find more information in this recent forum thread:
Let us know what you find, and hopefully we can provide further suggestions and workarounds.