Q. Timeout error in Eolas and databases

If you get an "internal server error" in Eolas or some of the databases, this is the workaround.


I'm getting an error when I click on a link 

you will get a " No results were found " error or an internal server error. Basically your session has timed out. There is a 2 hour timeout on Eolas or the Ebsco Databases*. So if you leave a browser tab open with an article or ebook  that you are reading and don't click or move your mouse for 2 hours it will timeout.

Workaround and Tips

This screen below will appear when content dependent on an active session is loaded through an expired session. Users who copy and paste the URL to an article or to a search directly from their browser bar, rather than generating a persistent link from within the interface. Persistent links can be generated either by using the "Share" dropdown menu on the Results List, or the "permalink" tool on the right-hand side of a detailed record.
Additionally, when using EBSCO interfaces, users will want to use the links and buttons within the interface to navigate forward and backward, rather than using the browser's forward/back buttons.

Quick Workaround: hit F5 on your keyboard to refresh your screen.

a system problem has occurred screenshot

* What are the EBSCO Databases/products?

(EBSCO is the company/publisher/vendor we get these databases from)

Eolas Search
Academic Search Complete (EBSCOhost)
Business Source Complete (EBSCOhost) 
eBook Academic Collection (EBSCOhost) 
Regional Business News (EBSCO HOST)
UK & Ireland Reference Centre 



  • Last Updated Wed,Dec,2020
  • Views 342
  • Answered By Aine Meehan

FAQ Actions

Was this helpful? 1   0