Skip to content

advanced search | help

Known Issues and Bugs

Connecting from Home (Proxy Server)
Electronic Reserves
Streaming Media
Other

Connecting from Off-Campus (Proxy Server)

Error message: "Couldn't decode pre-session cookie" Hitting Refresh will attempt to resubmit your request
Proxy server sessions "expire" after a certain period of inactivity. If you receive the above error message, refreshing your browser's window will attempt to re-join your proxy session. In some cases this may fail. You will need to close your browser and re-start the proxy server or use our bookmarklet to jump back into the proxy server.
Reviewed: March 16, 2011

Electronic Reserves

Popup blockers affect faculty management of e-reserves
Faculty managing their own e-reserves need to disable the popup blockers in order to transfer files to ERes
Reviewed: March 16, 2011
PDF Files may not display with certain Security Settings in Internet Explorer
Internet Explorer may not display E-Res PDF files if certain Internet security settings are turned on. These include checking the "Do not save encrypted pages to disk" in Advanced Internet Options or having the Internet Security level set to "medium" or "high".
Reviewed: March 16, 2011

Streaming Media

Intermittent video and/or audio drop-out with Quicktime 7.6 for Windows

If you are experiencing intermittent video and/or audio drop-outs (e.g. blank screen w/audio, screen but no audio, etc...) while using Quicktime 7.6 for Windows, open Quicktime Preferences and select "Safe Mode (GDI Only)."

"Live Broadcast Paused", "Error 403: Forbidden" or audio dropout

If you receive these error messages or experience audio dropout the problem could be caused by one of three issues:
1) The firewall on your personal computer blocking access to the stream. You must configure your firewall to allow the Quicktime Player to communicate with the Internet. Consult the manufacturer of your firewall software if you are unsure how to grant this access.
2) You may have paused the stream for more than one minute. Paused streams timeout after 60 seconds of inactivity.
3) Your connection speed and/or the capacity of your computer's CPU may be too limited to access streaming reserves. If your firewall is configured correctly and your are not pausing the streams for more than 60 seconds, we recommend you try accessing your streaming reserves from one of the Libraries' computers.

"Error 404: No found"

If you receive this error message please try back in a few minutes. If the problem persists please let us know. See "Ask Us" below for contact information.

"Error 461: Unsupported Transport"

If you receive this message you may be trying to open the stream with a player other than the Quicktime Player (e.g. RealPlayer). Streaming reserves should be accessed with the latest free version of the Quicktime Player. Blank browser windows and dialog boxes
When launching streams from certain browsers a dialog box and blank browser window appear. Click "cancel" to remove the dialog box and then close the blank browser window. Ask Us

If you continue to experience technical difficulties with streaming reserves contact us here.

Other

Proxy autodetect feature in the Zotero browser plug-in causes seemingly random prompts for UW NetID login
If you are prompted for a UW NetID login when trying to visit web sites you should have access to, chances are that the proxy auto-detect/redirect feature in the Zotero browser plugin is interfering with your browsing experience. To resolve this issue you will need to disable the proxy features in Zotero. A short tutorial on how to do this is available at http://faculty.washington.edu/murata/zotero/zoteroproxyconfig_med.html.
Updated: March 16, 2011
Security Alert error dialog when accessing secure site (https:// URLs)
When attempting to access secure sites via https:// URLs (e.g., MyUW, electronic reserves readings), the browser raises a Security Alert dialog box and complains that the site's "security certificate has expired or is not yet valid".
Check the system date on the client workstation; an incorrect system date will often trigger this error message.
Reviewed: March 16, 2011

Contact Us
Last modified: Wednesday March 16, 2011 (jlward1)