[Appfabric 1.1 For Windows Server 64 Msi Download
Hanne Rylaarsdam
This article describes Cumulative Update 7 (KB 3092423) for Microsoft AppFabric 1.1 for Windows Server. This update package fixes several issues that affect the caching and hosting services that are provided by AppFabric 1.1. For more information about these issues, see the "More Information" section.
This cumulative update includes all the features and fixes that were included in earlier cumulative updates for AppFabric 1.1 for Windows Server. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
The following file is available for download from the Microsoft Download Center:
Download the package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
{System.Runtime.CallbackException: Async Callback threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
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)
After you apply this cumulative update, AppFabric uses a nonblocking garbage collection (background server garbage collection). Nonblocking garbage collection is a new feature in the Microsoft .NET Framework 4.5.
To enable this feature, follow these steps:
When you uninstall any cumulative update for Microsoft AppFabric 1.1, you may see a dialog box that states "The feature you are trying to use is on a network resource that is unavailable." In this situation, the cumulative update will not be uninstalled. To work around this issue, follow these steps:
When you now try to uninstall the cumulative update and are prompted for the location of the MSI, you can point it to the "packages" subfolder in the copy of the temporary directory that you created (such as to "c:\appfabrictempfiles\packages"), and the uninstallation should be successful.
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.
A few weeks back I blogged about the Windows Server AppFabric launch (AppFabric is Microsoft's "Application Server") and a number of folks had questions about how to install and configure the "Velocity" memory cache. It used to be kind of confusing during the betas but it's really easy now that it's released.
Have you tried to setup a appfabric (velocity) instance ? I suggest you try & even do a blog post, maybe under the scenario of using it like a memcache for dasblog. I would love to know how to setup it up, it's crazy hard for what it is.
Run the installer and select AppFabric Cache. If you're on Windows 7, you'll want to install the IIS 7 Manager for Remote Administration which is a little plugin that lets you manage remote IIS servers from your Windows 7 machine.
The configuration tool will pop up, and walk you through a small wizard. You can setup AppFabric Hosting Services for Monitoring and Workflow Persistence, but since I'm just doing Caching, I'll skip it.
The Velocity Caching Service needs to know where to get its configuration and it can get it from one of two places - either a database or an XML file on a share. If you use the XML file on a share, you'll need to make sure the service account has access to the share, etc. I'll use a database. The config wizard can make it for you as well. Click Next then Finish up the configuration.
Now what? Go to the Start Menu and type in Caching. You'll have an item called "Caching Administration Windows PowerShell." This is where you can connect to the cache, check out what's going on, make new caches, etc. Run it as Administrator.
Cool, it's up and running. If you look in the config database (or the XML file if you chose that) you'll see that I have one machine in my memory cluster. I could have lots and lots, and if I had Windows Server Enterprise I would also have high-availability if one of the nodes went down.
I download the AppFabric Caching Samples and opened the CacheSampleWebApp in Visual Studio. Immediately we notice the two new references we don't usually see in a web application, Microsoft.ApplicationServer.Caching.Core and .Client.
Your cache can be hooked up in the web.config or from code (however you like). Here's a code example helper method where the sample does this manually. This data could come from wherever you like, you just need to tell it a machine to talk to and the portnumber. It'll automatically connect to the
You can use Performance Monitor as there is an imperial buttload of different Performance Counters Available. As I mentioned, you can make different partitions, like "default" or "poopypants" and check the stats on each of those separate, or the cache as a whole:
And of course, I can recycle my webserver, start it up again and fetch an order and it's still there. You've effectively got a big, partitionable distributed (and optionally highly available) hashtable across multiple machines.
As with all things, a little abstraction goes a long way. If you have an existing caching strategy (via EntLib, or whatever) you can almost certainly swap out your internal storage for AppFabric Caching.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
i have 2 windows server 2008 r2 on vmware.one of them is Domainthe other one is joined to domain that it's name is "win sharepoint"i am trying to install sharepoint 2013 on "win sharepoint"i installed all prerequisites except windows server appfabricwhen i trying to install sharepoint , it started to downloading windows server appfabric but after that it shows:
windows server APPfabric installation error
You could download the AppFabric installer manually (but don't run it) =235496 , and then run the installer through the Prerequisites installer like this: prerequisiteinstaller /appFabric: WindowsServerAppFabricSetup_x64.msi.
In my experience, if the AppFabric service isn't installed 100% correctly, you will have all kinds of sporadic SharePoint problems (crashes) in the future. I also suspect (but have never confirmed) that trying to run the prerequisites installer multiple times sometimes gets the machine into a state where the App Fabric service can never be installed, so you might consider re-installing the OS if this keeps happening.
I've also found that the AppFabric service installation has problems if the machine (and the user account you are installing under) are not correctly joined to the AD domain. You might check the clock on your VM to make sure its within a few minutes of the clocks on your domain controllers, and also make sure that your new VM is only using Domain Controllers as its DNS servers (so it can look up all those SRV records, which other DNS servers may not have).
Microsoft AppFabric Caching is no longer supported. For developers running AppFabric Caching in production environments that need to guarantee reliability and stability for their users, you should consider migrating to an alternative that provides on-going support.
Both Memurai and Windows Server AppFabric support a client/server model of communication and all of the semantics and features of AppFabric Caching are supported by Memurai. However, Memurai goes further and extends those features with far more functionalities than currently available in the legacy AppFabric. This section provides an overview of the key architectural differences between AppFabric Caching and Memurai.
AppFabric Caching supports tags for assigning metadata to objects in the cache, and you can use an API to search the cache and find objects with the tags. Tags only work within a region, and the caveat is that providing the tag-search functionality requires objects in a region to be confined to a single cache host. Alternatively, if you do not specify a region, objects can be cached across all hosts in a cluster. In this way, developers are faced with a trade-off: better searchability with tags or improved scalability using multiple cache hosts.
Conversely, you can use tags with Memurai by embedding descriptive strings in key names or by using the set data type to group related keys together. Using sets in this way allows you to quickly and efficiently retrieve all of the associated data with the MGET command. Unlike AppFabric Caching, no restrictions are placed on where data is stored.
Nodes in a Memurai cluster are configured with individual configuration files, stored on the nodes themselves rather than in a central location. This configuration file is fully compatible with the Redis 5 syntax.
AppFabric supports a High Availability (HA) mode. When enabled, HA mode stores a copy of every cache object or region on a separate cache host. High availability is achieved because the cache cluster will supply any clients with a copy of the data even if one of the cache hosts is unavailable. The static assignment of Lead hosts for Windows AppFabric Caching clusters leads to inflexible cluster management and unnecessary overhead for administrators. HA mode requires that all cache hosts in a cache cluster are running the Enterprise Edition (or higher) of Windows Server 2008 or Window Server 2008 R2.
795a8134c1