Upgrading from 4.0.5

[Dirk]

Now that 4.5 RC2 is available, I'm eager to try it out, but I tried RC1 and recieved the message "Cannot upgrade from 4.0.5" the installer dropped out and left me with a destroyed remnant of zimbra. No problem, restore from backup, and try again, still didnt work, restore from backup and give up.

So, is it worth trying RC2? Should RC1 have worked?

Full version number: Release 4.0.5_GA_518.SuSE10_20061218035837 SuSE10 FOSS edition

Thanks

[phoenix]

It should work, did you file a bugzilla report? Did you post to the forums about the problem? What was in the logs? I'd try it again and file a report if it doesn't work.

[Dirk]

Thanks Bill, it was late when I tried RC1, lots of other stuff had gone wrong and I just wanted to get the server back up so I didnt check the logs.

So, I just completed the RC2 install, it went through to the end and I can the services have started, so that's all good, but it looked like a lot of errors were thrown to the screen during the install.

I've looked at the log file for the install, from the end of the script where it reports "Operations logged to /tmp/zmsetup.log.29388" but cannot see them. So I'll explore the software and make sure it's all working.

Long story short, RC2 worked where RC1 did not, so that's good news for the GA.

[Dirk]

Holy Crap!!! The whole thing looks different! Seems faster too

Fantastic

I tried the html client too, but that failed:

HTTP Status 500 -

type Exception report

message

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

exception

org.apache.jasper.JasperException: File "/h" not found
	org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
	org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
	org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:114)
	org.apache.jasper.compiler.JspUtil.getInputStream(JspUtil.java:838)
	org.apache.jasper.xmlparser.XMLEncodingDetector.getEncoding(XMLEncodingDetector.java:105)
	org.apache.jasper.compiler.ParserController.determineSyntaxAndEncoding(ParserController.java:304)
	org.apache.jasper.compiler.ParserController.doParse(ParserController.java:169)
	org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
	org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:155)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	com.zimbra.webClient.filters.CharEncodingFilter.doFilter(CharEncodingFilter.java:45)
	com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:323)

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

[phoenix]

Yes, neat isn't it? I like the new tabs.

I'd report that problem with the new 'lite' client in bugzilla. Did you click on the 'switch to the basic client' message in the login box?

[Dirk]

I didnt even see that button, I just used the https://server/zimbra/h url listed in one of Kevins earlier posts, however, he actually wrote it as https://server/zimbra/h/ . Notice the trailing forward slash? With that, it works, without it it seems to fail.

Can anyone else confirm this?

[phoenix]

Can anyone else confirm this?

Yes, I can confirm that. You need the trailing '/' if you type it in manually. I don't know if the trailing slash is a bug.

[Dirk]

Righto, so far I'm well impressed, mainly with the speed - it's just so much faster, props to the team for (presumably) optimising the code so much.

Are tasks enabled in this release? I seem to have a folder in my email tree called "Tasks - renamed (286:1168349608)" ?

[phoenix]

No, I don't think the Tasks feature is in this release. I think it's scheduled for later this year, hasn't it been mentioned on the forums somewhere? Just found it here.

[dkarp]

We created a new system Tasks folder in advance of the Tasks app (coming in a post-4.5 release). Your existing Tasks folder got moved out of the way to accommodate.