1 Reply Latest reply on May 14, 2010 11:36 AM by jhaynes

    Failed report during transmission on 6.8.2 platform

      Guys, we are getting below error on report server logs, when reports are being transfered to portal any idea what can be cause here :

      -------------------------

      5/14/2010, 8:44:23 AM 0x02D8: OpenSSLSocket::Connected to [x.x.x.x:443] using [TLSv1/SSLv3][DES-CBC3-SHA]
      5/14/2010, 8:44:23 AM 0x02D8: Report Transmitter: Successfully connected to x.x.x.x on port 443, with SSL without Authentication.
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case HTTP_STATE_EMPTY / eHTTP_STATE_EMPTY - 0
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case HTTP_STATE_EMPTY / eHTTP_STATE_EMPTY - 1
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case HTTP_STATE_EMPTY / eHTTP_STATE_EMPTY - 1
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case HTTP_STATE_EMPTY / eHTTP_STATE_EMPTY - 1
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case HTTP_STATE_EMPTY / eHTTP_STATE_EMPTY - 1
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case HTTP_STATE_EMPTY / eHTTP_STATE_EMPTY - 1
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case eHTTP_STATE_BODY - 2
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: case eHTTP_STATE_COMPLETE - 3
      5/14/2010, 8:44:30 AM 0x02D8: Report Transmit failed, EM Server failed to write files.
      5/14/2010, 8:44:30 AM 0x02D8: Report Transmitter failed to process response.
      5/14/2010, 8:44:30 AM 0x02D8: ProcessResults: in catch(...) block - 3
      5/14/2010, 8:44:30 AM 0x02D8: Report Transmitter: Unexpected return code from Portal.
      5/14/2010, 8:44:30 AM 0x02D8: Error transmitting to portal. (Attempt: 2)
      5/14/2010, 8:44:35 AM 0x02D8: Error transmitting to portal. Attempting to continue transmit
      5/14/2010, 8:44:35 AM 0x0760: The Report Transmitter may have failed to deliver the report to an intended destination
      5/14/2010, 8:44:35 AM 0x0760: Unexpected error generating report.

        • 1. Re: Failed report during transmission on 6.8.2 platform
          jhaynes

          Not really enough to go on in that log. Your next clue will be in the IIS logs to see what it did with the post request. You can also look inside the config.ini file for the directory path to the reports_custom and reports directories and then verify that they exist in the proper locations.  Has this ever worked?  If so then what has changed since this last time this was working?

           

          I suggest you open up a case so we can take a look at this.

           

          Jeff Haynes