Application Services Creation claims name already exists

Steen Strunge
Tera Contributor

When trying to create a Manual Application Service a validation continiously claims the name already exists. I do not have any name in whole cmdb which matches. What am I doing wrong?

find_real_file.png

1 ACCEPTED SOLUTION

So if you name it 'Test Client Prod App - Steen', it fails as well? 

The IdentifyCI details can be seen on this page, which might help. 

https://developer.servicenow.com/dev.do#!/reference/api/orlando/server_legacy/c_IdentificationEngineScriptableApiAPI

View solution in original post

9 REPLIES 9

Barbara L - Gli
Tera Guru

Hello,

Is this occurring no matter what name you input? 

This script include is what displays that exact message when it's checking if it "alreadyExists", at line 327:

YOUR-INSANCE-NAME.service-now.com/sys_script_include.do?sys_id=0ef3fd1d73c30010ee4dd3c72bf6a704&sysparm_view= 

I believe this is being called when the App Service is being validated, is this at all customized in your instance? Or could something be going wrong with the number, so the number already exists?

It's using a hidden function to identify the actual service so I can't say exactly how it's validating, but the hidden function is when it calls "SNC.IdentificationEngineScriptableApi.identifyCI(input)" on line 73 so that should all be completely oob

I have tried with many different names and checked in cmdb_ci to be sure no same value exists.

And I also found this script

find_real_file.png

 

Which call this - and then I am lost:
find_real_file.png

So if you name it 'Test Client Prod App - Steen', it fails as well? 

The IdentifyCI details can be seen on this page, which might help. 

https://developer.servicenow.com/dev.do#!/reference/api/orlando/server_legacy/c_IdentificationEngineScriptableApiAPI

Thank you SteveMac.

I have now found a message saying "Missing mandatory field [portfolio_status] in table [cmdb_ci_service_auto]"

So not the name, but a missing input.

 

 

AlexandreHerrer
Kilo Expert

Hi,

I've the same problem with my client, I've raised a /hi ticket, this is caused by other fields mandatory at CMDB level, we've an old instance and theses fields were marked mandatory:
cmdb.install_status

cmdb.location

cmdb.manufacturer

and a custom field cmdb.u_type

unsetting the mandatory, or just putting a dictionary override for cmdb_ci_service_auto solves the issue.

Best Regards