Just installed .NET agent 9.6.
We have a webservice calling a method running on a cluster server: it stalls at each run. If the .NET agent is removed, the webservice runs okay.
Can you please advise how to solve this problem?
Sometimes certain tracer types can cause application problems & I see you are currently using default-full.pbl in your agent profile.
As a first step I would suggest changing that to default-typical.pbl & recycling the agent/IIS AppPool.
The default-typical.pbl will use toggles-typical.pbd instead of the toggles-full.pbd used by default-full.pbl.
Compared to toggles-full.pbd, toggles-typical.pbd removes these 4 tracers
If using default-typical.pbl is successful you can then restore default-full.pbl and disable each of the above tracers one by one to see which one causes the problem.
SocketTracing has been highlighted quite a lot in the past but whether it causes a problem is really application dependent.
If default-typical.pbl is still not successful the problem may lie with the webservices.pbd invoked by the spm.pbl.
In that case I would suggest you open an issue with Support because more detailed research will be required.
Hope this helps
This is an OOTB PDB deployment...
I disabled the traces as directed and the web service is now running fine..
I will not attempt to identify the offending trace right now as this is a production system. We will try it later on our development systems.
Many thanks for your help.
Retrieving data ...