Re: Cochrane 500 internal server error

Thanks Alex and Dom,

I received this message below early this morning. However, I might try
recommended fixes later if needed. I'm holding off until I hear back from
them Thank you very much, everyone.

Hi Penny,

*Cochrane Library*

Thank you for your inquiry regarding the above mentioned matter.

Please be advised that this is a known issue and our Highwire team is
currently working diligently to fix this issue.

I do apologize for any inconveniences caused.

Kind regards,



*Rashanda Young Journal Customer Services Global Customer Service Team *

On Mon, Nov 25, 2019 at 10:10 PM Petrie, Alex <[email protected]>
wrote:

> Hi Penny
>
>
>
> Not quite the same but we got that error when we were trying to create a
> search widget for the new interface. It occurs whether we use ezproxy in
> the code or not.
>
>
>
> This is the widget code (very messy and contains code that’s not needed
> because we were playing around with it to see if we could fix it) and error
> below.
>
>
>
> If we go direct to the Cochrane site with or without ezproxy it’s fine
> though.
>
>
>
> Cheers,
>
> Alex
>
>
>
>
>
> <p><img style="vertical-align: top;" src="
> https://login.smhslibresources.health.wa.gov.au/public/images/Cochrane_search.png"
> /></p>
>
> <form action="
> https://www.cochranelibrary.com/search?p_auth=s5EBisMJ&p_p_id=scolarissearchportlet_WAR_scolarissearch&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_scolarissearchportlet_WAR_scolarissearch_scolarisAction=redirectSearchResult"
> method="post" target="_blank">
>
> <input type="hidden" name="searchType" value="basic" />
>
> <input type="hidden" name="facetDisplayName" value="" />
>
> <input type="hidden" name="facetQueryTerm" value="" />
>
> <input type="hidden" name="facetQueryField" value="" />
>
> <input type="hidden" name="facetCategory" value="" />
>
> <fieldset class="fieldset">
>
> <legend class="sr-only">Basic Search</legend>
>
> <div class="select search-by">
>
> <select title="Search by options" aria-label="Search by options"
> name="searchBy" class="custom-select-enabled search-type">
>
> <option selected value="1">Title Abstract Keyword</option>
>
> <option value="2">Record Title</option>
>
> <option value="3">Abstract</option>
>
> <option value="4">Author</option>
>
> <option value="5">Keyword</option>
>
> <option value="6">All Text</option>
>
> <option value="7">Publication Type</option>
>
> <option value="8">Source</option>
>
> <option value="9">DOI</option>
>
> <option value="10">Accession Number</option>
>
> <option value="11">Trial Registry Number</option>
>
> <option value="12">Cochrane Group</option>
>
> <option value="13">Cochrane Topic</option> </select> </div>
>
> <div class="search-select-crg-container select" style="display: none;">
>
> <select class="search-select-crg-list"></select></div>
>
> <div class="search-select-topic-container select" style="display: none;">
>
> <select class="search-select-topic-list"></select> </div>
>
> <div class="search-text-container">
>
> <div class="control-group control-group-inline search-input-wrapper">
>
> <input type="text" size="30" class="field browser-search search-text
> ui-autocomplete-input" value="" aria-label="Enter search term"
> id="searchText" name="searchText" placeholder="Search">
>
> <div id="autocomplete-results"></div>
>
> </div>
>
> <div class="control-group control-group-inline search-button-wrapper">
>
> <button type="submit" class="searchByBtn" aria-label="Search">
>
> <i class="fa fa-search" aria-hidden="true"></i>
>
> </button>
>
> </div>
>
> </div>
>
> </form>
>
>
>
>
>
> *From:* EZproxy List [mailto:[email protected]] *On Behalf Of *Penny
> Hecker
> *Sent:* Tuesday, 26 November 2019 5:52 AM
> *To:* [email protected]
> *Subject:* [EZPROXY-L] Cochrane 500 internal server error
>
>
>
> Hello,
>
> Has anyone ever encountered an off-campus 500 internal server error with
> Cochrane, but after users have already successfully accessed Cochrane via
> proxy? The 500 error shows up after they've typed in a search. Instead of
> results they receive the 500 error. I have replicated the error in my
> attached screenshot.
>
> I don't think it's an EZproxy thing but it is happening only with
> off-campus access. Cochrane/Wiley is slow to respond to us. I hope to hear
> back from them tomorrow. Anyone familiar with this? We have EZproxy 6.5.2,
> Linux. Thanks.--Penny
>
>
>
>
>
> [image: Cochrane 500 error.png]
>
>
>
>
>
>
> --
>
> *.................................*
>
>  Penny Hecker, Associate Professor
>
>  eResources and Web Services Librarian
>
>  Sims Library | Southeastern Louisiana University
>
>  SLU 10896 Hammond, LA 70402
>
>  [email protected]
>
>  Voice: 985-549-2290 | Fax: 985-549-3995
>
>
>
>
> ------------------------------
>
> To unsubscribe from the EZPROXY-L list, click the following link:
> http://listserv.oclclists.org/scripts/wa.exe?SUBED1=EZPROXY-L&A=1
>


-- 
*.................................*
 Penny Hecker, Associate Professor
 eResources and Web Services Librarian
 Sims Library | Southeastern Louisiana University
 SLU 10896 Hammond, LA 70402
 [email protected]
 Voice: 985-549-2290 | Fax: 985-549-3995


********************************************************************
If you wish to stop receiving messages from EZPROXY-L or otherwise amend your preferences,
you can do so <a href="https://www.oclc.org/forms/internet-subscription.en.html">here</a>.
Or email [email protected] including the relevant text below in the body of the email:
• To unsubscribe: "unsubscribe EZPROXY-L"
• To receive EZPROXY-L in digest form: "set EZPROXY-L digest"
• To set your options to no mail: "set EZPROXY-L nomail"
• To receive these messages in the future "set EZPROXY-L mail"
To contact the list owners directly please send your message to [email protected].
If you unsubscribe from EZPROXY-L, you will no longer be able to participate in any of its features, including the public forum.
To unsubscribe from all OCLC marketing email communications
(including all OCLC listervs, OCLC Connect emails, OCLC event notifications, product/service/cooperative updates and newsletters),
please email us at [email protected].