What is the parent portal Appalnet

Failed to schedule synchronization and quota update in Windows Azure Pack Management Portal

  • 3 minutes to read

This article will help you resolve an issue that causes bad errors in the Schedule synchronization and the Quota update when you delete users or subscriptions in the WAP Management Portal (Windows Azure Pack).

Original version of the product: Microsoft System Center 2012 R2 Virtual Machine Manager, Windows Azure Pack (on Windows Server 2012 R2), System Center 2012 Virtual Machine Manager
Original KB number:   3056677

Problem Description

If you try to delete users or subscriptions in the WAP Management Portal (Windows Azure Pack), the action might fail. Errors you may receive are faulty Messages with Plan out of sync and quota update. If you try to delete a subscription, you might get one too no subscription is assigned to the client error .

Debug logs contain errors that are similar to the following:

One or more errors occurred while contacting the underlying resource providers. The process may be partially complete.

Details: The subscription could not be created. Reason: Message:

or

The subscription could not be deleted. Cause: Message: The underlying connection was closed: There is an unexpected error in a send., InnerMessage: No data could be read from the transport connection: an existing connection was forcibly closed by the remote host.

Error messages referring to empty subscription IDs can also indicate this condition. (These error messages are displayed as " Subscription- "= [] shown.)

root cause

This problem can occur when there are multiple bindings for port 8090 in the Internet Information Server (IIS) settings of the Service Provider Foundation (SPF) server.

solution

To resolve this issue, make sure that the bindings for port 8090 are correct on the SPF server. By default, there should be a single HTTPS binding on port 8090. If there are multiple bindings, remove duplicate entries and make sure that the binding is set to listen on all IP addresses.

There are two bindings in the screenshot below. The second entry for HTTPS 8090 should be removed.

additional Information

Debug logging may display errors that are similar to the following:

2 [0] 0D2C. 0754 :: 2015-03-27 15: 09: 21.042 [ActivityEventSource] Started Activity [HttpRequest, ID {8ab952bd-c43f-4ded-B173-50d4055f9341}] parent activity [web authentication call, ID {4659b10b-cf3a-4bcc-9769- f6e1b8663fe5}] elapsed: 0ms Context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} Properties: requestURL = [https: //wapserver.contoso.local: 8090 / provider / subscriptions] & x-MS-Client-Request-ID = [e8dbc04c-5381-40ba-8909-69b83a4f3f13] & x-MS-Client-Session-ID = [99459df3-bb71-4f30-9315-1b0c6c916a58]

3 [0] 0D2C. 0754 :: 2015-03-27 15: 09: 21.058 [ActivityEventSource] successfully completed activity [HttpRequest, ID {8ab952bd-c43f-4ded-B173-50d4055f9341}] parent activity [web authentication call, ID {4659b10b-cf3a-4bcc-9769 -f6e1b8663fe5}] passed: 0ms context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} Duration: 124ms Properties: OriginalPath = [/ Provider / Subscriptions] & requestURL = [https: //wapserver.contoso.local: 8090 / provider / subscriptions] & Subscription ID = [] & x-MS-Client-Request-ID = [e8dbc04c-5381-40ba-8909-69b83a4f3f13] & x-MS-Client-Session-ID = [99459df3-bb71-4f30-9315 -1b0c6c916a58]

4 [1] 0D2C. 0754 :: 2015-03-27 15: 09: 24.406 [Microsoft-ServiceProviderFoundation] Component: Provider activity [Web authentication call, ID {4659b10b-cf3a-4bcc-9769-f6e1b8663fe5}] parent activity [None, ID {00000000-0000- 0000-0000-000000000000}] passed: 0ms context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} Creating clients and linking them with the stamp client name: [email protected]_a7c63b17-c0fb-48bf-bdc4-5f10b1c26

5 [0] 0D2C. 0754 :: 2015-03-27 15: 09: 24.484 [Microsoft-ServiceProviderFoundation] Component: Provider activity [Web authentication call, ID {4659b10b-cf3a-4bcc-9769-f6e1b8663fe5}] parent activity [None, ID {00000000-0000- 0000-0000-000000000000}] passed: 0ms Context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} the subscription could not be deleted. Cause: Message: The underlying connection was closed: There is an unexpected error in a send., InnerMessage: No data could be read from the transport connection: an existing connection was forcibly closed by the remote host.

6 [0] 0D2C. 0754 :: 2015-03-27 15: 09: 24.489 [Microsoft-ServiceProviderFoundation] Component: Provider activity [Web authentication call, ID {4659b10b-cf3a-4bcc-9769-f6e1b8663fe5}] parent activity [none, ID {00000000-0000- 0000-0000-000000000000}] elapsed: 0ms context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} under system .net. HttpWebRequest. GetResponse () under System. Data. Services. Client. webutil. GetResponseHelper (ODataRequestMessageWrapper request, DataServiceContext context, IAsyncResult AsyncResult, Boolean handleWebException) under System.Data.Services.Client.DataServiceRequest.Execute TElement [under] (DataServiceContext context, QueryComponents) queryComponents. Data. Services. System.Data.Services.Client.QueryResult.ExeClient. DataServiceQuery `1.Execute () under System. Data. Services. Client. DataServiceQuery `1. GetEnumerator () under System. Linq. Enumerable. FirstOrDefault [TSource] (IEnumerable`1 source) under System. Data. Services. Client. DataServiceQueryProvider. ReturnSingleton [TElement] (Expression expression) under System. Linq. Queryable. FirstOrDefault [TSource] (IQueryable`1 source) under Microsoft.SystemCenter. Foundation. Provider. SubscriptionResourceProvider. DeleteSubscription (string ID)

7 [0] 0D2C. 0754 :: 2015-03-27 15: 09: 24.490 [Microsoft-ServiceProviderFoundation] Component: Provider activity [Web authentication call, ID {4659b10b-cf3a-4bcc-9769-f6e1b8663fe5}] parent activity [None, ID {00000000-0000- 0000-0000-000000000000}] passed: 0ms context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} the underlying connection was closed: unexpected error when sending.

8 [0] 0D2C. 0754 :: 2015-03-27 15: 09: 24.491 [Microsoft-ServiceProviderFoundation] Component: Provider activity [Web authentication call, ID {4659b10b-cf3a-4bcc-9769-f6e1b8663fe5}] parent activity [None, ID {00000000-0000- 0000-0000-000000000000}] passed: 0ms context: {c477a2fb-8864-4d89-96c7-24bdccee5b94} Message: the underlying connection was closed: an unexpected error during a send., InnerMessage: No data could be read from the transport connection be: an existing connection was forced by the remote host

For more information on debug logging, see the following articles: