How to solve "get-crmsetting : The remote server returned an error: (404) Not Found."

(0) Share

Report

Posted on by Dale Metcalfe

100

So, Chitrarasan Duraisamy was nice enough to point me to a tool that enables tracing for diagnostics in CRM which was excellent, and his response was very quick. Now, I am able to enable and disable tracing but the powers that be want to know why powershell puts out a 404 not found error when I use the get-crmsettings command. I followed the instructions for configuring powershell for CRM in KB 907490 but when I run get-crmsetting commands I get:

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 need to be able to administer this deploy of CRM 2013 with powershell. 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. Does anyone have any thoughts on how to solve this? Thank you.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

AFTAB HUSSAIN on at

Like (0)

Report

Hello Dale,

Refer to the link - community.dynamics.com/.../148644.aspx

Hope this helps.

Thank You !

Was this reply helpful? Yes No
Suggested answer

Jeff Dodds 50 on at

Like (1)

Report

I was experiencing the same issue, basically any of the CRM commandlets would give me a 404 result.

I used fiddler to attach to the process and see the URL it was getting a 404 when connecting to. Accessing the URL directly in a browser revealed that it was specifically a 404.8 (The request filtering module is configured to deny a path in the URL that contains a hiddenSegment section.).

IIS on the CRM Front End server had the XrmDeployment folder set to be a HiddenSegment in Request Filtering. Removing that allowed all the commands to run properly.

I hope this helps someone. :)

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi,

I can't give an exact answer since I don't know the details of your environment but usually this happens when you have a host header present in the Host name field under the Microsoft Dynamics website > Bindings > <your binding> (443)

You need to leave the Host name field blank and let CRM handle the addresses for his WebAddress settings not from IIS, like below.

After doing this Powershell will be able to resolve the endpoint, no 404.

Hope this helps !

Regards,

Razvan

Was this reply helpful? Yes No
Abdul Wahab 12,119 Moderator on at

Like (1)

Report

Hi Jeff Dodds

I navigate to below but unable to find HiddenSegment in Request Filtering.

Please help me to solve this navigation issue.

Thank you

Was this reply helpful? Yes No
Jeff Dodds 50 on at

Like (1)

Report

Hi Abdul,

What I meant was after you open the Request Filtering Module, click on the Hidden Segments tab then select and remove the XRMDeployment segment.

The environment pictured I haven't had a need to use PowerShell against which is why I haven't bothered to remove it as of yet. Hope that helps.

Jeff

Was this reply helpful? Yes No
Dmitri 34 on at

Like (0)

Report

In my case I found the "XRMDeployment" only on the server with front end server role. Removing it from the server resolved the problem there and on the server with back end role.

Was this reply helpful? Yes No