---
title: "Acquia Search custom configset error messages"
date: "2025-05-28T08:42:11+00:00"
summary: "Troubleshoot custom configset errors in Acquia Search with our comprehensive guide to common issues and resolutions."
image:
type: "article"
url: "/acquia-cloud-platform/help/69456-acquia-search-custom-configset-error-messages"
id: "9a31c325-dd38-4bfb-a9fe-32e984e4ac65"
---

The following table lists the error messages of the Acquia Search custom configset:

**Error message**

**Description**

**Resolution**

`The uploaded file is not a valid ZIP archive.`

The uploaded file is not a zip file.

Upload a zip file with the .zip extension.

`File in the archive starts with "Byte Order Mark".`

The file in the archive starts with a Byte Order Mark (BOM) character. This character is added by Microsoft OS.

Remove the Byte Order Mark (BOM) character from the start of the file.

`File in the archive refers to an unavailable file.`

The file is not present in the archive. 

Insert the missing file in the archive.

`File has invalid line endings, Use Unix style.`

The file uses line endings other than UNIX. Acquia Search requires UNIX line endings.

Use UNIX line endings. It uses only “\\n” at the end of a line.

`Found files with invalid content or format.`

The archive contains files with invalid format or content.

Ensure that the files follow the [custom configset file requirements](/acquia-cloud-platform/custom-solr-configuration "Custom Solr configuration") before they are inserted in the archive.

`Required file 'solrconfig.xml' is not found in the root of the archive.`

The `solrconfig.xml` file is not found at the top-level directory.

Ensure that the `solrconfig.xml` file is present at the top of the archive directory.

`Unwanted files found. Please remove or rearrange.`

Unnecessary files are present in the archive.

Remove unused or unwanted files from the archive.

`Any error having prefix "Solr Error:".`

This error message is generated at the Solr level after the basic validation is completed.

Test the configset on a local environment before uploading it to production.

`Configset file you are trying to upload, already exists.`

The configset is the same as an existing configset for your application. The new configset does not introduce any changes.

Use the existing configset with your desired settings, or modify the configset and upload the updated file.

`File is too large. Maximum size allowed is 1MB.`

The size of the file is more than 1 MB.

Upload a file with a size less than 1 MB.

`Unknown Error`

An unknown issue occurred during the configset upload.

[Create a Support ticket](/service-offerings/support "Support").