Forum Discussion

AndiiiA's avatar
AndiiiA
New Contributor
7 months ago
Solved

OCR service failed to process the document

Since the your maintenance today we're encountering an OCR issue:

 

Details:
Image dimension: 46x41
Size: 755 bytes
Hash: 363b161c3a2f0e4d1c3dc9ca5607c401
Request execution time: 469 ms
Server: https://ocr.api.dev.smartbear.com
Status code: 500 (Internal Server Error.)
Error message: remaining connection slots are reserved for non-replication superuser connections.
 
Does anybody have the same problem? Is it a server issue?
  • vinniew's avatar
    vinniew
    7 months ago

    Hi All 

     

    I have tried replicating this on 15.55 / 15.53 and 15.50 

     

    It seems like it is working

     

    Can you check again ? 

13 Replies

Sort By
  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    7 months ago

    Hi,

     

    There was an e-mail notification from SmartBear that they will have license server maintenance today (on Monday, Oct 23). This might be the reason of the problem.

     

    • Barry_R's avatar
      Barry_R
      New Contributor
      7 months ago

      Aware of the email but that should have finished by now.

       

  • jrsbr's avatar
    jrsbr
    Contributor
    7 months ago

    We received that email on Friday 20th Oct after 1700 local when we had just finished for the weekend.  SmartBear defo need to improve their coms to match the efforts of their sales and marketting team.

  • Barry_R's avatar
    Barry_R
    New Contributor
    7 months ago

    Yes also having the same issue.

    The OCR service failed to process the document.

    Details:
    Image dimension: 61x30
    Size: 105 bytes
    Hash: e5abc0f9b0c325f4b7b3ac536b1308da
    Request execution time: 375 ms
    Server: https://ocr.api.dev.smartbear.com
    Status code: 500 (Internal Server Error.)
    Error message: remaining connection slots are reserved for non-replication superuser connections.

  • AndiiiA's avatar
    AndiiiA
    New Contributor
    7 months ago

    Still not working. I opened a ticket on the case management portal.

    • vinniew's avatar
      vinniew
      Staff
      7 months ago

      I can see there was an internal defect raised for our dev team which was being worked on today. 

       

      It seems like this has been solved 

  • vinniew's avatar
    vinniew
    Staff
    7 months ago

    Hi All 

     

    I have tried replicating this on 15.55 / 15.53 and 15.50 

     

    It seems like it is working

     

    Can you check again ? 

    • AndiiiA's avatar
      AndiiiA
      New Contributor
      7 months ago

      Works also on our side now. The SmartBear Team also replied to our submitted ticket that it should work now, thanks.