INTRODUCTION
Cumulative update package 2 is available for Microsoft AppFabric 1.1 for Windows Server. This update package resolves an issue that is described in the "More Information" section.
This cumulative update includes all the fixes that were included in Cumulative Update 1 for Microsoft AppFabric 1.1 for Windows Server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2671763 Cumulative update package 1 for Microsoft AppFabric 1.1 for Windows Server
More Information
For more information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Issue that is fixed in this update
Microsoft AppFabric 1.1 for Windows Server crashes when an anonymous client tries to access it.
Note For more information about the stack trace that is generated when this issue occurs, see the "References" section.
Known issue with Cumulative Update for Microsoft AppFabric 1.1 for Windows Server
Important This update applies to the caching functionality of AppFabric 1.1 only. We recommend that you install the update only on servers that are running the AppFabric cache or that are using the AppFabric cache client.
Issue
After you install the update, the AppFabric Configuration Wizard incorrectly reports the status of the Persistence and Monitoring configuration as "Not configured." Additionally, the user interface status is incorrect.
To verify that the services are running, follow these steps:
-
Open the Powershell administration console.
-
Run the Get-ASAppMonitoring –Root command to verify the configuration of the state.
-
Run the Get-ASAppInstanceStore –Root command to verify the instance store connection strings.
This issue can safely be ignored as it does not affect the functionality of either AppFabric Hosting Services or the services that are hosted by AppFabric Hosting Services.
How to obtain Cumulative Update 2 for Microsoft AppFabric 1.1 for Windows Server
Cumulative update package information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this cumulative update package, you must have Microsoft AppFabric 1.1 for Windows Server installed.
Restart requirement
You may have to restart the computer after you apply this cumulative update package.
File information
The English version of this cumulative update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Microsoft AppFabric 1.1 for Windows Server
|
File name |
File version |
File size |
Date |
Time |
Platform |
|
Distributedcacheadministration.psd1 |
Not Applicable |
915 |
29-May-12 |
17:58 |
Not Applicable |
|
Distributedcacheadministration.psm1 |
Not Applicable |
13,573 |
29-May-12 |
23:15 |
Not Applicable |
|
Distributedcacheconfiguration.psd1 |
Not Applicable |
590 |
29-May-12 |
17:58 |
Not Applicable |
|
Distributedcacheconfiguration.psm1 |
Not Applicable |
11,490 |
29-May-12 |
23:15 |
Not Applicable |
|
Microsoft.applicationserver.caching.client.dll |
1.0.4644.0 |
178,456 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.configuration.dll |
1.0.4644.0 |
92,456 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.configuration.dll-help.xml |
Not Applicable |
70,762 |
29-May-12 |
20:20 |
Not Applicable |
|
Microsoft.applicationserver.caching.configuration.resources.dll |
1.0.4644.0 |
17,216 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.core.dll |
1.0.4644.0 |
837,912 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.managementps.dll |
1.0.4644.0 |
84,264 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.managementps.dll-help.xml |
Not Applicable |
176,671 |
29-May-12 |
17:57 |
Not Applicable |
|
Microsoft.applicationserver.caching.server.dll |
1.0.4644.0 |
444,696 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.configuration.exe |
1.1.2116.2 |
715,032 |
29-May-12 |
20:49 |
x86 |
|
Setup.exe.config |
Not Applicable |
235 |
29-May-12 |
18:00 |
Not Applicable |
For all supported x64-based versions of Microsoft AppFabric 1.1 for Windows Server
|
File name |
File version |
File size |
Date |
Time |
Platform |
|
Distributedcacheadministration.psd1 |
Not Applicable |
915 |
29-May-12 |
17:58 |
Not Applicable |
|
Distributedcacheadministration.psm1 |
Not Applicable |
13,573 |
31-May-12 |
18:26 |
Not Applicable |
|
Distributedcacheconfiguration.psd1 |
Not Applicable |
590 |
29-May-12 |
17:58 |
Not Applicable |
|
Distributedcacheconfiguration.psm1 |
Not Applicable |
11,490 |
31-May-12 |
18:26 |
Not Applicable |
|
Microsoft.applicationserver.caching.client.dll |
1.0.4644.0 |
178,456 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.configuration.dll |
1.0.4644.0 |
92,456 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.configuration.dll-help.xml |
Not Applicable |
70,762 |
29-May-12 |
20:20 |
Not Applicable |
|
Microsoft.applicationserver.caching.configuration.resources.dll |
1.0.4644.0 |
17,216 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.core.dll |
1.0.4644.0 |
837,912 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.managementps.dll |
1.0.4644.0 |
84,264 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.caching.managementps.dll-help.xml |
Not Applicable |
176,671 |
29-May-12 |
17:57 |
Not Applicable |
|
Microsoft.applicationserver.caching.server.dll |
1.0.4644.0 |
444,696 |
29-May-12 |
20:49 |
x86 |
|
Microsoft.applicationserver.configuration.exe |
1.1.2116.2 |
715,032 |
29-May-12 |
20:49 |
x86 |
|
Setup.exe.config |
Not Applicable |
235 |
29-May-12 |
18:00 |
Not Applicable |
References
For more information about Microsoft AppFabric 1.1 for Windows Server, visit the following MSDN website:
General information about Microsoft AppFabric 1.1 for Windows ServerWhen this issue occurs, the following stack trace information is included in an error event of an AppFabric event log:
AppFabric Caching service crashed with exception {System.Runtime.CallbackException: Async Callback threw an exception. ---> System.IdentityModel.Tokens.SecurityTokenValidationException: The service does not allow you to log on anonymously.
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.CommunicationObject.EndOpen(IAsyncResult result)
at Microsoft.ApplicationServer.Caching.WcfServerChannel.OnOpen(IAsyncResult result)
at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
--- End of inner exception stack trace ---
at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
at System.Runtime.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
at System.ServiceModel.Channels.ServerSessionPreambleConnectionReader.ServerFramingDuplexSessionChannel.OpenAsyncResult.OnUpgradeConnection(IAsyncResult result)
at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
at System.ServiceModel.Channels.InitialServerConnectionReader.UpgradeConnectionAsyncResult.OnAcceptUpgrade(IAsyncResult result)
at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
at System.ServiceModel.Channels.StreamSecurityUpgradeAcceptorAsyncResult.OnAuthenticateAsServer(IAsyncResult result)
at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.Security.NegoState.WriteCallback(IAsyncResult transportResult)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)}. Check debug log for more information
