Small and medium business | Business Central, N...

Enabling Diagnostic Tracing for Dynamics NAV Web Services

(5) Share

Report

Posted on by CU23060257-1

In the article below, it mentions to use WCF to to enable NAV web services tracing.

https://community.dynamics.com/blogs/post/?postid=72949ba3-64a4-4f24-ab8a-b9c00dc493de

When I implemented what was mentioned in the article, I could not restart my server. Any faced this issue?

I am using NAV2017.

Categories:

Microsoft Dynamics NAV

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Holly Huffman 6,530 Super User 2025 Season 2 on at

Like (0)

Report
Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!

The issue you're facing with the server not restarting after enabling diagnostic tracing for Dynamics NAV Web Services in NAV 2017 could be due to misconfigurations in the WCF tracing setup. Here are some potential causes and solutions:
Possible Causes

Invalid Configuration in web.config:

If the changes made to the web.config file for enabling WCF tracing are incorrect or incomplete, it can prevent the NAV Server from starting.

Trace Listener Issues:

The trace listener settings might not be properly defined, or the file path for the trace logs might be inaccessible or invalid.

Resource Constraints:

Enabling tracing can increase resource usage. If the server is already under heavy load, this might cause startup issues.

Permissions:

The account running the NAV Server might not have sufficient permissions to write to the trace log file.

NAV Service Tier Configuration:

If the NAV Service Tier configuration is not aligned with the WCF tracing setup, it can cause conflicts.

Solutions

Validate web.config Changes:

Double-check the changes made to the web.config file. Ensure that all <system.diagnostics> and <trace> elements are correctly configured.

Check Trace Log Path:

Verify that the file path specified for the trace logs is valid and accessible by the NAV Server account.

Test with Minimal Tracing:

Start with minimal tracing settings (e.g., only critical errors) to reduce resource usage and identify the issue.

Review Event Logs:

Check the Windows Event Viewer for any error messages related to the NAV Server startup. This can provide clues about the root cause.

Restore Default Configuration:

If the issue persists, revert the web.config file to its original state and restart the server. Then, reapply the tracing settings step by step.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 20,439 Super User 2025 Season 2 on at

Like (2)

Report

If this helps:https://www.microsoft.com/en-us/dynamics-365/blog/no-audience/2011/01/20/enabling-diagnostic-tracing-for-dynamics-nav-web-services/

Was this reply helpful? Yes No
Suggested answer

Mansi Soni 8,907 Super User 2025 Season 2 on at

Like (3)

Report

Hello, May this resources can help as well

http://navhelp.modst.dk/help/da-dk/conMicrosoftDynamicsNAVTraceEvents.htm
https://www.microsoft.com/en-us/dynamics-365/blog/no-audience/2011/01/20/enabling-diagnostic-tracing-for-dynamics-nav-web-services

Regards,
Mansi Soni

Was this reply helpful? Yes No
Vahid Ghafarpour 12,116 Super User 2025 Season 2 on at

Like (1)

Report

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No