Search results

The acceptable rate of cache misses depends on the requirements and design of your application and how the ScaleOut APIs are being used. If your developers expect 100% of the ScaleOut API calls to successfully find an object in the ScaleOut service then 44 misses/sec could be interpreted as a...

Raj, We've narrowed down the problem to changes Microsoft made to struct argument passing in RyuJIT for .NET 4.7.1. The simplest resolution is to upgrade to our latest release, but if that isn't possible then you should be able to work around the problem by changing your app's web.config file...

By default, ScaleOut StateService (SOSS) relies on internal heuristics when it comes to handling communication delays and network interruptions. You can disable it by setting the auto_npf configuration parameter in the soss_params.txt file to 0. That would allow you to manually lower SOSS’s...

We've reproduced the problem on a setup similar to yours but haven't yet determined a root cause. We've also confirmed that this issue does not occur with our latest release (5.6.3.318) running under 2008R2/4.7.1. We'll continue to dig into this, but if you need an immediate way to move forward...

In most cases we advise customers to avoid vMotion — if vMotion causes a ScaleOut host to go offline for an extended periods then other hosts will assume that it failed. The ensuing recovery protocols can affect store throughput. We’ve improved resilience since 2013 and added a number of...

Hi Raj, Version 5.4.3.255 is compatible with .NET 4.7.1. You'd see assembly load exceptions being thrown if there was an incompatibility. Are you seeing any errors? Are there any unusual entries in the Windows Event Log?

You should not need to modify that supportedRuntime element. The most common cause of this error is that the assembly you're trying to load was downloaded from the internet and is being blocked by Windows. Check in the assembly's properties to see if it needs to be unblocked. You'll also need...

If it's one host causing the burst then it's probably being caused by a single, large object being being flushed by the client cache. Is there any one object that's shared by all 55 web applications? Also, have there been any significant changes to your load or to your app in the last few...

To configure ScaleOut StateServer to work without multicast, you need to manually define your host group. A host group is a manually-defined roster of IPs that are eligible to form a store. The first step is to disable multicast either through Management Console in the Host Configuration tab by...

Hi nithin, The ScaleOut service will automatically generate a self-signed certificate (generated by OpenSSL) when it starts up if accept_secure is set to 1 and there isn't already a key pair in the product's installation folder. The generated certificate is then automatically deployed to the...

To run an installer-less client application, you'll need to copy the following files into the same directory as your application: Native DLLs (found in the installation root directory) soss_svccli.dll soss_perflib_client.dll .NET DLLs The optimal file locations for the .NET DLLS will depend...

Hi Adam, If you have data that needs to be modified outside of a user's page request then you'll almost certainly want to move it out of session state and into a separate object that's accessed through our NamedCache API and is keyed by UserID instead of a session ID. (I found your original...

The reason why you're getting this exception deals with the fact that host from other environment is joining your ScaleOut StateServer (SOSS) store making the number of hosts there to be larger than the number you're licensed for. If other host is running on the same subnet as your existing...

Hi Ali, ScaleOut Software does not provide a Redis product, so I'm afraid we can't help you with specifics about Redis. ScaleOut does provide its own in-memory session provider product called ScaleOut SessionServer, though, which I encourage you to evaluate. And these are great questions, so...

Using the 'SOSS Powershell Administration' shortcut or by importing the 'SossAdministration' PowerShell module directly into PowerShell, you can use the PowerShell cmdlet 'Clear-AllObjects' to clear all objects from the ScaleOut StateServer store. You can also clear all objects from the store...

The SOSS client library does not load any default settings from app.config by itself but it is trivial to do this in your own application code: Add a reference to System.Configuration to your project if you haven’t already. Add a new appSetting to your app.config file...

DataCacheServerEndpoint class is defined for a source compatibility purpose only, it is not used by the WSAF Caching Compatibility Library. Instead, you should configure ScaleOut StateServer (SOSS) client library to allow your application to communicate with the caching cluster. You can use...

If your application works fine when it runs on one of the state servers and does not work on remote client machine, it means your remote client is not properly configured. You should start with running ScaleOut StateServer (SOSS) installer on the client machine by selection the "Remote Client"...

Hi Nick, This exception occurs when a web request takes longer than 90 seconds to complete. (90 seconds is the lock timeout for ASP.NET sessions). So this is a side-effect of a very slow page handler. If a web request takes more than 90 seconds to complete, the request handler loses its...

The symptom you’ve experienced is likely caused by network security software stopping traffic between the serving running the SOSS Object Browser and the SOSS store. We recommend verifying connectivity between the servers on all SOSS ports (the default ports are 720, 721, and 722). If this is...