After the update to 6.0.8, all links to shared documents shows an error:
HTTP ERROR 500
Problem accessing /service/home/ACCOUNT@DOMAIN/FOLDER.
Reason:
Internal Server Error
Powered by Jetty://
The document folder works well for the owner, but is not reachable for all others.
Is ZimbraPublicServiceHostname correctly set for the domain?
No, it wasn't.
Every thing worked fine with the config till yesterday with 6.0.7.
Now after the update, it doesn't.
we have 2 domains: zimbra.wien.info and wien.info
so i did
zmprov md wien.info ZimbraPublicServiceHostname zimbra.wien.info
and after zmcontrol stop; zmcontrol start the error changed to
"Reason: 0"
What else can I do?
Note: Shared Briefcase Folder and Files do work properly - only shared documents don't!
As this is critical for us, I opened bug 50224
it's a known issue bug 50191. we'll be issuing a patch for this shortly.
Hi Brian,
It's not clear from the bug report if this issue impacts only non-US-EN language versions of 6.0.8 or all versions.
We and our clients make extensive usage of shared items within Zimbra, so we would hold off upgrading to 6.0.8 until the patch is released if this impacted US-EN 6.0.8.
Can you clarify please?
Thanks!
Mark
Hello Mark.
I'm the one who discovered the bug 50191.
https://bugzilla.zimbra.com/show_bug.cgi?id=50191
As you can easly see, all English languages are OK (Uk, USA and Australian).
I can assure you this bug ONLY affects non EN languages.
Best regards,
Leonardo Corato
Well, I'm sitting here with Release 6.0.8_GA_2661.UBUNTU8_64 UBUNTU8_64 FOSS edition in good old USA English, and I have this same problem. Unless there's a solution for the English-speaking versions that I have not been able to find yet....Quote:
Originally Posted by leocor
Joe
P.S. YES I have set zimbraPublicService Hostname appropriately....
Strange. When we switch to US.English, our shared documents work again.Quote:
Originally Posted by fcjoe
But this is only a workaround for a few users and not a solution for most of our german speaking users. We need the patch urgently!
Hi Leonardo,Quote:
Originally Posted by leocor
Thanks for the reply, but based on Joe's response I think we will wait for the patch.
FWIW, I appreciate Zimbra fixing this bug quickly, but as compared to other bugs there was less commentary in this one from Zimbra about the root cause(s) and scope of impact, which is why I posted here originally.
The bug report shows the fix was tested against "6.0.8 GA + P1" (Patch1?), so hopefully we will see a patch released soon.
Joe, once the patch is released I would be most grateful if you can report whether or not the patch fixes this for you please.
Best regards to all,
Mark