locked
Exchange 2016 Unable to edit virtual directory settings RRS feed

  • Question

  • Hi Friends.. I need your help to get my the below issue resolved. I had installed new exchange 2016  post installing when i try editting  the virtual directory settings i am getting below error
    "
    The version of Internet Information Services (IIS) that is running on server can't be determined. This error can occur due to network connectivity issues. Check the availability of your network and try again. Parameter name: Server"

    If someone faced this issue please let me know.. and important note all required exchange services are running fine and dependent services as well


    Thanks Sekhar

    Monday, September 11, 2017 4:18 PM

All replies

  • What Version of Windows is the server running?

    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.

    Monday, September 11, 2017 6:50 PM
  • Windows 2016 standard version.

    Thanks Sekhar

    Monday, September 11, 2017 7:20 PM
  • What CU of Exchange are you running? There are issues below CU3?

    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.

    Monday, September 11, 2017 7:26 PM
  • Newly installed Exchange 2016 Cu5 

    Thanks Sekhar

    Monday, September 11, 2017 7:42 PM
  • Can you disable windows firewall and restart the server and test?

    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.

    Monday, September 11, 2017 7:46 PM
  • All those steps are completed... 

    Thanks Sekhar

    Monday, September 11, 2017 7:49 PM
  • OK so what steps have you completed? It will help troubleshooting if we know what you have done?

    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.

    Monday, September 11, 2017 7:52 PM
  • Windows Firewall has been Turned off.

    Ensure required services like Exchange, IIS , remote registry and IKE and AuthIP IPsec Keying Module are started.

    No errors on windows log to move ahead. 


    Thanks Sekhar

    Monday, September 11, 2017 8:01 PM
  • I've generally only seen this issue with either firewall, nlb or services not started.If they are started and there are still issues I would expect something in the logs.

    Outside of that the issue could be larger than just this server (DNS, network etc.)


    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.

    Monday, September 11, 2017 8:08 PM
  • I am seeing below is the only error and the fix for the below error is to enable Ipv6 which is already there in my system

    Process ExSetupUI.exe (PID=6380). WCF request (Get Servers for contoso.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details 
     System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0469476. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       --- End of inner exception stack trace ---

    Server stack trace: 
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at System.ServiceModel.ICommunicationObject.Open()
       at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Int32 retry, Boolean& doNotReturnProxyAfterRetry, Boolean useCache)
       at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)


    Thanks Sekhar

    Monday, September 11, 2017 8:16 PM
  • Hi,

    Based on your description, I know that you got the error above when you edit the VD settings.

    To narrow the issue, I need to confirm:
    Did you get the error when you edit the VD settings in EAC? Could you edit them via commands?

    According to the error message in your last post, Issue may be arisen by the port 890 and related services. 

    For troubleshooting:
    1. Make sure that Microsoft Exchange Active Directory Topology service is running.
    2. Run nltest /dsgetsite in Windows Powershell and check if the Exchange server has been assigned to a site. If no, we could add a register key under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters, see figure below:


    3. run prepareAD: run setup /prepareAD /ActiveDirectorySplitPermissions:true in Windows Powershell.

    If issue remains, feel free to post back!


    Best Regards,

    Manu Meng
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Tuesday, September 12, 2017 8:57 AM
    Moderator