The program w3wp.exe, with the assigned process ID, could not authenticate locally by using the target name HTTP/WEBSITENAME.

You may face this error when you are running your development environment on virtual server where you have also configured alternate access URL-s.The full message is something like this: The program w3wp.exe, with the assigned process ID, could not authenticate locally by using the target name HTTP/WEBSITENAME. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name. Try a different target name.

applocix blog posting w3wp.exe unable to authenticate on target name helps us out:

  1. Go to REGEDIT and open the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  2. Right click MSV1_0 –> New -> Multi-String Value
  3. Type BackConnectionHostNames and click Enter.
  4. Right click on newly created value and select Modify.
  5. Enter the hostname of the site: WEBSITENAME (and on a new line enter the FQDN, WEBSITENAME.domain.com)
  6. Restart IIS

This way I got my internet zone host name work on my virtual server.

Gunnar Peipman

Gunnar Peipman is ASP.NET, Azure and SharePoint fan, Estonian Microsoft user group leader, blogger, conference speaker, teacher, and tech maniac. Since 2008 he is Microsoft MVP specialized on ASP.NET.

    7 thoughts on “The program w3wp.exe, with the assigned process ID, could not authenticate locally by using the target name HTTP/WEBSITENAME.

    • December 27, 2013 at 9:27 pm
      Permalink

      This is a live saver !

      Thanks for the tip, solved my issues.

    • January 10, 2014 at 5:30 pm
      Permalink

      Thanks so much!

    • February 28, 2014 at 6:03 pm
      Permalink

      Great! Thank you.

    • July 23, 2015 at 7:36 pm
      Permalink

      Efectivo, muchas gracias, sin embargo, me pregunto, que hice mal ????

    • September 11, 2015 at 4:57 pm
      Permalink

      Bingo! Helped me a lot. Thanks for great help!

    • November 11, 2015 at 1:55 pm
      Permalink

      I’ve been struggling to set up a test multi-tenant Dynamics NAV environment with tenants specified with alternate access urls (alternative tenant id). I couldn’t get a OData connection working with the tenants. Your post was the answer to my problem! Thank you very much.

    • July 29, 2016 at 5:06 am
      Permalink

      Thanks it helped to resolve MIM 2016’s Service unavailable issue

    Leave a Reply

    Your email address will not be published. Required fields are marked *