Perfmon Collector Agent fails to start.

Article Id: 40567
Status: Published
Updated On: 14-02-2018 07:46
Legacy Id: TEC1358765
Products:
CA Application Performance Management Agent (APM / Wily / Introscope) , INTROSCOPE
Issue/Introduction:

 Issue:

 Perfmon Collector Agent fails to start. A correct version of wily.Agent.dll is in C:\Windows\Assembly.

 The service fails with a 'Windows could not start the CA APM PerfMon Collector Service on Local Computer. Error 1053: The service did not respond to the start or  control request in a timely fashion'. There is an error that shows up in the Windows Application event log with the following info: 

 Faulting application PerfMonCollectorAgent.exe, version 10.1.0.15, time stamp 0x560f17c5, faulting module KERNEL32.dll, version 6.0.6002.19594, time stamp  0x56ac2a1d, exception code 0xe0434f4d, fault offset 0x0002012f, process id 0x%9, application start time 0x%10.

 When run directly from the command-line (PerfMonCollectorAgent.exe), it shows an error as below:

 Introscope 10.1.0.15\wily\bin>PerfMonCollectorAgent.exe

 Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'wily.Agent, Version=9.1.0.0, Culture=neutral,  PublicKeyToken=2b41fdfb6cd662a5
 ' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
 File name: 'wily.Agent, Version=9.1.0.0, Culture=neutral, PublicKeyToken=2b41fdfb6cd662a5' ---> System.IO.FileLoadException: Could not load file or assembly ' wily.Agent, Version=10.1.0.15, Culture=neutral, PublicKeyToken=2b41fdfb6cd662a5' or one of its dependencies. The located assembly's manifest definition does not  match the assembly reference. (Exception from HRESULT: 0x80131040)
 File name: 'wily.Agent, Version=10.1.0.15, Culture=neutral, PublicKeyToken=2b41f
 dfb6cd662a5'
 
 WRN: Assembly binding logging is turned OFF.
 
 To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
 
 Note: There is some performance penalty associated with assembly bind failure logging.
 To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
 
 at com.wily.introscope.perfmonservice.PerfMonCollectorServiceMain.Main()
 

 Environment:

 Any supported Windows platform. APM 10.1.

 

 Cause:

 This particular system had earlier versions of Perfmon Collector Agent installed previously which left the entries in the C:\Windows\Microsoft.NET\Framework\ <Framework version>\CONFIG\machine.config file. For example,

 <runtime>
 <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
 <dependentAssembly>
 <assemblyIdentity name="wily.Agent" publicKeyToken="2B41FDFB6CD662A5"/>
 <bindingRedirect oldVersion="0.0.0.0 - 65535.65535.65535.65535" newVersion="9.1.0.0"/>
 </dependentAssembly>
 </assemblyBinding>
 </runtime>
 

Resolution:

 Leave the <runtime> </runtime> section in place, but correct/remove earlier version reference in <bindingRedirect> tag. For example:

 <bindingRedirect oldVersion="9.1.0.0 - 65535.65535.65535.65535" newVersion="10.1.0.0"/>

 

 Additional Information:

 After upgrading, a .NET Agent, you receive a Server Error in '/' Application

 Troubleshooting and Tips for the .NET Agent

Environment:

Release: CEMUGD00200-10.1-Introscope to CA Application-Performance Management-Upgrade Mai
Component: