NET (Agent, Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

.net Agent Reporting post IIS restart

Highlighted
Adventurer

.net Agent Reporting post IIS restart

Hi,

We are facing issues with the .net agent reporting after IIS restarts. There are 2 applications in the same set of 4 load balanced servers. After the IIS restarts we see only one of the 2 applications are reported by agents. 

AppDAgentReporting.JPG

Regards,

Pavan Kumar

.net Agent Reporting post IIS restart
4 REPLIES 4
AppDynamics Team (Retired)

Re: .net Agent Reporting post IIS restart

Hi @Pavan.Kumar

 

Please see if Microsoft's System Center Operations Manager (SCOM), which includes an Application Performance Monitoring feature, not conflicting with AppD .NET agent. Both employ the .NET Profiler interface, and only one profiler can be used at a time.

 

Please update the thread if you are able to resolve the issue or still have further questions.


Thanks,
Radhika P




Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

Re: .net Agent Reporting post IIS restart

As Radhika said, please verify there is no other profiler .

Also since you say load balancer , are you sure the load is there on the other two servers where you dont see them in Appd?

If there is no load Appdynamcis will not show it up.

Adventurer

Re: .net Agent Reporting post IIS restart

Hi Radhika,

Thanks for the inputs.

There is no conflict with the profiler. We had issue with the sitename. In out latest internal site release they modified the sitename. We were looking into the apppool name. we had different names at diff places. We corrected our config file and it started working.

 

Regards,

Pavan Kumar

Adventurer

Re: .net Agent Reporting post IIS restart

Hi Umervali,

Thanks for your inputs.

There was enough traffic on all the servers.

We had issue with the sitename. In out latest internal site release they modified the sitename. We were looking into the apppool name. we had different names at diff places. We corrected our config file and it started working.

 

Regards,

Pavan Kumar