- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello EVeryone,
Trying to create a 'Service Instance' with Population method = Tag based but it does not allow to create.
For testing purpose three ( 3 ) CI has the Key/ Value pair for testing , however can not create SI
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thankyou all for assisting seems we had BR for allowing only Operational and once it was created as Operational it worked
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Nisha30
Ensure you are following the same steps as Use tags to populate application services
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey @Nisha30,
That banner, "A problem occurred during service creation", is a generic client-side catch in the CSDM Application Service wizard, it almost never tells you the real cause. Before you go back and re-tune the tag setup, pull up System Logs (System Log > All, filtered to the timestamp you hit "Preview the Service") and look for the actual exception behind that toast, in practice it usually points to a scripted REST resource or IRE payload failure rather than a bad tag definition. There's a documented known issue, KB1113499, about the Application Service wizard sending a malformed IRE payload during creation and update that surfaces this exact generic error, worth checking against your instance's patch level. Separately, confirm the key/value pair on your three test CIs actually lives in cmdb_key_value and not just some custom attribute on the CI form, tag-based population only reads from that table, and the key name is case-sensitive, so "Serviceid" has to match what's stored there exactly. If a service record does end up getting created despite the error, try Recalculate Service from Related Links, that's forced the candidate population through for others after a failed initial save.
Thank you,
Vikram Karety
Octigo Solutions INC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thankyou all for assisting seems we had BR for allowing only Operational and once it was created as Operational it worked