next »

[aswaim]

This problem started gradually 2 wks ago.  I'd get the above message after only a couple of minutes into a session of editing the calendar.  This week it started happening after less than a minute into the session.

Today I get this message as soon as I log in.

Any suggestions?

I tried adding the script URL to Trusted Sites in IE.  Also tried this with Netscape brower.  Same results.

IE 6.0
Win 98
for past yr I've been on cable modem connection
and also during this time running Zone Alarm
w/o seeing this problem.

[aswaim]

Here's an odd postscript to above problem.  I browsed in the user.txt file and found entry for my administrator username & password but also entry for "anonymous".  (Maybe that was always there...?)

Logged in as "anonymous" and no password and was able to log in the calendar-admin.cgi script but on the calendar selection screen, next click resulted in same old "Your session has expired."

Hmmmm.

[DanO]

** entry for "anonymous". (Maybe that was always there...?) **

Yes.

** "Your session has expired." **

It sounds like the calendar might not be able to read the cookie which is set when logging in. How do you have IE 6's security set regarding cookies?

Dan O.

------------------

[aswaim]

Thanks for replying, Dan.

Yes, I set IE to accept all cookies.

Read through archives here several other msgs re: "Session expired" problems.  Wondered about problem between my system clock and time on server...?  Tweaked system clock a bit in both directions but no go.

Curiously, when I log in, I still get the "Session expired" message" immediately but when I hit Reload/Refresh I get successful log in.  (seems to point toward web browser hiccup).  But then when I click "Continue" on Calendar Select page, I'm still back to "Session expired. You must log in again."

Hmmm.

------------------

[DanO]

Have you checked to make sure the session data is being written to the session directory? Maybe that directory's permissions have changed and CalendarScript is unable to record the information?

Dan O.

------------------

[aswaim]

Yeah, I checked all the folder and file permissions.  Even tried transferring the "junk.txt" file back into the /sessions directory since debug seemed to think it should be there.  

That didn't help.

Since I had a time crunch to update this calendar, I took the necessary three hours today to re-install the whole thing.

What I did was save some of the orig files from the templates/calendars/default folder so, at least, I didn't have to reset all of those.  

after installation, I was able to copy over the installed files with my orig copies of:
preferences.txt
default.html
and it wanted styles.pl too
though that appears to be relic from older version?

So...bottom line....all works fine now.

That seems to point to something having got gummed up in the program, not browser problem, not web server problem...

I have a vague thought about whether this application hits a wall after a certain number of event or schedule entries?  Didn't find any ref in docs to an upper limit on that.  Doesn't *seem* like this should be a factor, but who knows?

I had two and half years worth of almost daily events.  Maybe a factor...

I do still think this a wonderful application and I'm still (even after today) very glad to have taken the time to register it!

[DanO]

** I have a vague thought about whether this application hits a wall after a certain number of event or schedule entries? Didn't find any ref in docs to an upper limit on that. ... I had two and half years worth of almost daily events. Maybe a factor... **

I have a current client using CalendarScript and they have in excess of 8,000 events on each of two different calendars, 10-20 events per day and they've never run into a problem with user's sessions expiring so I really doubt that's it.

JMO

Dan O.

------------------

[aswaim]

Good to know that number of events/schedules would not have been a factor.

Just wanted to add that re-install of the application, of course, only took a few mins; what took longer was putting all our events back in because ... yeah, I didn't have a complete backup of them on my own machine.

I figured I might as well do a full install of 3.2 instead of the upgrade I did to 3.2 last year....

....which also might have been a factor here.  Although again, things ran fine for many months since then.

It still seems odd that this problem started so gradually as mentioned in first msg.   But all's well that ends well.

Thanks again for your replies, Dan.