Chad#

Ramblings of a technology junkie.

Having trouble starting Velocity host on x64?

I recently installed Microsoft Velocity client on 5 of my dedicated servers and I thought I’d give this distributed caching a try and see how it went.  The 5 severs are all running Windows Server 2008 Standard x64 with AD Services.  Installing couldn’t have been easier or have gone smoother.  So after installing Velocity on my 5 machines I went to the lead machine to start it.  Note, at this point I hadn’t setup the cluster yet I was just installing it on the machines.

   1: PS C:\Program Files\Microsoft Distributed Cache\V1.0> get-cachehost
   2:  
   3: HostName : CachePort           Service Name              Service Status
   4: --------------------           ------------              --------------
   5: VSERVER:22233                  DistributedCacheService   SERVICE DOWN

So far so good.

Next was to start the individual cache host…

   1: PS C:\Program Files\Microsoft Distributed Cache\V1.0> get-cachehost
   2:  
   3: HostName : CachePort           Service Name              Service Status
   4: --------------------           ------------              --------------
   5: VSERVER:22233                  DistributedCacheService   SERVICE DOWN
   6:  
   7:  
   8: PS C:\Program Files\Microsoft Distributed Cache\V1.0> start-cachecluster
   9: Unable to open store PartitionAccessor: System.DllNotFoundException: Unable to l
  10: oad DLL 'sqlceme35.dll': The specified module could not be found. (Exception fro
  11: m HRESULT: 0x8007007E)
  12:    at System.Data.SqlServerCe.NativeMethods.DllAddRef()
  13:    at System.Data.SqlServerCe.SqlCeConnection..ctor()
  14:    at System.Data.SqlServerCe.SqlCeConnection..ctor(String connectionString)
  15:    at System.Data.Cas.Main.SqlCeStore.OpenConnection(String connectionString)
  16:    at System.Data.Cas.Main.SqlStoreProvider.Open(String ownerId)
  17:  
  18: HostName : CachePort           Service Name              Service Status
  19: --------------------           ------------              --------------
  20: VSERVER:22233                  DistributedCacheService   SERVICE DOWN
  21: Start-CacheCluster : Unable to load DLL 'sqlceme35.dll': The specified module c
  22: ould not be found. (Exception from HRESULT: 0x8007007E)
  23: At line:1 char:18
  24: + start-cachecluster <<<<

Well –- that didn’t work.  You’ll see I used the cmdlet start-cachecluster this just goes down the list and uses start-cachehost on each cluster node.

I later found out that this is a known issue with Velocity and a temporary fix for CTP2 has been found.  Just download SQL Server Compact 3.5 SP! x64 and install it on your machine.  So after installing that I tried to run start-cachecluster again.

   1: PS C:\Windows\System32> start-cachecluster
   2:  
   3: HostName : CachePort           Service Name              Service Statu
   4: --------------------           ------------              -------------
   5: VSERVER:22233                  DistributedCacheService   SERVICE UP

Fixed!

So this is a known issue by the Velocity team and it will be fixed in the next version.

Posted: Nov 04 2008, 11:20 AM by Xtek | with 1 comment(s)
Filed under: ,

Comments

pauljones said:

You are right Chad! Velocity is still in its infancy and requires quite a bit of maturity before it can actually be considered for high performance, mission critical apps. Eventually when the V1(the first real version)comes out, it would have to be thoroughly tested before deployment. The product would have to undergo some rigorous scrutiny before performance and reliability hungry applications can consider using it.

All the best!

# November 18, 2008 5:00 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)