Can not open attachments on a new GA version

[gutzeit]

When I try to open an attachment, I get the following error :

HTTP Status 404 - /public/ZimbraMailNewCompose.jsp

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

type Status report

message /public/ZimbraMailNewCompose.jsp

description The requested resource (/public/ZimbraMailNewCompose.jsp) is not available.


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

Apache Tomcat/5.5.7

[phoenix]

Which browser, which operating system and what type of attachment is it?

I've just done a test with pdf, txt, bin, gif and html files on a CentOS4 with FF 1.2.0.1 without any problems - they all open or save correctly.

[gutzeit]

Firefox 1.5 and IE 6.0.
Attachment type is .eml (another email).

OS is RHE4, Update 2

[phoenix]

I guess you'll have to wait for one of the Zimbra guys then, I've just forwarded an email to myself and had no problems opening it.

[KevinH]

Attached mail is working for me as well. Can you do 'View Original' and attach a zip'd result to this thread?

[kelley.ch]

I as well have the same issue -- error:

HTTP Status 404 - no such item

type Status report

message no such item

description The requested resource (no such item) is not available.
Apache Tomcat/5.5.15

This is a Critical problem...

[kelley.ch]

msg - upload not found: adea8f41-9c55-4225-af71-83be5426fbf2:56d424ca-a84d-4467-87ae-99c20d836b82
com.zimbra.cs.mailbox.MailServiceException: upload not found: adea8f41-9c55-4225-af71-83be5426fbf2:56d424ca-a84d-4467-87ae-99c20d836b82
at com.zimbra.cs.mailbox.MailServiceException.NO_SUCH _UPLOAD(MailServiceException.java:194)
at com.zimbra.cs.service.FileUploadServlet.fetchUploa d(FileUploadServlet.java:163)
at com.zimbra.cs.service.mail.ParseMimeMessage.attach Uploads(ParseMimeMessage.java:478)
at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:267)
at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:155)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:91)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:255)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:228)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

code - mail.NO_SUCH_UPLOAD
method - ZmCsfeCommand.prototype.invoke
detail - soap:Sender
data - [object Object]

[jholder]

Try to log out and log back in. it looks like the auth token expired.

[Dirk]

I've had similar experiences before, our users are under instructions that "if anything strange happens, press F5 before calling me"

Which refreshes the page and reloggs the user of course, it does solve most odd glitches.

[bobby]

that error looks like what happens when you've got windows logged in to multiple accounts open in the same browser

Bug 3846
File upload doesn't work with multiple client sessions