Your session is no longer valid. CE10 only.

[mdwyer]

We are running CE 9 in production and CE 10 in development, on two independent servers.

Because this migration is a low priority project, I will often have sessions open in both environments but get interrupted with more important tasks. The frustating thing is that the CE10 session will timeout, but the CE9 session does not.

As I understand the session timeouts, the WCS component is using the default 20-minute setting. Neither WCS service has an override on the command line as found in the CCM properties tab.

Am I looking in the right place? Is there a timeout difference between CE9 and CE10? Not a crititcal issue, but if there's a quick solution I'd like to apply it.

- Mike

 

[Turkbear]

Hi,
Check the timeout of the Cookie ( Token) created when you first log in..I'm not exactly sure where it is set, but if it expires, your session will no longer be seen as valid.

 

[synapsevampire]

I would think that it's reflected in the command line of the WCS in the CCM, but you can also check the Start Parameters for the service itself under the Services directly.

Here's the timeout settings, so you should be able to just set it:

http://support.businessobjects.com/library/kbase/articles/c2012077.asp

Here's a blurb on tokens:

http://support.businessobjects.com/library/kbase/articles/c2015902.asp

-k

 

[mdwyer]

Thanks. Yes, I have a custom management app in production that sets a logon token to "500" - minutes, I think. As the "blurb on tokens" points out, that token may allow access even after logging off. Since I run that app once a day, that probably keeps me alive in production. I'll see what happens tomorrow if I don't run it. And, since I'm the only guy in dev, I could boost the server timeout - if I think I would remember to reset it when I start bringing users online.