Answers.Body: <p>Ironically, I found that this problem was caused by the fact that the tables are too large!
  They really should have designed the correct error messages!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-31T12:48:32.307Z
Answers.LastActivityDate: 2019-10-31T12:48:32.307Z
Answers.UserDisplayName: Code42
Body: <p>I was running <a href="https://cibersort.stanford.edu" rel="nofollow noreferrer">CIBERSORT</a> but caught this error right after it started permutation:</p>
  
  <pre><code>org.rosuda.REngine.Rserve.RserveException: eval failed, request status: error code: 127
  88
  </code></pre>
  
Tags: <rna-seq><cibersort>
Title: CIBERSORT runtime error eval failed
ThreadText: # CIBERSORT runtime error eval failed
  
  (Asked by: username_0 on 2019-10-31)
  
  I was running [CIBERSORT](https://cibersort.stanford.edu) but caught this error right after it started permutation:
  
  ```
  org.rosuda.REngine.Rserve.RserveException: eval failed, request status: error code: 127
  88
  
  ```
  
  **Tags:** rna-seq, cibersort
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-10-31. Score: 1
  
  Ironically, I found that this problem was caused by the fact that the tables are too large!
  They really should have designed the correct error messages!
  
  
  ---
  
  