Trace directory null after Dynamics 365 Upgrade

(0) Share

Report

Posted on by J Matlon

1,465

After upgrading CRM 2016-> Dynamics 365 (On Prem) I can't drill into any records. I will just get the message "Requesting data from Dynamics 365".

In the application log, I am getting an error about an Invalid Trace Directory, and the Trace Directory is null.

I've checked the trace directory in the config database, powershell, and the registry settings... they are all set to "C:\Program Files\Microsoft Dynamics CRM\Trace". This directory does exist, and the user running our CRM app pool has write access to this folder.

Is there anything else that I could be missing?

*This post is locked for comments

All responses (2)

Answers (1)

MohamedRamadan on at

Like (0)

Report

RE: Trace directory null after Dynamics 365 Upgrade

We are facing the same issue when we upgraded to Dynamics CRM 365 (9.0) on premise. However, I doubt that it is related to the "legacy form rendering" setting.

If will be helpful if you can specify the server changes trials that Microsoft did for you, so we can try it and we figure the issue solution.

Thanks.
Verified answer

J Matlon 1,465 on at

Like (1)

Report

RE: Trace directory null after Dynamics 365 Upgrade

I had to submit a ticket to MS on this one.

The issue still wasn't clear. We played with some settings, and nothing was fixed. Then we played with the "legacy form rendering" setting, and the issue appeared resolved.

We set the "legacy form rendering" back to normal (off), then cleared browser settings, and the issue went away.

This was very strange, since all users were experiencing the issue. But we couldn't quite place what the server change was that made things work again.