Troubleshooting

I cannot identify the version of Data Hub and MarkLogic installed in my service.

Use REST APIs to return the version of Data Hub and MarkLogic installed in your service.

Workaround:
  1. In the MarkLogic Data Hub Service Dashboard, click the service name in the Service column.
  2. Create one or more service users.
  3. Use REST APIs to return summary information about your service:
    • To return the Data Hub version installed in your service, click the Curation Staging REST endpoint and enter your service user login credentials. In your browser, use the following REST API: 
       https://host-name:8010/v1/resources/mlHubversion
      Note: The mlHubversion REST API can be used for services running Data Hub 5.0.x through 5.2.x.

      For details, see Data Hub Extensions to the REST Client API.

    • To return the MarkLogic version installed in your service, click the Manage endpoint and enter your service user login credentials. In your browser, use the following REST API: 
       https://host-name:8003/manage/v2

      The value of version is the MarkLogic version number.

      For details, see GET /manage/v2.

I cannot ingest documents using MLCP or DMSDK without losing some documents.

If you use MLCP or DMSDK for ingestion during auto-scaling events, a small number of documents might fail to insert into the database. In most cases, the client automatically retries multiple times to insert the documents into the database. For additional information about the failed documents, you can view the URIs of the failed documents in the logs.

Workaround:
  • Re-ingest your documents using MLCP, DMSDK, or another client, such as Gradle or Java API.

I cannot access the Data Hub Explorer application because of a certificate error.

When accessing Data Hub Explorer, your browser will notify you that your connection might not be private.

Example:
  • NET::ERR_CERT_AUTHORITY_INVALID
Workaround:
  • In your browser, click the Advanced link/button and proceed to the Data Hub Explorer application, bypassing the error message.

I cannot create a service because I get the service status code SERVICE_FAILED.

When you create a service in your DHS portal, you might experience the service status code SERVICE_FAILED. This service status code means that your service failed to create. The instability of the Microsoft Azure platform contributes to the service creation failures. This is a known issue that intermittently occurs on the Microsoft Azure platform.

Workaround:
  • Retry creating your service in the Create Data Hub Service page.
Note: If you continue to experience the service status code SERVICE_FAILED, contact Support.