Previous Topic: Documents Submitted to Content Database Time OutNext Topic: How do I change the location EVLs are written to?

Platform Deployment Guide › Content Services › Troubleshooting the Content Indexer › Content Indexer Fails to Initialize the Content Connector

Content Indexer Fails to Initialize the Content Connector

Symptom:

After a 'CA Data Protection Content Database' service restart, Content Indexer jobs fail to start and reports "Failed to initialize the Content Connector".

Reason:

The 'CA Data Protection Connector Framework' service has lost communication with the Content Database.

Solution:

Restart the 'CA Data Protection Connector Framework' and then the 'CA Data Protection Content Indexer' service.