Highlighted
Super Contributor.
Super Contributor.
456 views

Discovery jobs very slow and sometimes failing

Hi Experts,

 

We have Discovery jobs that are failing and few very very slow. Checked for the heap size but it does not help.

 

The communication log says NTCMD network path not accessible.

 

 

everity="debug">Reporting error code 114 to framework.</log>
 <log start="9:14:53" severity="debug">Error message is: NTCMD: Network path is not accessible.</log>
 <log start="9:14:53" severity="debug">Reporting error code 114 to framework.</log>
 <log start="9:14:53" severity="debug">Error message is: NTCMD: Network path is not accessible.</log>
 <log start="9:14:53" severity="debug">Reporting error code 114 to framework.</log>
 <log start="9:14:53" severity="debug">Error message is: NTCMD: Network path is not accessible.</log>
 <log start="9:14:53" severity="debug">Reporting error code 114 to framework.</log>
 <log start="9:14:53" severity="debug">Error message is: NTCMD: Network path is not accessible.</log>
 <results>

 

The IP's are pingable via servers and everything looks fine from the network end,

 

Any one faced this kind of issue before? Please advice.

 

Regards

Mathew

0 Likes
1 Reply
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Discovery jobs very slow and sometimes failing

Hi,

Please define very slow. What the expectation is?

 

Regarding the problem you see in comm logs:

Checking accessibility of "admin$" shared folder:

Please make sure that the remote machine has "admin$" shared folder accessible from the probe machine. To check the access to "admin$" shared folder on remote machine, please perform following steps:

  • Login to probe machine.
  • Go to "Start"->"Run".
  • Enter
    \\<remote machine>\admin$ address.
  • Press enter.
  • If you have an access to "admin$" share - you are done.
  • If there is no access to "admin$" share, following steps are needed:
    • Login to the remote machine.
    • Click Start, click Run, type regedit, and then click OK.
      • Locate and then click the following registry subkey:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
      • In the details pane, click AutoShareServer.
      • On the Edit menu, click Modify. In the Value data box, type 1, and then click OK.
    • Exit Registry Editor, and then restart the computer.
      Note If the AutoShareServer registry entry does not exist, follow these steps to create it:
      Locate and then click the following subkey in the registry:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
      On the Edit menu, point to New, and then click DWORD (32-bit) Value.
      Type AutoShareServer, and then click OK.
      Double-click AutoShareServer, type 1, and then click OK.
    • At the command prompt, type net start srvnet, and then press ENTER.
Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.