“Java-based Reader” Installation Issues

To open a book for online reading, we recommend clicking on its title or cover.

However, if your ebrary site happens to also offer ebrary’s older stand-alone reader, the “Java-based Reader” (aka the Unity Reader), and you wish to use it, click the “Java-based Reader” button instead; it is located below the book in search results.

The Java-based Reader is being phased out and may not work smoothly on newer systems, here are some tips if you experience problems:

  • Make sure you have the most recent version of Java, at least version 7
  • Cookies need to be enabled

Error Code 102 usually means the Unity Reader was unable to connect to ebrary servers, here are some suggestions:

  • reader.ebrary.com must not be blocked on ports 80 and 443
    • This has been a common problem with sites that are using proxies
  • Make a firewall exception for the Unity Reader
  • Make sure you have write access to your home directory
    • The Unity Reader does not require admin rights for installation but it creates personalized files for users in their home directory
    • Occasionally, roaming profiles have resulted in issues with this

Error Code 30 issues or expired/invalid session errors:

  • If you are using a proxy such as a Bluecoat or Squid Proxy, ensure the proxy server does not cache-control any content from ebrary.

If you are still having trouble, visit the following diagnostic sites and send the results to us.

http://site.ebrary.com/validate
http://www.ebrary.com/kb/users/java_diag.jsp