.NET Troubleshooting Guide Follow

 

Known Issues

The .NET Micro-Agent does not run with other agents, so any functions related to these agents won’t be available.

Troubleshooting

This article addresses different .NET troubleshooting issues. Additional information about installation troubleshooting can be found in the Installation Troubleshooting article.

 

Supported Versions

Verify that you're using one of the following supported .NET frameworks:

  • .NET Framework 2.0 to 4.8
  • .NET Core 2.0, 2.1, 2.2

 

 Supported Application OSs

Verify that Your .NET Application is running on a 64-bit application. The .NET Micro-Agent only supports 64-bit applications and operating systems. 

 

Providing the  PDB File Path and Source File Path During Installation

During the installation process, you’ll be asked to provide the directory path to PDB file(s) on the application host. If these files don't exist, make sure they’re copied to the path when the application is deployed.

You’re also asked to provide the directory path to the Source files(s) on the Collector host.If these files don't exist, make sure they’re copied to the path when the application is deployed.

 

Decompiling Code Requires a PDB (Program Database) File

For OverOps to fully diagnose errors and exceptions, we require your source code as well as the PDB. The PDB is critical for extracting variable names and is a crucial part of the Micro-Agent's work. 

 

Source Code Files Aren't Being Decompiled

When using the .NET Micro-Agent, decompilation is not supported yet; you’ll need to copy the source files after deploying the application and link to them from the Micro-Agent using the source flag.

 

Disabling Automatic Startup for the Collector Service (Windows)

Open Services, find the service called Takipi Service or Takipi, open the services property, and in the General tab, disable automatic startup for this service.

mceclip0.png

 

Attaching the .NET MIcro-Agent to Your .NET Application 

The .NET Micro-Agent is attached to your IIS application by default when the Micro-Agent installation completes. 

If you're using a standalone application), you’ll need to set the following environment variables manually for the CLR to load the Micro-Agent:

COR_ENABLE_PROFILING=1
COR_PROFILER={9E9BF2AC-891E-4AAD-9192-44645082EB3E}

For .NET Core use the following environment variables:

CORECLR_ENABLE_PROFILING=1
CORECLR_PROFILER={9E9BF2AC-891E-4AAD-9192-44645082EB3E}

Installing .NET Micro-Agent with a Linux Collector

OverOps on .NET enables you to install either a Window or a Linux Collector with the .NET Micro-Agent. Follow the instructions in this article to install the Linux Collector. Then, download the MSI installer from this link  (the link always points to the latest MSI installer) to install the .NET Micro-Agent. 

 

Using Azure App Services with VMs or Windows Containers

There are different kinds of VMs that Azure supplies: 

    1. Azure Virtual Machines, which are full VMs for you to access and manage. 
    2. Azure App Services - which are sort of "Managed VMs" - everything is configured and provisioned for you, but you still have different ways to access the machine, and it has persistent memory like a normal VM. 
    3. Full Windows Containers, which are not currently supported in OverOps. Azure App Services and Azure Windows Containers are two different services.

For .Net Core, there currently only support for running on Windows in VM and not in containers. Containers currently play a fairly limited role in .NET Core adoption but will be fully supported in a future version.

 

Support for Multiple Applications

The OverOps Collector supports multi-applications pointing to it. 

  • For PDBs, you’ll need to configure the path to them (symbols) on the Micro-Agent machine’s agent.properties file. Set the takipi.symbols.path property to the location of your  PDB.
  • The source needs to be located on the machine where the Collector is running. The location of the source file is set in the Micro-Agent machine’s agent.properties file by setting the takipi.sources.path property to the location of the source file on the Collector machine.

Refer to this article for more details.

 

Comments

0 comments