Service Mapping - Can't calculate storage path error

james_lewis
Tera Contributor

During most my Service Mapping discoveries I get the following error

find_real_file.png

Can't calculate storage path for "d:\". File system on connection did not match any file system on the host

I was wondering if any of you have seen this before and know how to solve it.

Seen on Geneva and Istanbul instances.

8 REPLIES 8

Hi James,



Looking at the screenshot, the File Systems tab is empty and fairly certain this is what it looks for (and not the storage devices). Were there any errors after you ran discovery?



Regards,



Dave


No errors found.   Just one warning



https://tcfdev.service-now.com/discovery_log.do?sys_id=bf41bb5b4fe40300fccb76601310c73c&sysparm_view...WarningNo results returned from probe.


for the probe WMI: Find APD File Location (nodes: 0)


Hi James,



If you have this in a dev env, perhaps as a test, manually add the file system similar to below (mount point might be important) and then rerun mapping:


Screen Shot 2017-08-21 at 10.28.23.png



If it works, then this would then narrow it down to the horizontal discovery and so can then focus investigation on the file system discovery issue.



Regards,



Dave


Pratiksha
Mega Sage
Mega Sage

A pattern with a connection section creating connections to storage has created a connection with file system that doesn't exist on the host.

Connection Section has created bad connections

Review the discovery the log, mainly the "Create Connections" step under the Connection Section creating connections to storage. If the values if "file_system" are not correct, fix the pattern.