no handler was found for GET

[eswbitto]

Hello everyone,

I'm having a peculiar issue regarding just one file in our Alfresco installation.

Our install
4.2.d on Centos 6.4 w/ Apache as the SSL connection.

I have a site with site managers that have an issue with one excel spreadsheet file. This file is accessed multiple times a day by different people. When one user logs in to make a change to the file it doesn't show that the file is locked. (I'm guessing it only shows locked when you do offline editing)

When they go to do online editing it launches M$ office or (sharepoint protocol). There is an error message that reads the file is locked. I've attached the two files that come up.

I know for sure that no one has the file open when trouble shooting this issue. The only way that I can fix the issue is to download a copy of the file. Then delete the file in Alfresco. Then upload the copy. Then the users are able to access the file again.

When looking into catalina.out I am getting this INFO message.

INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for HEAD to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices/1314 Learning Camp Invoice Tracker.xlsx'
08:50:43,445  INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for GET to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices/1314 Learning Camp Invoice Tracker.xlsx'
09:02:58,976  INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for HEAD to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices/1314 Learning Camp Invoice Tracker.xlsx'
09:02:59,293  INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for OPTIONS to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices'
09:02:59,862  INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for GET to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices/1314 Learning Camp Invoice Tracker.xlsx'
09:03:00,315  INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for GET to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices/1314 Learning Camp Invoice Tracker.xlsx'
09:03:00,680  INFO  [vti.web.VtiRequestDispatcher] Note - no handler was found for GET to uri='/hcos-learning-camps/documentLibrary/Deposits, Invoicing, Transfers/Invoices/1314 Learning Camp Invoice Tracker.xlsx'
‍‍‍‍‍‍‍‍‍

When looking for errors or warnings the only thing that is remotely in the same time frame is this warning.

WARN  [webscripts.connector.RemoteClient] [http-apr-8080-exec-35] Exception during close() of HTTP API connection
 ClientAbortException:  java.io.IOException
‍‍‍‍

I can't find any other topics on this issue. So I am at a loss.

[4lfr3d7115]

I have the same problem. Did you fixed?
Comunnity 4.2.e on Centos 6.4 w/ Apache

[4lfr3d7115]

The solution:

http://forums.alfresco.com/forum/end-user-discussions/alfresco-share/42c-cannot-savemovedeletecancel...


I'm also affected by this bug on 4.2.c

I think what you're experiencing is bug ALF-17725/ALF-18283, which itself seems to be a regression of bug MNT-2239. I experienced it myself and was able to reproduce it as follows:

    Create a new site
    Upload a document (.odt for example)
    Click "Edit Offline"
    You now have two different nodes: the "workign copy" and the "original"
    The "original" node could be accessed by clicking on "View Original Document" in the "working copy" document actions
    The "working copy" node could be accessed by clicking on "View Working Copy" in the "original" document actions
    If you click "Cancel Editing" on the "working copy" everything works fine
    If you click "Cancel Editing" on the "original" it apears to work, but both the "working copy" and the "original" are now permanently locked, i.e. can't be deleted, unlocked, replaced with new version, etc.

This bug seems to be fixed in Enterprise version (see ALF-18283), but there's also an interim solution to unlock affected documents described in one of the MNT-2239 comments. Whatch the cleanup video posted in the comments, upload javascripts from the ticket's attachments, follow the steps and you should have your document back.

Good luck!
—

Sergei