<p>This happens.</p>
<ol>
<li>One possibility is it's simply NCBI blocking the request to avoid being overrun by e.g. bots. This occurs if you've been running the script repeatedly within a single day. It will be fine tomorrow in this scenario.</li>
<li>The second possibility is you've not supplied an email address.</li>
<li>The final possibility is if you're running a VPN. NCBI has taken a strong dislike to VPN's <em>per se</em>, I've never figured out its algorithms - it seems to permit a fixed number of requests then pointedly refuses. Just turn off the VPN.</li>
</ol>
<p>If its point 2 then understanding how you've coded this would be useful to allow an email address to be sent. Biopython has a function for this. I just use Biopython BTW.</p>

CC BY-SA 4.0
2023-04-14T11:59:18.803Z
2023-04-14T15:05:57.593Z
2023-04-14T15:05:57.593Z
M__
<p>After a long time not running EDirect, I got an error when I tried using it. It said,&quot; curl: schannel: next InitializationSecurityContext failed: Unknown error (0×80090367) - There is no common application protocol between the client and server...
I tried using WiFi and hotspot, but it did not work.
Additional info:
1- I ran EDirect on Cygwin64 Terminal on my personal computer with Windows 11 operating system.
2- I first ran 'export PATH=<span class="math-container">${PATH}:$</span>{HOME}/edirect'. After that, I tried 'esearch -db pubmed -query &quot;stroke AND english [FILT] AND has abstract [FILT] NOT review [PTYP]&quot; | efilter -mindate 2000 | efetch -format xml | xtract -pattern PubmedArticle -element PMID AbstractText &gt; dm_cs.txt'</p>
<p>I used to ran it successfully on the same PC over WiFi or hotspot three month ago.</p>

CC BY-SA 4.0
2023-04-14T11:11:43.747Z
Please [edit] your question and add: i) your operating system, ii) the _exact_ command you tried to run and iii) tell us if there is anything special about your setup (are you behind a firewall? are you connecting over ssh or something similar? anything else relevant).
terdon
CC BY-SA 4.0
2023-04-14T11:52:57.717Z
Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking.
Community
<curl><edirect>
No common application protocol between the client and server? An error when using Entrez Direct
# No common application protocol between the client and server? An error when using Entrez Direct

(Asked by: username_0 on 2023-04-14)

After a long time not running EDirect, I got an error when I tried using it. It said," curl: schannel: next InitializationSecurityContext failed: Unknown error (0×80090367) - There is no common application protocol between the client and server...
I tried using WiFi and hotspot, but it did not work.
Additional info:
1- I ran EDirect on Cygwin64 Terminal on my personal computer with Windows 11 operating system.
2- I first ran 'export PATH=${PATH}:${HOME}/edirect'. After that, I tried 'esearch -db pubmed -query "stroke AND english [FILT] AND has abstract [FILT] NOT review [PTYP]" | efilter -mindate 2000 | efetch -format xml | xtract -pattern PubmedArticle -element PMID AbstractText > dm\_cs.txt'

I used to ran it successfully on the same PC over WiFi or hotspot three month ago.

**Tags:** curl, edirect
> **Comments:**
> **username_1**: Please [edit] your question and add: i) your operating system, ii) the _exact_ command you tried to run and iii) tell us if there is anything special about your setup (are you behind a firewall? are you connecting over ssh or something similar? anything else relevant).  
> **username_2**: Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking.  

---

## 1 answers

### Answer by username_3 on 2023-04-14. Score: 1

This happens.

1. One possibility is it's simply NCBI blocking the request to avoid being overrun by e.g. bots. This occurs if you've been running the script repeatedly within a single day. It will be fine tomorrow in this scenario.
2. The second possibility is you've not supplied an email address.
3. The final possibility is if you're running a VPN. NCBI has taken a strong dislike to VPN's *per se*, I've never figured out its algorithms - it seems to permit a fixed number of requests then pointedly refuses. Just turn off the VPN.

If its point 2 then understanding how you've coded this would be useful to allow an email address to be sent. Biopython has a function for this. I just use Biopython BTW.


---

