2 Replies Latest reply on Jan 11, 2016 3:12 PM by A.T. Romano

    HTTP Status 500 Error

    ltcc2016

      Using Premiere Elements 13 and Windows 10 uploading to Vimeo. Got this error earlier this year when running Windows 7 and it was something to do with Adobe's services that they fixed on their end.

      Dear adobe, The error string is below. Please fix again and advise.

      Thanks.

       

      HTTP Status 500 -

      type Exception report

      message

      description The server encountered an internal error that prevented it from fulfilling this request.

      exception

      java.lang.NullPointerException

        org.apache.jsp.csp.error_jsp._jspService(error_jsp.java:171)

        org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:728)

        org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)

        org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)

        org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:728)

        com.adobe.ols.service.previmeo.filter.SessionFilter.doFilter(SessionFilter.java:74)

        com.adobe.ols.service.previmeo.filter.SessionCountingFilter.doFilter(SessionCountingFilte r.java:109)

        com.adobe.ols.service.previmeo.filter.NoCacheFilter.doFilter(NoCacheFilter.java:59)

        com.adobe.ols.service.previmeo.filter.CharacterEncodingFilter.doFilter(CharacterEncodingF ilter.java:48)

      note The full stack trace of the root cause is available in the Apache Tomcat/7.0.42 logs.

      Apache Tomcat/7.0.42

        • 1. Re: HTTP Status 500 Error
          A.T. Romano Level 7

          ltcc2016

           

          The HTTP Status 500 Error is not typically an Adobe error. In contrast, it is a problem with YouTube, Vimeo, and the like, and it gets fixed at the YouTube, Vimeo, or Facebook side of things.

           

          Until Vimeo works out the problem, can you upload your Premiere Elements 13/13.1 Timeline content to a file (AVCHD.mp4) saved to the computer hard drive and then from there upload it to Vimeo at the Vimeo web site?

           

          Within the next few hours, I will upload a Premiere Elements 13/13.1/Windows 10 64 bit Timeline to Vimeo using the Premiere Elements built in feature. The plan is to post those results before the end of the day (within the next 6 hours or sooner).

           

          Please consider.

           

          Thank you.

           

          ATR

          • 2. Re: HTTP Status 500 Error
            A.T. Romano Level 7

            Itcc2016

             

            I have had a chance to do upload of my Premiere Elements 14/14.1 Windows 10 64 bit Timeline to Vimeo using the Premiere Elements built in feature. It failed with the HTTP Status 500 message.

            I did the upload of my Premiere Elements 14/14.1 Windows 7 64 bit Timeline to Vimeo using the Premiere Elements built in feature. It failed with the HTTP Status 500 message.

             

            Because both failed, I did not continue to do these test using Premiere Elements 13/13.1.

             

            I then exported the same Timeline content to file (AVCHD.mp4 1920 x 1080p30) and saved it to the computer desktop. Then uploaded that file to Vimeo at the Video web site.

            No problems in doing that with Windows 10 64 bit.

             

            This issue is presenting as it had in the past where it pointed to a problem at the web site which was to receive the upload from the Premiere Elements built in feature. The answer that is forced is to wait until Vimeo, in this case, corrects the server at its side.

             

            The issue appears specific to Vimeo. There is no problem with the upload to YouTube using the same Premiere Elements 14/14.1 Timeline and the built in YouTube feature in Premiere Elements 14/14.1.

            Facebook was not looked at.

             

            More news as it developments on this Vimeo server issue.

             

            ATR