Discovery error: "The result file can't be fetched because it doesn't exist"

[sr_surendra]

Dear all,

I'm getting error "The result file can't be fetched because it doesn't exist" .

I checked hi document provided for this 

https://hi.service-now.com/kb_view.do?sysparm_article=KB0749612

Solution given for this is :

From the MID server and with the same account used by discovery, ensure the user account used for discovery can:

Access/Create files on the target host

\\<ip_address>\admin$\tmp

I'm not able to understand what actually needs to be done as mentioned in solution

"How can I ensure user account used for performing discovery can access/create files on target host \\<ip_address>\admin$\tmp "

Is this something which I have to do or I have to ask server team to do some configurational changes on access of user which is mentioned in credential?

Can somebody help please?

Regards,

Surendra

[sergiu_panaite]

Hi Surendra,

MID server uses a pre-configured user account to run the Discovery; for more information on the user and the credentials configuration see:

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/discovery/concept/ru...

Now, the user account you configure on MID server needs to have certain administrative rights on the target machines against which Discovery runs. For more information see:

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/discovery/reference/...

So in the current case you need to check if the user configured on MID server has access to create files on the target machine (the discovered target, a Windows machine in this case) on the following path:

\admin$\tmp

You might need to ask your server team if that user has the proper administrative rights.

Regards,
Sergiu

[sr_surendra]

Thanks Sergiu for explaining this in simplest words possible.

I'm going through links mentioned above. 🙂

I'll get back here once I followed steps as mentioned.

Regards,

Surendra.

[Fernando Gois]

Thank you @sergiu.panaite , for you explanation about this issue. I had the same doubts as @sr.surendra@tcs on what is explained under https://hi.service-now.com/kb_view.do?sysparm_article=KB0749612

And just to make sure I am following you:

• When the KB Article Resolution says "From the MID server and with the same account used by discovery", the article is referring the "Windows Credential" that initiated the WMI probe, right?
• And under Step 1 (the only step), when it refers "Access/Create files on the target host", "target host" means the server (windows server) we want to Discover via WMI, from the MID Server, correct?

Thanks in Advance!

Fernando Gois

[Ashish Verma4]

Hi Surendra,

Please check with Firewall team, there is a blockage of port 445 for windows servers.

Port the port 445 and check , issue get resolved.

Thanks,

Ashish