Thanks for your response. I plan to contact them again this afternoon. It may be a bug but I'm surprised that they aren't being deluged with calls about it!
Main Topics
Browse All TopicsAfter a short period of inactivity, the web interface stops responding and a new log on screen pops up prompting the user to log on again. Both windows end up needing to be closed in order to reconnect to database and continue work. We have worked with Sage tech support and they had us change timeout values in various places in IIS but the problem continues. In ACT on the server in Web administration, time for session timeout is set to 6 hours.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
From my testing so far, it seems to take between 1/2 hour to an hour of inactivity. It seems it was a much briefer time before we started making changes to timeout settings in IIS. I can't really say if it's the same amount of time each time at this point. I was just trying to establish that it was still happening. Not every user has reported it but I think there may only be 2 users who are actually using the system regularly so far and they have both reported it. Have you seen this before? The Sage technician I worked with yesterday seemed to indicate that most people aren't using the product the way we are. We are only using the Web interface so far so users are using the product the same way they would a standard Windows app and just leaving it open for extended periods. Any insight you can share would be most appreciated!
OK that corresponds with what I'm seeing. I appreciate your help. I would consider this to be a major bug in the program however since this is undocumented. The user is led to believe that by setting the timeout session in ACT! on the server, that this is all that is necessary. In fact the tech support person I worked with yesterday confirmed that the ACT! timeout session time should be overriding the other settings. How do I elevate this issue with Sage and why aren't others complaining about it??
Do you have client's connected to the database and are they experiencing problems? - this could be some other aspect of Act timing out in which case changes can be made with ActDiag on the server.
Do you have the Web interface on the same server/pc as the database itself? - It is advisable to have Act hosting the database on one server and for the web client dealing with IIS and the hosting on another machine. I've never really understood why but Sage have admitted there are far fewer issues doing things this way.
Just wondering were you using the default apfw virtual folder or a custom one? I suspect the Web Admin tool only affects the default folder.
Test the default localhost/apfw address and see if timeouts are respected there.
If so, copy the entire contents of the APFW physical directory in programfiles\act\act for web to the folder you created for your custom virtual directory and restart IIS.
If you have a custom virtual directory, the physical directory it points to should be rebuilt after every update to take advantage of program changes.
Also what AV are you using. I've heard some have a memory leak where it ate a load of memory and then IIS stoped serving up web pages, it would just deny the connections, you could see it in the logs, it used to get problems the closer AVG got to eating all the memory. Only thing that would fix it was a reboot. This was most common on SBS though.
Also with the logins I used to have problems where users would put in their username/password and they would get the red text on the login page saying an error has been logged. You'd get various framework errors in the event logs but an iisrest would fix it. I now just schedule that to run at the end of the backups at 2/3am and it keeps things ticking over.
Failing that, can you post the web.config file?
Business Accounts
Answer for Membership
by: A2ZsupportPosted on 2009-01-21 at 10:15:24ID: 23432271
We are having the same problem, but have not had any luck resolving it. If I find a solution, I will let you know.