Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Need Premium Support?

ScaleOut Software offers customers several options for support and maintenance plans on a subscription basis for an annual fee.

Topics:

x4

asked: Sep 04, 2017 at 07:27 AM

Seen: 168 times

Last Updated: Sep 05, 2017 at 05:58 PM

Multiple host are getting registered to store in one pc. and it is getting reset automatically. getting below error after sometime

[NotLicensedException: Client is not licensed to perform this operation.] Soss.Client.DataAccessor.Read(ReadOptions options) +2085 Soss.Web.SossStoreProvider.GetItem(HttpContext context, String id, ReadOptions readOptions, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actions) +483

[HttpException (0x80004005): Couldn't access session state for SessionID: xxxxxxxxx...
more ▼

asked Sep 04, 2017 at 07:27 AM in Support

gautamnayak247 gravatar image

gautamnayak247
1

(comments are locked)
10|5000 characters needed characters left

1 answer: sort voted first

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 host(s) and it is sharing the same TCP ports and the same multicast IP, it can automatically join your store. If you're using one host environment (for example, for dev or test purposes), you can isolate it within your subnet from these type of intrusions by binding the SOSS service to loopback adapter's IP address. You can read more about this approach in the following best practices article:

http://static.scaleoutsoftware.com/docs/soss_help/content/_deployment_considerations.html#_dep_13_standalone_hosts_can_use_a_loopback_adapter_if_a_network_is_not_available_or_to_keep_hosts_from_discovering_each_other

If you are using multiple hosts environment, you can isolate it from other SOSS environment by using a unique set of the interconnect, management and server ports. It is a good practice anyway to change default SOSS ports within the environment you want to control to prevent the auto-discovery when, for example, a newly installed host is starting up on the same subnet using the same default TCP port numbers.

Another way to isolate your SOSS store from others is to change the multicast IP for each host there to non-default unique IP address. Please note, only certain IP address ranges can be used for the multicast IP (as defined by iana.org): In IPv4, addresses 224.0.0.0 through 239.255.255.255 (the former Class D addresses) are designated as multicast addresses.
more ▼

answered Sep 05, 2017 at 05:58 PM

Support gravatar image

ScaleOut Support Team ♦
1.9k 19 20 20

(comments are locked)
10|5000 characters needed characters left