Failed to add windows service to AppDynamics

[CommunityUser]

Hello,

I can't add windows service to AppD

Config:

<app-agents>
    <IIS>
      <automatic />
    </IIS>
	<standalone-applications>
        <standalone-application executable="E:\ASApps\MFMMWWS\AccessSoftek.MW.System.Service.Host.exe">
           <tier name="MFMMW winservice" />
        </standalone-application>
    </standalone-applications>
  </app-agents>

WinService:

Error form AgentLog.txt

AccessSoftek.MW.System.Service.Host 1 16 Error AgentTransientEventManager Error occurred during handling of operations : Exception: System.NullReferenceException: Object reference not set to an instance of an object.

I tried to configure POCO Entry Points (https://docs.appdynamics.com/display/PRO42/POCO+Entry+Points)
But I didn't discovery any Classes/Methodes in the Transaction Discovery Tool

[Hariraj_J]

Hi,

Confitm that the exe you are tring to instrument is a .Net by running the command

 tasklist /m "mscor*"

https://docs.appdynamics.com/display/PRO42/Instrument+Windows+Services+and+Standalone+Applications

Regards,

Hari 

[Ashish_Singh]

Hi Svdubovik,

In case of Windows Services/Standalone applications, if your Windows service or standalone application doesn't implement an auto-detected framework .net agent do not capture BTs OOTB and you have to configure Custom Match Rules of type ".Net Class/Method" to initiate the BT.

For more details refer the following document 

https://docs.appdynamics.com/display/PRO42/Instrument+Windows+Services+and+Standalone+Applications

One way of identifying appropriate Match Rules is by enabling the "find-entry-points" node level property.

(assuming application is making some common exit calls like Http/DB etc).

Following docs explains how to enable this node level property.

https://docs.appdynamics.com/display/PRO42/App+Agent+Node+Properties+Reference#AppAgentNodePropertie...

https://docs.appdynamics.com/display/PRO42/App+Agent+Node+Properties#AppAgentNodeProperties-editregi...

Once you enable this, all the executing call stacks related transaction of the application will be dumped into BusinessTransaction.txt logs. Which we can use to create Match Rules.

Please enable above node property at tier level and execute transactions which you will like to monitor. Review theBusinessTransaction.txt logs and you should see empty stack dumped into BT logs.

Once you find the appropritae class/method from call stack to create custom match rule ( POCO). please refer the below document.

https://docs.appdynamics.com/display/PRO42/POCO+Entry+Points

if you still face any issue, please provide us zip of complete DotNetAgent folder for review located at %ProgramData%\AppDynamics or if you have changed the default location then provide the same to troubleshoot further. This is a hidden folder and can be found at the following location:

Windows Server 2008 and later %ProgramData%\AppDynamics\DotNetAgent

Windows Server 2003 %AllUsersProfile%\Application Data\AppDynamics\DotNetAgent

Thanks,

Ashish.