Search results

  1. S

    How do I load a .NET 4.0 assembly into the Object Browser?

    When I attempt to load my assembly into the Object Browser, I receive a "not a valid .NET assembly error". I know my assembly is valid, and my application works without error. Do I need to add something to my assembly to support the Object Browser?
  2. S

    Why do object/session expiration events stop being delivered to a Web application after upgrading from ASP.NET 2.0 to ASP.NET 4.0?

    I recently upgraded my web application to target the .NET 4.0 framework instead of .NET 2.0. My application properly received and handled session expiration events prior to the upgrade, but the events are no longer firing after the upgrade.
  3. S

    When does ASP.NET’s Session_End event get raised by the StateServer service?

    As the title implies, under what conditions does the ASP .NET Session_End() event fire?
  4. S

    Will an object be removed from the client cache when it is removed from the SOSS store?

    I'm concerned about object coherency for removed objects. If I have two clients running the same application, and Client A removes the object from the SOSS store, what behavior can I expect from Client B if it then requests the same (now deleted) object?
  5. S

    Will an object with pending events be removed before its events are fired?

    My application logic requires that the object still exists at the time I receive the expiration event. Is the expiration event a pre-event or post-event (i.e., has the object already been deleted and the event is post-facto?)
  6. S

    When an object is removed from the store, does it mean that any pending events associated with object are removed from the event queue as well?

    My application requires the use of object event handling. Objects typically timeout and expire on their own, but there are use cases when an object may need to be explicitly deleted before its expiration timeout. Will my events still fire?
  7. S

    How are remote clients counted?

    A ScaleOut StateServer distributed data store can be accessed by remote machines that have ScaleOut’s remote client libraries installed. The number of remote client machines that are allowed to connect to a store is determined by the license key being used by the SOSS hosts. Remote client...
  8. S

    How are remote clients counted?

    Our license key includes a maximum of 16 remote clients. We have 12 web servers running a single web application. We'll be adding a second web application onto these same web servers in the near future. Will we need to license additional remote clients?
  9. S

    What are the steps to complete a rolling upgrade?

    We would like to upgrade our ScaleOut store to the latest version. How can we do this without downtime?
  10. S

    What are the steps for applying a new license key?

    We've received a new license key after testing our product with a temporary license key during evaluation. How do we apply this new license key without any downtime?
  11. S

    Why isn't there a date in the License Expiration field?

    In the Host Licensing tab using the SOSS Console, the License Expiration field shows "None". Why is this?
  12. S

    Do anti-virus products interfere with ScaleOut hosts?

    Our IT policy requires all servers to actively run an anti-virus solution to help protect us from risk. Since SOSS is a high performance product, will running anti-virus software negatively impact our performance?
Top