Applies to
DocuWare on-premises. 7.7–7.14.
What to check
A full-text error may originate in Java startup, one cabinet's Solr core or the route to a dedicated search server. These need different checks, so begin with the log associated with one reproducible failure.
Practical steps
- For startup failures, check service-account access, the configured Java path and whether another process uses port 9012.
- For a search failure affecting one cabinet, compare its GUID with the corresponding Solr core and inspect the core error.
- For a separate Fulltext server, verify connectivity from the processing server and review firewall or endpoint-protection rules.
Confirm the result
Retest the same document search after the identified issue is corrected. Rebuilding a damaged core requires the source's backup and reset procedure; do not delete core folders merely because search is slow.