Discovery - The result file \\x.x.x.x\admin$\temp\psscript_output_076ca129-d772-42ad-ad0a-0439d8be2141.txt can't be fetched because it doesn't exist

[Harish27]

Hi , 

I have configured my mid server in Aws and validated it. When i ran the quick discovery for a windows machine am getting a strange error. The result file \\x.x.x.x\admin$\temp\psscript_output_076ca129-d772-42ad-ad0a-0439d8be2141.txt can't be fetched because it doesn't exist.

Discovery schedule ran successfully but it didn't gather all the required information. Ex. it didn't gather serial number, model etc. 

What is the cause of this error and how to rectify this. ? [ I am new to discovery ] 

Br,

Harish M

[Kieran Anson]

Hi,

The service account being used by the MID service needs to have access to this directory via the admin share. If you login to your MID server, are you able to access the admin$ share? 

KB0749612

[Harish27]

Hi Kieran,

Ya i did grant full permissions for the service account to both windows and admin$ share. 

I have followed this link : https://stackoverflow.com/questions/18388381/make-sure-that-the-default-admin-share-is-enable-on-servername for granting the permission.

I ran the discovery schedule and am able to see the information like serial number, model etc which were not visible earlier. But i still see the same issue in the discovery log. 

Br,

Harish M

[Appli]

Hi Harish, please check KB article with update set attached; an issue seems to be fixed in Paris version of patch 4 however it should be possible to apply a workaround.

Hope it helps

[ishan_]

Check if inbound TCP traffic allowed for target server on port 445 (for SMB).