Error with multiple calls using the same account

Waylon Smith

This issue is for a SyteLine 9 ERP using IDO service. My issue is that while an IDO call is being processed, and I make another call with a new connection using the same account, I get a "MGException exception processing 'LoadCollection' request: Your session has been deleted. You must close your session and log on again to continue." error message. I'm using the account as a service account, but apparently it cannot handle concurrent requests. I'm using .NET to handle the calls. Is there some programmatic way to handle this. Or is there some SyteLine setting or special account that has to be used for concurrent calls?

ChuckAtDRI

That is because your SyteLine license must be a Named License and not a Concurrent License. You can verify that on the License Management form. With a Named license each user can only be logged in once per site. With a Concurrent license the same user can be logged in multiple times until all the license tokens are in use.

Try using the SL_Internal account. That is a special account made specifically for doing IDO integrations. It does allow you to log in multiple times, but it still has a limit. Look on the License Management form, Multi-Session Users tab to see how many you are allowed. However, you are still limited to that number of concurrent sessions with the SL_Internal account. It is presumed that it would be used for back-end integrations which do not stay logged on for long periods of time.

Also, in your code, be sure that you always do a Logoff before you close the connection. Otherwise the license token can stay locked and you will run out of sessions for the account.

Also, if this is a development system that was copied from your live instance, you may need to manually truncate the ConnectionInformation and SiteConnectionInformation tables. We would often run into that issues when our clients did a Live to Pilot refresh. I don't believe there is a form that shows you the SiteConnectionInformation data, but it is also used in licensing and any stale entries there can cause that 'your session has been deleted' message, but typically we see that when trying to login to the refreshed database as 'sa'.

I hope that helps a bit.