Error "Target instance already exists (cannot create new record)" when adding new record
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2023 10:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2023 01:24 AM
Hi Piotr,
Was this issue ever fixed? Currently experiencing the same issue myself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2023 10:01 AM
HI ticket was required.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 02:03 AM - edited 05-19-2025 02:04 AM
I know this is a somewhat old thread but it's the first one that comes up with this error and doesn't seem to have a solution.
In my case, I saw that there was a previously renamed instance on the instance table. The underlying database was the same as the instance I was trying to clone, and so the validation would fail. By deleting the other record from the instance table, I was then able to insert the new record with the correctly named instance.
So for example: old instance name was abc2 but the new instance name was abctest. The instance table still referenced abc2. I deleted abc2 and was then able to insert abctest. To ServiceNow, the name of the subdomain doesn't seem to matter much for cloning purposes. It's the underlying SQL database reference that matters here.