No inclusion connection created from CI (type: cmdb_ci_appl_sharepoint)

Adiseshu Borra
Giga Guru

Hi All,

we are getting below message in service mapping for some of business services.

"No inclusion connection created from CI (type: cmdb_ci_appl_sharepoint). Please check the correctness of the incoming connection and the pattern".

when i run a quick discovery with respective IP address, there is no issue. But facing issue in service mapping.

Can some one help me on this. Thanks in advance. 

find_real_file.png

1 ACCEPTED SOLUTION

Adiseshu Borra
Giga Guru

Finally with the help of HI support, we resolved the issue.

solution : add cmdb_ci_appl_sharepoint table name in ECC agent property.

 ECC agent Table :ecc_agent_property

Property Name :map_accuracy_errors_ci_types_to_exclude

View solution in original post

6 REPLIES 6

johnnyjava
Kilo Guru

These messages occur when a Pattern is "smart enough" to know that one of the Connection Sections should have created a connection to your next tier - weather that is an Application Flow between (for example) Apache and Tomcat or an Inclusion Connection (for example) of IIS Virtual Directory within IIS Web Server.

In the case of Sharepoint, one of these Connection sections should have included (by way of the Create Connection Operation) another CI. To figure out what went wrong, you can review your logs by right-clicking on the Sharepoint node within your map.

 

find_real_file.png

Hi Johnyjava,

Thanks for your response.

in discovery logs, i am getting below errors.

1) 'Registry key HKEY_LOCAL_MACHINE/SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0/ServerId not found on host'

2) Groovy code failure. com.snc.sw.exception.CommandFailureException: HTTP request to http://*****:20000//_admin/FarmServers.aspx failed with status The remote name could not be resolved: '****'. HTTP request to http://***:20000//_admin/FarmServers.aspx failed with status The remote name could not be resolved: '***'

Note : *** is the server name.
 

 

Adiseshu Borra
Giga Guru

Finally with the help of HI support, we resolved the issue.

solution : add cmdb_ci_appl_sharepoint table name in ECC agent property.

 ECC agent Table :ecc_agent_property

Property Name :map_accuracy_errors_ci_types_to_exclude

I feel like that's masking the issue. You could just as well had set those particular messages to ignore.

Why don't you want the pattern to correctly perform an inclusion to some database?