NAV 2017 Web Server install error

tarkmylertarkmyler Member Posts: 57
Hi folks - I'm having no luck getting the NAV 2017 web server installed on a Windows Server 2012 r2 box. The NAV 2017 service tier, and SQL 2014 are running on the same server (very small customer). The sequence is install, error, rollback. This is a system that had the NAV 2013r2 web server running before upgrade.
I have removed and re-installed IIS in the process of trying to fix the issue. After rooting around in the event log I came up with a WIX log that complains about not finding Powershell 3.0 - The server has powershell 4.0 and 2.0 installed via windows features, with no option for powershell 3.0.

I found a wix log file related to the installation that contains the following line (log file attached) ...

Property(S): NAV_POWERSHELL_MESSAGE = Microsoft Dynamics NAV Setup cannot complete because an installation prerequisite is missing: Windows PowerShell 3.0. You must install the relevant prerequisite before you continue with Microsoft Dynamics NAV Setup. For more information, see http://go.microsoft.com/fwlink/?LinkId=317819.

In the windows application log - I'm seeing a message that says ...

Type: Microsoft.Dynamics.Nav.Management.Exceptions.NavCommandException
SuppressMessage: False
SuppressExceptionCreatedEvent: False
FatalityScope: None
Message: <ii>A web server instance already exists.</ii>

I am not sure if they are related, but one happened at the same time as the other...
Any suggestions would be appreciated!
Mark Tyler
Pacific City, OR


  • Options
    tarkmylertarkmyler Member Posts: 57
    edited 2017-05-31
    So... this issue persists and appears to have nothing to do with powershell. I found this posting on another site...


    It appears that the error log showing "New-NavWebServerInstance : A web server instance already exists" is the real issue. I have uninstalled NAV 2013r2 and NAV 2017 web server components.

    Still no love.

    Any idea where New-NAVWebServerInstance goes looking for instances?
    Mark Tyler
    Pacific City, OR
  • Options
    tarkmylertarkmyler Member Posts: 57
    Still no love here... I managed to clean up everything and get a different message from New-NAVWebServerInstance - see log file below and snippet with highlighted message.

    ExecFirewallExceptions: Installing firewall exception2 Microsoft Dynamics NAV 2017 Web Client on port 8080, protocol 6
    WixCreateInternetShortcuts: Creating IUniformResourceLocatorW shortcut 'C:\Users\sysadmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Dynamics NAV 2017 Web Client.url' target 'http://localhost:8080/DynamicsNAV100/WebClient'
    CAQuietExec64: OK.
    CAQuietExec64: WARNING: UnhandledErrorMessage
    CAQuietExec64: New-NavWebServerInstance : Some or all identity references could not be translated.

    CAQuietExec64: At C:\Program Files\Microsoft Dynamics NAV\100\Web Client\Bin\WebServerInstance.ps1:45 char:1
    CAQuietExec64: + New-NavWebServerInstance @arguments
    CAQuietExec64: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CAQuietExec64: + CategoryInfo : NotSpecified: (:) , IdentityNotMappedException
    CAQuietExec64: + FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Dynamics.Nav.Management.C
    CAQuietExec64: mdlets.NewNavWebServerInstance
    CAQuietExec64: Error 0x80070001: Command line returned an error.
    CAQuietExec64: Error 0x80070001: CAQuietExec64 Failed
    CustomAction CreateWebApplication returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 10:30:37: InstallFinalize. Return value 3.
    Mark Tyler
    Pacific City, OR
  • Options
    NavNabNavNab Member Posts: 181
    Hi Mark,

    Open IIS and stop NAV 2013 R2 web client instance.

    I know that you already uninstalled NAV 2013 R2 also reinstalled IIS and all the stuff... but I believe the site (the web client) on IIS remains and it binds to port 8080.

    The first error you got before you uninstalled NAV 2013 R2 is because NAV 2013 R2 instance was running. You should have just stop it and NAV 2017 would install smoothly ;)

    I hope this will help
Sign In or Register to comment.