Friday, 25 November 2016

503 Eror When Configuring CRM 2016 Using PowerShell

When configuring claims / certificates using CRM and PowerShell I was getting the following error:
The remote server returned an error: (503) Server Unavailable
AND
Fail to configure Microsoft Dynamics CRM to use the specified certificate.


I noticed that the Application Pool Service CrmDeploymentServiceAppPool had stopped.


Turns out the service account had Log on as Service enabled but not log on as a batch! Rookie mistake but CRM was working fine (with the AppPool started) so I hadn't noticed it!

No comments: