Error: Failed to copy remote distributed modules.

Email It to Me Print this Page
Symptoms
The notification emails of NetWrix Event Log Manager or NetWrix Logon Reporter contain the following errors:
<timestamp> <problematic_server> <error> Failed to copy remote distributed modules. Error details: The process cannot access the file because it is being used by another process.
Image 1
Cause
To collect the event data from the remote machines, NetWrix Event Log Manager and NetWrix Logon Reporter use the same agent services. The error occurs when 2 or more different processes are trying to update agent service modules on the problematic server simultaneously. This may occurs in the following cases:
  1. Both products are configured to collect events from the problematic server.
  2. 2 or more different Event Log Manager managed objects are configured to collect logs from the problematic server.
NOTE:
  • The scheduled tasks of the products are configured to start the data collection every 10 minutes, so there is probability that 2 processes will try to update files at the same time.
  • The issue is not critical if it does not lead to the "Log overwrites" warnings (See the following KB article: Log overwrites warnings )
Resolution
Please perform one of the following steps to resolve the issue:
  1. If you added the problematic server into the different managed objects (or into both products) by mistake, remove it from one of the managed objects (or from one of the products).
How to remove a server from the managed object:
  • Start NetWrix Management Console and click the appropriate managed object.
  • Switch to the Items tab, click the problematic server and click Remove.
How to remove a server from the NetWrix Logon Reporter data collecting:
  • Start NetWrix Logon Reporter, enable the "Do not gather events from specified computers" check box and click Configure.
  • Add the problematic server into the Computers list and click OK. Click Apply.
Image 2
  1. If you need to have the problematic server in both managed objects (or in both products), disable the agent usage for one of the managed objects (or for one of the products).
How to disable the agents for the entire managed object:
  • Start NetWrix Management Console and expand the appropriate managed object.
  • Click the Event Log Manager node and turn off the "Enable network traffic compression" option.
Image 3
 
How to disable the agents for the particular server (method is valid for both products and affects all managed objects):
  • Navigate to the program installation directory and open the "agent.ini" file via Notepad.
  • Add the following string and save changes: server_name=remote
Image 4
 
  1. If you do not want to disable agent usage for the problematic server, configure the scheduled tasks triggers to run less frequently for both managed objects (or for both products).
That will decrease the probability that 2 processes will try to update files at the same time and perhaps resolve the issue. 
 
How to configure the scheduled task trigger in Windows 7/2008:
  • Start Task Scheduler, navigate to the Task Scheduler Library node and double-click the appropriate scheduled task.
  • Switch to the Triggers tab and edit the Daily trigger.
  • Set it to Repeat task every 20 minutes. Click OK, and then click Apply.
Image 5
 
How to configure the scheduled task trigger in Windows XP/2003:
  • Click Start / Control Panel / Task Scheduler and double-click the appropriate scheduled task.
  • Click Schedule and then click Advanced.
  • Specify 20 minutes in the Repeat task area. Click OK, and then click Apply.
Image 6
(*) Netwrix Auditor replaces former Change Reporter products
Was this information helpful?