Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-24-2010, 07:18 AM
Trained Alumni
 
Posts: 6
Default Briefcase share issues after upgrade from 5.0.9 to 6.0.4

We did an upgrade from 5.0.9 to 6.0.4. It went off without a hitch or any errors. Once users started getting back in they complained of share issues. After investigating I came up with any user who tried to look at a document or download would get a 404 file not found error. I found that when the user opens something in the top level it would ask them for their credentials. They enter them open the file. Then they go back to the files the got the error on and they could open them.

I tried the fix in: [SOLVED] Shared Briefcase problems post 5.0.18->6.0.1 upgrade but it did not fix the issue. Any help would be appreciated!
Reply With Quote
  #2 (permalink)  
Old 03-25-2010, 04:55 AM
Trained Alumni
 
Posts: 6
Red face Bug# 43084

Found this is a known issue.

Bug#: 43084

Jud
Reply With Quote
  #3 (permalink)  
Old 05-07-2010, 10:49 AM
Trained Alumni
 
Posts: 6
Angry they closed the ticket

So they tested again and did not find the issue. Then they closed the ticket without a fix. They told me to hit the reopen button, but I cannot find it. Anybody else deal with this?

This is the tech response and testing, then my reply.

Tried

log in as jylee@zimbra.com on dogfood.zimbra.com
create /Obchod briefcase folder
create /Obchod/nabídka pro nového klienta briefcase folder
add testfile.txt in /Obchod/nabídka pro nového klienta folder
share /Obchod to test-jylee@zimbra.com on catfood.zimbra.com

log in as test-jylee@zimbra.com on catfood.zimbra.com
created mountpoint /sharetest for shared folder jylee@zimbra.com/Obchod
tried following URL and they all worked

https://catfood.zimbra.com/home/test....com/sharetest

https://catfood.zimbra.com/home/test...retest/nabídka pro
nového klienta

https://catfood.zimbra.com/home/test...retest/nabídka pro
nového klienta/testfile.txt
------- Comment #8 From Judson Edwards 2010-04-26 07:40:45 [reply] -------
That does not work for us. Problem is that after the upgrade it changed the
share file destination from one name to another. As a work around we are able
to change the address of the file to the correct one and get in. Using your
example

"https://catfood.zimbra.com/home/test-jylee@zimbra.com/sharetest/nabídka pro"

Everything points to "catfood.zimbra.com" however the box it resides on is
"dogfood.zimbra.com" when you "click" the share files it changes "catfood" to
"dogfood"

Our workaround for all users is to have the users go to the address bar and
change the address from dogfood to catfood and you can access the file.
Reply With Quote
  #4 (permalink)  
Old 05-07-2010, 11:06 PM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Quote:
Originally Posted by jmyeds View Post
So they tested again and did not find the issue. Then they closed the ticket without a fix. They told me to hit the reopen button, but I cannot find it.
A Bug's Life Cycle
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 05-10-2010, 02:42 PM
Trained Alumni
 
Posts: 6
Default

Right and I click on that and it takes me to definitions, not how to reopen. Talked to a QA and he said click the "reopen" radio button next to staus. I do not know what I am doing wrong but I have no radio button. I tried Chrome, IE and Firefox. No button
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.