Overview of the Issue

This article is meant to help when:

1. The vFunction Agent is not loading in a .NET Application running in a Linux environment
2. The vFunction Controller is not able to talk to the vFunction Agent and no log file is created by the vFunction Agent

Confirm the Environmental Variables are accurate

1. Set one additional Environment Variables to help with visibility

export PAL_OUTPUTDEBUGSTRING="1"

2. Check the Standard Output during the startup of the .NET Application. Some additional information should be printed about the vFunction Agent profiler being loaded

The profiler was loaded successfully. Profiler CLSID: '{cd7d4b53-96c8-4552-9c11-6e41df8eab8a}'

Loading profiler failed during instantiation.  Profiler CLSID: '{cd7d4b53-96c8-4552-9c11-6e41df8eab8a}'.  HRESULT: 0x8007007e

3. If the Profiler fails to load, check that the Path used in the vFunction Environment Variables is accurate and has no typos
4. If the Profiler fails to load, confirm that the User running the Application has Full Access to the Directories associated with vFunction

Gather Debug-Level Information

1. Add an additional Environment Variable to print very verbose information about the Profiler Loading process to Standard Error

export LD_DEBUG=all

2. If the Standard Error and Standard Output logging is not already captured, write the details into a file that can be shared with vFunction for further investigation

### Replace "my-app" with the Application's executable's name
./my-app > debug-output.log 2>&1