Services Detected Name: "Declared unavailable by agent"

[Vineet_Sinha]

What can be the reason that for some services the Detected name is shown as below in DT UI

[declared unavailable by agent] / [unresolved]

Below are some more points related to the observation

* The processes associated with the services showing unavailable are detected and named as expected.

* The Services main technology are .NET and ASP.NET

*No custom service detection rules are set 

*Other NET/ASP.NET services related to same host are detected and named properly.

Thanks

[Mohamed_Hamdy]

Hi Vineet_Sinha,

I think you need to open a support ticket and try to include the logs, screenshots, and URLs

[FullastackMon]

Salam Hamdy,

Is it resolved now? If yes,  please provide the steps to fix this Issue. Thanks!

Regards,
Manohar

[Rodrigo_Miranda]

I also have this problem

[georgiag]

I also am experiencing this problem.

Disabling the .NET WCF v2 made an improvement for a process I tested on, is that feature enabled for you?

[ernestojm]

I also have this problem, has anyone been able to solve it?

[Rodrigo_Miranda]

I open a ticket, we've been looking for the reason for two months, we still don't have anything

[dylan_taelemans]

I also am experiencing this problem.
Has there been any update yet?

[chrmckenna]

Same issue here

[cesarsaravia]

Hi @Vineet_Sinha 
I highly recommend on these cases to raise a support ticket and the supporting team could help you to deep investigate this behavior with your services.
Regards,

[ViniFerreira]

Hi @Vineet_Sinha , 

How was this problem? Did you solve it?