Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows MSI install does not deploy required gRPC libraries for .NET Core #781

Closed
JcolemanNR opened this issue Oct 30, 2021 · 1 comment · Fixed by #788
Closed

Windows MSI install does not deploy required gRPC libraries for .NET Core #781

JcolemanNR opened this issue Oct 30, 2021 · 1 comment · Fixed by #788
Assignees
Labels
bug Something isn't working

Comments

@JcolemanNR
Copy link
Contributor

Description
While testing the .NET agent on a fresh system, I noticed that I was receiving errors when enabling Infinite tracing for .NET Core applications. Upon deeper investigation, the .net core agent folder is missing the gRPC native libraries.

Expected Behavior
The MSI installer correctly deploys all required dependencies.

Steps to Reproduce
On a clean system, run the windows MSI installer (agent version 9.1.0).
Enable infinite tracing
Turn agent logs up to finest
Profile a .net core application
Review agent log and notice that an exception is encountered establishing gRPC channels due to missing native dlls.

Your Environment
Windows Server 2019 Datacenter
.NET agent 9.1
.NET Core 5.0 console application with custom instrumentation

@JcolemanNR JcolemanNR added the bug Something isn't working label Oct 30, 2021
@JcolemanNR
Copy link
Contributor Author

JcolemanNR commented Nov 1, 2021

manual workaround is to copy the following files:
grpc_csharp_ext.x64.dll
grpc_csharp_ext.x86.dll

from C:\Program Files\New Relic\.NET Agent\netframework to C:\Program Files\New Relic\.NET Agent\netcore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant