Error "Invalid insert. Service with SN App Service ID: SNSVC0001038 already exists"

lvenna
Tera Contributor

I am in the process of creating a Dynamic CI Group for Change Management purposes. I have created a CMDB group, and while attempting to define a new Dynamic CI Group, I encountered the following error:

“Invalid insert. Service with SN App Service ID: SNSVC0001038 already exists.”

 

Screenshot_24.png


I would appreciate any insights into the root cause of this issue and guidance on how to resolve it. Specifically, I am trying to understand if this is related to a conflict with an existing service in the CMDB or a configuration constraint within the Dynamic CI Group setup.

Has anyone else experienced a similar issue, or can someone provide clarity on how this validation works? 

 

1 ACCEPTED SOLUTION

Robert H
Mega Sage

Hello @lvenna ,

 

It seems that there is already an existing Service in your CMDB with that number. A Dynamic CI Group is a Service as well (its table name is cmdb_ci_query_based_service).

 

Please verify by going to the cmdb_ci_service_auto table (might be called "Application Service" or "Service Instance" depending on your ServiceNow release) and adding the Number column to the list. Is there already a record with Number = SNSVC0001038?

 

RobertH_0-1746856118194.png

 

If so then the number counter needs to be adjusted. Please sort the above list by Number and take note of the largest Number. Then navigate to System Definition > Number Maintenance and open the configuration for Prefix "SNSVC". In that form, click Show Counter.

 

RobertH_1-1746856451814.png

 

Finally, update the Number field to the largest Number you found in the service table. 

 

RobertH_2-1746856573974.png

 

The next time someone creates a Dynamic CI Group the system will increase that counter and assign it to the CI, ensuring that it is available.

 

Regards,

Robert

 

 

 

 

View solution in original post

3 REPLIES 3

Robert H
Mega Sage

Hello @lvenna ,

 

It seems that there is already an existing Service in your CMDB with that number. A Dynamic CI Group is a Service as well (its table name is cmdb_ci_query_based_service).

 

Please verify by going to the cmdb_ci_service_auto table (might be called "Application Service" or "Service Instance" depending on your ServiceNow release) and adding the Number column to the list. Is there already a record with Number = SNSVC0001038?

 

RobertH_0-1746856118194.png

 

If so then the number counter needs to be adjusted. Please sort the above list by Number and take note of the largest Number. Then navigate to System Definition > Number Maintenance and open the configuration for Prefix "SNSVC". In that form, click Show Counter.

 

RobertH_1-1746856451814.png

 

Finally, update the Number field to the largest Number you found in the service table. 

 

RobertH_2-1746856573974.png

 

The next time someone creates a Dynamic CI Group the system will increase that counter and assign it to the CI, ensuring that it is available.

 

Regards,

Robert

 

 

 

 

lvenna
Tera Contributor

I successfully created a Dynamic CI Group containing approximately 11,000 CIs. However, when I reference this group in the Configuration Item field on a Change Request or Change Task, the Affected CIs tab does not auto-populate with the associated CIs from the dynamic group. I also attempted this on related change tasks, but the behavior remains the same.

Is this the expected behavior in ServiceNow?


My primary goal is to allow users working on change requests to simply select a Dynamic CI Group, and have all the CIs within that group automatically populate under the Affected CIs tab. This would significantly improve efficiency for scenarios where thousands of CIs are involved.

If using a Dynamic CI Group does not natively support for my work, can you please help me on alternative solutions or recommended best practices to bulk-add CIs to a Change Request or Change Task. Manual addition is not scalable when dealing with a large volume of CIs.

SK Chand Basha
Giga Sage

Hi @lvenna 

 

Follow the steps mentioned in below KB article to resolve the issue. 

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0955143

 

Mark it helpful and accept Solution!! If this helps you to understand!!