web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Cannot enable tracing getting error 404

(0) ShareShare
ReportReport
Posted on by 100

So, I have followed the instructions in KB 907490 (how to enable tracing inMicrosoft Dynamics CRM) but I cannot get it to work. The powershell snapin is registered and adds in fine, but when I run Get-CrmSetting TraceSettings (or any other category under Get-CrmSetting) I get the following error:

get-crmsetting : The remote server returned an error: (404) Not Found.
At line:1 char:1
+ get-crmsetting tracesettings
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (Microsoft.Crm.P...rmSettingCmdlet:GetCrmSettingCmdlet) [Get-CrmSetting
   ], WebException
    + FullyQualifiedErrorId : CRM Deployment Cmdlet Error,Microsoft.Crm.PowerShell.GetCrmSettingCmdlet

I have googled this for days with no result. Some solutions state that the FQN of the site is not correct in the registry, so I passed -dwsserverurl to the command (with creds of course) and then I get a 401 unauthorized instead. We are using the default applicationpoolidentity as opposed to a service account, so as far as I know permissions shouldn't be an issue. I am not even 100% sure what the dws server url is supposed to be. I am new to CRM. I suspect it might have something to do with SPNs but I didn't think they'd require configuration because we are not using kerberos and I went with the default applicationpoolidentity users (NETWORK SERVICE I believe) on install.

If anyone has any thoughts on this I would really appreciate any help, sorry I am so green.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Royal King Profile Picture
    27,686 on at

    Use the tool from codeplex  to enable /disable tracing on the CRM server

    crmdiagtool2011.codeplex.com

    This tool is built for 2011 but it works for 2013 as well. You have run this tool within CRM server.

  • Dale Metcalfe Profile Picture
    100 on at

    Thank you so much! That worked perfectly. Wow, that was so fast. Its so funny that what has stumped me for days was solved in minutes. That's why you go to the pros. Thanks again!

  • Dale Metcalfe Profile Picture
    100 on at

    I guess I should ask just in case, there is no danger of causing issues with the CRM deploy just enabling and disabling trace with this tool is there? Is it just a front end for the powershell commands or is it poking the registry directly?

  • Royal King Profile Picture
    27,686 on at

    This tool updates the registry keys to enable/disable tracing.

  • Dale Metcalfe Profile Picture
    100 on at

    Again thank you, that worked perfectly as I said. Now I am being asked to get the powershell working though, in case we need it for more granular control of CRM settings...so I still need a solution for that 404 problem. Any ideas or should I create a new thread?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans