Cache assemblies not found in 64-bit AppFabric SDK

Question

I installed the new AppFabric SDK today, but it seems that the cache assemblies were not included in the 64-bit version. When I go to \Program Files\Windows Azure AppFabric SDK\V1.0\Assemblies\NET4.0, there's no Cache folder, or anything similar. We had to install the 32-bit SDK on another machine to get the right assemblies, since that version won't even install on a 64-bit machine.

Is this a flaw in the installer? Is there something I could have possibly missed during the installation process?

Answer 1

Hi Jon

I downloaded the new appfabric sdk - funnily still named 1.0, but April Update - publish date 4/28/2011 from this link. I installed WindowsAzureAppFabricSDK-x64.msi on my 64bit machine without any issues.

I have this folder here: C:\Program Files\Windows Azure AppFabric SDK\V1.0\Assemblies\NET4.0\Cache, with the following assemblies:

• Microsoft.ApplicationServer.Caching.Client.dll
• Microsoft.ApplicationServer.Caching.Core.dll
• Microsoft.Web.DistributedCache.dll
• Microsoft.WindowsFabric.Common.dll
• Microsoft.WindowsFabric.Data.Common.dll

Hope this helps,

Marc

Answer 2

Funny, that's the exact same file I downloaded, but the Cache folder doesn't show up for me. My NET4.0 folder just contains the following files:

• Microsoft.ServiceBus.dll
• RelayConfigurationInstaller.exe
• RelayConfigurationInstaller.exe.config
• RelayConfigurationInstaller32.exe
• RelayConfigurationInstaller32.exe.config

The NET3.5 folder looks similar, except it doesn't have the .exe.config files. I did have an old version of the AppFabric SDK installed before this one, but I uninstalled it before installing this one.

Has anyone else run into this issue?

Answer 3

During the CTP, there were issues with using the Windows Azure AppFabric Caching service if the non-Azure Windows AppFabric Caching service was also installed. I don't know it these issues have been fixed in the release.

Answer 4

Funny, that's the exact same file I downloaded, but the Cache folder doesn't show up for me. My NET4.0 folder just contains the following files:

• Microsoft.ServiceBus.dll
• RelayConfigurationInstaller.exe
• RelayConfigurationInstaller.exe.config
• RelayConfigurationInstaller32.exe
• RelayConfigurationInstaller32.exe.config

The NET3.5 folder looks similar, except it doesn't have the .exe.config files. I did have an old version of the AppFabric SDK installed before this one, but I uninstalled it before installing this one.

Has anyone else run into this issue?

Yep, I've got that problem as well. 

Exact same files listed in mine, also installed the x64 version.  I actually grabbed the DLLs Marc listed above from the SDK V2.0\Assemblies\Cache folder, where they do live, but when using the cache I'm getting this error:

ErrorCode<ERRCA0019>:SubStatus<ES0001>:Check the client version. It should be within the allowed version range on the server. If necessary, upgrade the client to the allowed version.

Which implies that I shouldn't be using the 2.0 dlls.

I guess I'll go try to get the 32 bit version...

Answer 5

Hi,

  It seems you've installed older SDK ( possibly Feb CTP Labs bits ), because the path that you've mentioned ( V2.0\Assemblies\Cache ) corresponds to Feb CTP release. For April Production release, the path for cache assemblies should be in C:\Program Files\Windows Azure AppFabric SDK\V1.0\Assemblies\NET4.0\Cache. Feb CTP release bits won't work with April prod provisioned cache endpoint.  Please download the April prod SDK from this link

Answer 6

Hi,

   Please download the AppFabric SDK from this link and install as follows

c:\>msiexec /i WindowsAzureAppFabricSDK-x64.msi /lv install.log /quiet

and post the install.log file

Answer 7

I uninstalled the SDK, redownloaded it from that link, and tried reinstalling according to your instructions, with the same result. Here's the install.log:

 

=== Verbose logging started: 5/2/2011  9:32:19  Build type: SHIP UNICODE 5.00.7600.00  Calling process: C:\Windows\SysWOW64\msiexec.exe ===
MSI (c) (18:F8) [09:32:19:945]: Resetting cached policy values
MSI (c) (18:F8) [09:32:19:945]: Machine policy value 'Debug' is 0
MSI (c) (18:F8) [09:32:19:945]: ******* RunEngine:
           ******* Product: .\Desktop\WindowsAzureAppFabricSDK-x64.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (18:F8) [09:32:19:946]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (18:F8) [09:32:19:946]: Grabbed execution mutex.
MSI (c) (18:F8) [09:32:19:964]: Cloaking enabled.
MSI (c) (18:F8) [09:32:19:964]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (18:F8) [09:32:19:968]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B8:1C) [09:32:19:974]: Running installation inside multi-package transaction C:\Users\jschuster\.\Desktop\WindowsAzureAppFabricSDK-x64.msi
MSI (s) (B8:1C) [09:32:19:974]: Grabbed execution mutex.
MSI (s) (B8:C8) [09:32:19:975]: Resetting cached policy values
MSI (s) (B8:C8) [09:32:19:975]: Machine policy value 'Debug' is 0
MSI (s) (B8:C8) [09:32:19:975]: ******* RunEngine:
           ******* Product: C:\Users\jschuster\.\Desktop\WindowsAzureAppFabricSDK-x64.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (B8:C8) [09:32:20:038]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (B8:C8) [09:32:20:116]: SRSetRestorePoint skipped for this transaction.
MSI (s) (B8:C8) [09:32:20:118]: Note: 1: 1324 2: . 3: 1
MSI (s) (B8:C8) [09:32:20:118]: MainEngineThread is returning 2
MSI (s) (B8:1C) [09:32:20:118]: No System Restore sequence number for this installation.
MSI (s) (B8:1C) [09:32:20:122]: User policy value 'DisableRollback' is 0
MSI (s) (B8:1C) [09:32:20:122]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:1C) [09:32:20:122]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B8:1C) [09:32:20:122]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:1C) [09:32:20:123]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:1C) [09:32:20:123]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:1C) [09:32:20:123]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:1C) [09:32:20:123]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (B8:1C) [09:32:20:123]: Restoring environment variables
MSI (c) (18:F8) [09:32:20:127]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (18:F8) [09:32:20:128]: MainEngineThread is returning 2
=== Verbose logging stopped: 5/2/2011  9:32:20 ===

Answer 8

And here's mine...my install log looks a lot larger.  Still, the only contents of the net4.0 folder are as follows:

 

 

10/26/2010  11:05 PM         1,746,792 Microsoft.ServiceBus.dll

10/26/2010  11:05 PM            14,200 RelayConfigurationInstaller.exe

10/26/2010  10:47 PM               138 RelayConfigurationInstaller.exe.config

10/26/2010  11:05 PM            14,208 RelayConfigurationInstaller32.exe

10/26/2010  10:47 PM               138 RelayConfigurationInstaller32.exe.config

and here's the install log:

install.log

(too long to post)

 

Answer 9

Disregard my last post. I opened the log file too soon, which I think may have cancelled the installation. I thought it was the same result, but it wasn't - the installation never finished, and the folders never showed up.

I tried again and waited much longer, which resulted in a much longer log file. Still the same result as my original attempt: the SDK installed, but no cache assemblies. Here's the log file:

http://www.mediafire.com/?pa7udnz30bpy873

Answer 10

For what it's worth, I just RDC-ed into my home computer, also an x64, ran the installer and it worked.  Copied the Cache folder over to my work pc and the TrySessionCloud app works now.  So, it's apparently either the SDK installer hates my work pc, or vice versa.

 

Answer 11

Hi Jon,

I understand that the \Program Files\Windows Azure AppFabric SDK\V1.0\Assemblies\NET4.0\Cache is not generated after installing 64bit Windows Azure AppFabric SDK.

There could be several issues within the local machine itself. The best would be to setup live meeting with you and investigate problem on your machine. Please contact the azure support team (http://www.microsoft.com/windowsazure/support/, click the "AppFabric" link) and ask them to look into your machine and assist you. This service is currently free.

Thanks,

---

Wengchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 12

From what I've seen in your install.log, your product guid is totally different from what we expect ( yours '{8CF60BEF-139E-49C4-A81C-7AF560F8EF56}' ... ours '{B4218088-6F4D-457C-B3A9-4D9FE5110A67}' ). Is it possible for you to share the msi also ?

When you said you had a previous version of AppFabric SDK installed, which one you meant ? AppFabric SDK prod with just ACS and SB (or) Cache CTP labs that has ACS, SB and Cache ?

Answer 13

From what I've seen in your install.log, your product guid is totally different from what we expect ( yours '{8CF60BEF-139E-49C4-A81C-7AF560F8EF56}' ... ours '{B4218088-6F4D-457C-B3A9-4D9FE5110A67}' ). Is it possible for you to share the msi also ?

Answer 14

Here is the MSI, although I can't imagine it's any different from what you would expect, since I got it from the standard download page for the new SDK (the page says publish date of 4/28/2011): 

http://www.mediafire.com/?ozppl1eajwav744

From what I'm hearing, it sounds like there must be something from one of my old AppFabric installs that didn't get completely cleaned up. I've probably had both of the SDKs installed that you mentioned - I was recently doing work on the Cache CTP, and I think I may have had the prod SDK installed earlier. Before installing this version, there was definitely a 2.0 folder in my AppFabric SDK folders in Program Files, if that helps at all.

Wenchao, I may have a live meeting with the support team, but for right now, it's not a big enough problem for me to spend time on it. Like I mentioned, we found a workaround on our end, and I just wanted to get the conversation going in case someone else (like David) had the same issue, or in case the installer itself was bad.

Answer 15

I've looked into your MSI Jon. It seems that the MSI is of older version ( Windows AppFabric SDK September 2010 release ). I've tried downloading the latest AppFabric SDK from this link and it installs fine.

Please delete the AppFabric SDK MSI in your system ( use some tool, like CCleaner, to delete temp files & reg entries, just in case ). Download AppFabric SDK from the specified link and try again.

Answer 16

Thanks Karthik, that worked. Maybe the download link for x64 was broken for a while and pointed to the old MSI, or maybe I somehow found the wrong link multiple times, but the new one is significantly bigger than my old file. I installed it and everything worked fine, with cache assemblies getting put in the right directory. Thanks for the help.

Answer 17

Hi,

To reiterate, you should install the latest update for Windows Azure AppFabric SDK 1.0 – April update which has correct assemblies.

---

bill boyce