We have a separate Publisher and CMS machine. While installing DXA 2.0, we are installing the Resolver using the command .\cms-customresolver.ps1. (btw, while running with .\cms-customresolver.ps1 -distDestination "C:\Program Files (x86)\SDL Web" we got an error 'A parameter cannot be found that matches parameter name 'distDestination'')

It worked fine on the CMS, but at the end it gave us an error that it could not restart the Publisher service (we have it disabled on the CMS, since we have a separate Publisher box).

Do we need to install it again on the Publisher machine? Do we still need to have it installed on the CMS (that doesn't have a Publisher)?


In general, Resolvers are used by the Publisher Service to resolve a publish action on a source item into zero or more items to be rendered.

So, yes, custom Resolvers should be installed on all Publisher boxes.

Resolvers are also used by the CME if the user presses the “See items to publish” button on the Publish Dialog. So, you should also install those on CME boxes.


Seems to look like documentation reference parameter was wrong.

Correct Command:

.\cms-customresolver.ps1 -extensionTargetFolder DxaExtensionPath -cmSiteName SITENAME 


 .\cms-customresolver.ps1 -extensionTargetFolder "C:\Program Files (x86)\SDL Web\web\WebUI" -cmSiteName "SDL Web"

cms-customresolver script adds the DXA Custom Resolver to the CMS/Publishing server's GAC and modifies the Tridion.ContentManager.config (suitable for R2 mapping only)

Indeed, Rick already answered, yes we need to install all the CME and Publishers servers.

  • Please create a comment on the documentation topic for this documentation defect. Jun 26 '18 at 20:39
  • Yes. I did already
    – Velmurugan
    Jun 26 '18 at 20:40
  • Oh, sorry, I didn’t even check. :-) Jun 26 '18 at 20:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.