Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The Windows Azure Pack Tenant Portal does not display installed templates


View products that this article applies to.

Symptoms

The Windows Azure Pack Tenant Portal (WAP Tenant Portal) may not display installed templates and may return a value of None in the Select template dialog box. This behavior may occur intermittently or when you add lots of templates.

For example, consider the following scenario:
  • A WAP Admin Portal is linked to three instances of Microsoft System Center Virtual Machine Manager. 
  • There are seven plans that are configured, 145 subscriptions that are associated with those plans, and 12 (out of a possible 312) templates that are added to each plan. 
  • You add between 80 and 160 templates to four of the plans that are linked to the Admin Portal.
  • You try to deploy a new virtual machine (VM).
In this scenario, after an hour or more, the WAP Tenant Portal starts showing None for the list of virtual machine (VM) templates to be built. 

Note To identify your Tenant API server, look for the virtual website MgmtSvc-TenantAPI in Internet Information Services (IIS) Manager. By default, the service listens on port 30005.

↑ Back to the top


Cause

The WAP Tenant API has a default time-out of 100 seconds.  If System Center Service Provider Foundation (SPF) cannot provide the complete template data to the Tenant Portal within the time-out that is configured by the OutgoingCallsDefaultTimeoutInSeconds value, the list of templates is not displayed.

↑ Back to the top


Resolution

To work around this issue, increase the time-out in the Tenant API web.config file. To do this, follow these steps:
  1. Make a backup copy of the Tenant API web.config file. (By default, this file is located in C:\Inetpub\MgmtSvc-TenantAPI.)
  2. Unprotect the web.config file by running the following command from an elevated Windows PowerShell Command Prompt window on the Tenant API server: 
    Unprotect-MgmtSvcConfiguration -NameSpace TenantAPI 
  3. Edit the web.config file to change the following value as follows: 
    <add key="OutgoingCallsDefaultTimeoutInSeconds" value="500"/>
  4. Restart the Tenant API APP Pool in IIS on the WAP Tenant API computer.
  5. Re-protect the file by running the following command: 
    Protect-MgmtSvcConfiguration -NameSpace TenantAPI
  6. Close all open Internet Explorer windows, and then retest.
After this change, you see the full list of VM templates on the Tenant site.

↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 3044159
Revision : 2
Created on : 3/27/2020
Published on : 3/27/2020
Exists online : False
Views : 359