Answers.Body: <p>I was able to solve this issue using the make blast db command in order to re create what was seemingly a corrupted database file. Hope this helps anyone who encounters a similar issue.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-08-27T07:13:16.577Z
Answers.Text: Please elaborate on the command which failed and how you corrected it. Edit your question instead of commenting on it.
Answers.UserDisplayName: Karthik Nair
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-08-26T17:59:27.353Z
Answers.LastActivityDate: 2024-08-26T17:59:27.353Z
Answers.UserDisplayName: Z_Gonzalez
Body: <p>I am currently attempting to run BLAST+ against a custom database using the following command:</p>
  <pre><code>&gt;\MATLAB\blast_plus\bin\blastn.exe -db genotype.fas -query C:\Users\jzl2\AppData\Local\Temp\1\tp2cdfa15f_9c682_4858_a298_6b0fd37d7674 -out C:\Users\jzl2\AppData\Local\Temp\1\tp7dfbbcd2_b0df_4206_a36a_d2517d67fcff
  </code></pre>
  <p>However, when running this command, I am getting the following error message:</p>
  <pre><code>Error: mdb_env_open: The system cannot find the path specified.
  </code></pre>
  <p>Any guidance as to what exactly this error means, the file it is referring to and how to go about a resolution would be much appreciated. In case it would be helpful to know, I am using an older version of Blast (v 2.11.0), but this has not been an issue until very recently.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-08-15T22:07:46.080Z
Comments.Text: Please show where the database you're trying to use can be found. `genotype.fas` is an unusual name.
Comments.UserDisplayName: gringer
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-08-22T20:32:46.290Z
Comments.Text: Hello. Thanks for the reply. I was actually able to fix this error by running make blast db. Turns out the database was corrupted and needed to be remade.
Comments.UserDisplayName: Z_Gonzalez
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-08-23T02:19:47.080Z
Comments.Text: Can you please add this as an answer? It will help other people encountering the same thing in the future.
Comments.UserDisplayName: gringer
Tags: <blast><blastn>
Title: BLAST+ error when running against a custom database: mdb_env_open: The system cannot find the path specified
ThreadText: # BLAST+ error when running against a custom database: mdb_env_open: The system cannot find the path specified
  
  (Asked by: username_0 on 2024-08-15)
  
  I am currently attempting to run BLAST+ against a custom database using the following command:
  
  ```
  >\MATLAB\blast_plus\bin\blastn.exe -db genotype.fas -query C:\Users\jzl2\AppData\Local\Temp\1\tp2cdfa15f_9c682_4858_a298_6b0fd37d7674 -out C:\Users\jzl2\AppData\Local\Temp\1\tp7dfbbcd2_b0df_4206_a36a_d2517d67fcff
  
  ```
  
  However, when running this command, I am getting the following error message:
  
  ```
  Error: mdb_env_open: The system cannot find the path specified.
  
  ```
  
  Any guidance as to what exactly this error means, the file it is referring to and how to go about a resolution would be much appreciated. In case it would be helpful to know, I am using an older version of Blast (v 2.11.0), but this has not been an issue until very recently.
  
  **Tags:** blast, blastn
  
  > **Comments:**
  > **username_1**: Please show where the database you're trying to use can be found. `genotype.fas` is an unusual name.  
  > **username_0**: Hello. Thanks for the reply. I was actually able to fix this error by running make blast db. Turns out the database was corrupted and needed to be remade.  
  > **username_1**: Can you please add this as an answer? It will help other people encountering the same thing in the future.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2024-08-26. Score: 0
  
  I was able to solve this issue using the make blast db command in order to re create what was seemingly a corrupted database file. Hope this helps anyone who encounters a similar issue.
  
  > **Comments:**
  > **username_2**: Please elaborate on the command which failed and how you corrected it. Edit your question instead of commenting on it.  
  
  ---
  
  