Troubleshoot "Failed to create collection: resource already exists" Splunk Error for Umbrella Add-On or Cloud Security App

Available Languages

Download Options

PDF (16.4 KB)
View with Adobe Reader on a variety of devices
ePub (90.1 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (75.9 KB)
View on Kindle device or Kindle app on multiple devices

Updated:October 17, 2025

Document ID:225235

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Background Information

Cause

Resolution

Introduction

This document describes how to troubleshoot a "Failed to create collection: resource already exists" error for Umbrella Add-On or Cloud Security App.

Background Information

Some customers can experience an error after configuring the Cisco Umbrella Add-On for Splunk or Cisco Cloud Security App for Splunk. End result no log data is ingested into Splunk. Debug logs in either the Add-On or the App shows this error:

HTTPError(response) splunklib.binding.HTTPError: HTTP 500 Internal Server Error -- Failed to create collection: resource already exists

Cause

This error occurs if you have setup the Add-On or App, previously deleted it, and tried to add it again.

When the app is uninstalled, splunkd normally triggers a reload function syncing the latest configuration with collection data in the database and removes the collection if no corresponding config is found - orphaned collection. However, the reload implementation within KVService fails to do so, leaving this orphaned collection in KVService.

When the app is reinstalled, it does not find the configuration file, as it was removed in the previous step, but when it tries to create it it fails because the KVService still has the collection present within the app context.

Resolution

To resolve the issue upgrade Splunk server to version 9.1.2312.104. If upgrading is not an option open a support ticket with Splunk support. They have a process to cleanup the orphaned collection.

For more information, refer to this splunk support KB: https://splunk.my.site.com/customer/s/article/Failed-to-create-collection.