Condividi tramite

VMM SSP 2.0 web site cannot communicate with the server component

  • Articolo

Sometimes you might observe an error while you are trying to peform certain operations in the website that attempt to communicate with the server component. The error will look similar to the one below:

What this means is that the VMM SSP 2.0 web site initiated a communication with the VMM SSP 2.0 server component and the communication did not succeed. The communication fails typically due to the following reasons:

1. The Service with display name: Virtual Machine Manager Self Service Portal 2.0 is not running.

2. The Web site is trying to communicate with the server component on a different TCP port than what the Service is configured to listen at.

3. The user principal name defined in the Web component does not match the service account under which the Service is running as.

4. Perhaps your firewall is getting in between and blocking the outgoing / incoming requests.

Here is how you verify/resolve each of these conditions:

1. Service Status

On the machine where you deployed the Server component, open service control manager by typing services.msc at Start -> Run. Identify the service with display name: Virtual Machine Manager Self Service Portal 2.0 and make sure its running. If not, please start it.

2. TCP port

a. Open the Web.Config file found in the <installationfolder>\Portal sub folder on a machine where the web component was deployed and make sure towards the end of the web.config file has the following section defined:

      <endpoint address="net.tcp://<machinename>:8000/" binding="netTcpBinding" bindingConfiguration="serviceEndPoint" contract="DDTKServiceReference.IDDTKService" name="serviceEndPoint">

        <identity>

          <userPrincipalName value="serviceaccount@domain.com"/>

        </identity>

      </endpoint>

Please make sure the machine name and port are the same as you specified during installation. Secondly make sure the user principal name reflects the current service account of the VMM SSP 2.0 service running on the machine where you deployed the Server component.

If you do not remember the TCP port number you specified during installation, you can always retrieve from the Microsoft.DITSC.ProvisioningService.exe.config file found in the <installationfolder>/Service subfolder. After you open this file, please scroll down to the bottom and you will find:

        <endpoint address="net.tcp://localhost:8000" binding="netTcpBinding" bindingConfiguration="tcpBinding" name="tcpEndPoint" contract="Microsoft.DDTK.ServiceContracts.IDDTKService"/>

The TCP port number above should match the TCP port number defined in the web.config file.

3. User principal name – Same as #2 above

4. Firewall - I will leave that to you.

I hope the troubleshooting in this post will help you establish the communication between the VMM SSP 2.0 web site and the server component.

Note: This applies to the VMM SSP 2.0 RC release.

Thanks,

Sai Kodi