Hi, We have 'some' custom stored processes in our company, launched in a browser. We use html, java-script and ajax-calls to get those stored processes present the data (dashboards, graphs, tables, ...). Users have to log in using their Windows-credentials, and once logged in, users can launch -depending on their user-rights- several stored processes. The stored process session they get after logging in normally remains active for an hour, but sometimes the session is terminated unexpectedly much earlier and requires the user to log in again. This isn't a really big deal for a normal stored process. But it's mainly a problem with an ajax-call which isn't capable in getting the data as expected, because it gets a http302-status code, followed by a redirect to the SASLogon-page (which isn't visible for the user...) I have 2 questions: Is there any way in tracking down the reason for the termination of these stored process sessions? I already checked the stored process serverlogs, but I can't find anything. Is it possible to check the status of a session before an ajax-call is made? SAS-version we use is 9.2 (by the end of the year we upgrade to 9.4) Thanks in advance!
... View more
