A 'Path not found' error occurs when runnign the AD_ReplSysVol script agaisnt a Domain Controller (NETIQKB48738)

  • 7748738
  • 02-Feb-2007
  • 20-Aug-2010

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

A 'Path not found' error occurs when runnign the AD_ReplSysVol script agaisnt a Domain Controller
A 'Path not found' error occurs when the Domain Controller running knowledge script AD_ReplSysVol attempts to access or open a file on another machine.
An AD_ReplSysVol 'Path not found' error occurs when attempting to open a file on the SYSVOL share of FRS replication partner.

Resolution

All components except the filename compose the path. The 'Path not found' error will occur if:

1.    The <{server}> is unreachable. For example this will occur when name resolution fails, the resolved IP address is unreachable or not the IP address of the FRS partner domain controller. Verify name resolution, DNS configuration, and network connectivity. Additional possible causes for intermittent errors include network congestion and heavy server load.

2.    The <{share}> doesn't exist. Verify the FRS partner is sharing SYSVOL and the Server service is running.

3.    The directory path<{path}\{subpath}\{...}>does not exist.

Perform the following steps to verify a valid UNC path:

1.    Verify the FRS partner is sharing SYSVOL and the Server service is running.

2.    Verify that the workstation service is running on the agent that encountered the error.

3.    Verify the path to the FRS partner exists.

Cause

If any component of the UNC path is unreachable or does not exist, the file open attempt will result in a 'Path not found' error.

This is the UNC path syntax:  <\\{server}\{share}\{path}\{subpath}\{...}\{filename}>

 

Additional Information

Formerly known as NETIQKB48738

If the 'Path not found' error occurs intermittently, FRS replication is occurring.  In the event that you may not be able to determine an explanation for the error, configure the Advanced tab to Raise an event only if it occurs 3 times within 3 job iterations to avoid one-off Events from the job.