Description

After Minirollup 07-07 or patch SWD-11302187.3 has been installed on the Core server, Agents were re-installed. After the installation of the minirollup and you push a NEW agent to a clean box during the agent install Amclient.exe complains about not finding ProcessRunner.dll.

This application failed to start because processrunner.dll was not found. Re-installing the application may fix the problem.

Resolution

Verify that the Agent Configuration's INI file is properly configured to add this file to the agent.

1. On the Core Server, Locate the INI file for the Agent Configuration in the LDLOGON directory.

2. In the Agent Configuration INI file, locate the following section heading:

   [Enhanced Software Distribution]
   

    

3. Locate the line similar to the one displayed below:
   

   FILExxx=processrunner.dll
   

    

If for some reason this line is not present in your Agent Configuration INI file, then it will need to be added to the ntstacfg.in#

1. Browse to the LDLogon directory on the Core Server.
   program files\LANDesk\ManagementSuite\LDLogon.

2. Locate the NTSTACFG.IN# file and open it with a Text Editor such as Notepad.exe or Wordpad.exe.

3. Find the following section:

   [Enhanced Software Distribution]
   

    

4. Under that section, look for an entry that adds the processrunner.dll file. It will appear as follows:

   FILE##=processrunner.dll
   

   Where ## is a valid unique number for that section.

5. If there is not entry for processrunner.dll, the missing line must be manually added.

6. After adding this line to the ntstacfg.in#, STAMPER.EXE must be executed. On the Core Server browse to \Program Files\LANDesk\ManagementSuite\ and double click on STAMPER.EXE.
   Note: Alternately, restarting the inventory service will run cause STAMPER.EXE to run.

7. Once STAMPER.EXE is run, verify that the date of NTSTACFG.INI is updated.

8. Then open the LANDesk Console.

9. Go to Tools | Configuration | Agent Configuration.

10. Click on the Rebuild All icon. This adds that line to all the Agent Configuration INI files. This will prevent the issue from occurring on newly deployed agent configurations.

11. On agent workstations that are already experiencing this problem, redeploy the agent configuration.