Hi all,
it took us some time to receive the bugfix and I tested it today and it is working just fine. I got the confirmation as well that the fix will be available in the April CU.
Sorry but I could not tell you more before, as I was asked to post no information about the progress etc.
Best of luck
Norbert
Hello All,
We have released a fix for this that will be part of the upcoming CU release. In can be downloaded now seperately from the hotfix site. This fix is server side as the issue is generated from SharePoint and not the client. So plan you installation of the fix accordingly. If anyone is using Office 365, operation are currently in the process of installing this patch and you should be seeing a change in the behavior soon.
The patch can be found here:
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2598261&kbln=en-us
Regards,
Michael Ma
I am experiencing a similar SAOP error when syncing Workspace after certain content is uploaded to SharePoint. I am trying to find exactly what content that are causing the problem by uploading bits of content at the time, but does anyone know a better way? Is there any logs or debug options that will tell my which file that are triggering the error message?
Best Regards,
Christian G H
Tyler Huntley
We are sorry for the delay but this is a complex fix that impacts other facets of the SharePoint Server. We are continuing to work on this fix and at this time do not have a release date as we look to ensure the integrity of the fix for release.
Regards,
Michael Ma
Norbert,
One of my environments is having this issue, has Microsoft contacted you about a estimated release date for the hotfix yet?
Thanks,
Scott
Dear all,
we have received an update from MS on friday. MS requested a Hotfix request internally. This needs to be evaluated and will take some time. Hopefully we will receive a hotfix request soon.
Somehow some columns from the content types we use are duplicated in the XML which cause the problem only in the SharePoint Workspace.
At the moment there is not much to do than wait for the hotfix.
Best regards
Norbert
Hi Michael,
we are still facing this problem. The strange thing is that for some libraries the copying is helping and for others it is not.
Do you have any further information what might be the cause?
Thanks a lot.
Best Regards
Norbert
This issue does not appear to be strictly related to managed metadata. Microsoft is currently investigating this issue and will post back if a solution is found.
Removing the "required" property for a managed metadata column doesn't apply at all times. I was able to sync another document library with required columns for managed metadata or lookup types.
I used the workaround mentioned by Dejan i.e. copying files into my local machine. Note, copying from a SharePoint library within the same site also doesn't help since I believe it carries over any corruption that may have happened to the files. The only drawback of that approach is losing the version history of the documents.
Fred
http://fyano.wordpress.com/
Hi,
yes I opened a ticket with Microsoft. Together with the company Metavis which we used for data migration, we figured it out. It seems that the source of the problem are columns which use managed metadata and are set to be required. In this combination the error occurs with old office documents. We established a new libary and set the columns not to be required and it works fine, even with old documents. Microsoft had problems to reproduce the error but had a similar behaviour. I dont know if there will be a hotfix for this, but we finally found a workaround.
Hope this helps.
Regards Norbert
Dear all,
I spent some time now figuring out this error and hope that I found the cause.
I tried the copy and paste approach and created new libraries and the error occurred still. I am not running any Profile Synchronisation service and therefore I doubt a connection.
What I noticed that the synchronisation did not stop immediately and the sync was succesful with some documents. So I deleted all folders and files and started moving files back to the library and double checking the sync status. Basicly all files seemed to work expect one type of files. When I moved old office files with the common extensions xls, doc or ppt to the library the error started and no sync was possible. I found two solutions for this, but they are not really practical when you have migrated thousand of old documents.
1. Before Uploading you open the file and save as an Office 2007 / 2010 document. Upload the file try to sync and its working.
2. This is not really useful but I tried to narrow it down. You can open the doc, to to File --> Info --> Inspect Document --> Remove All found data --> Save the file and it is working. In this case you have to retag all documents.
As I am not 100 % sure about this I would be glad if any of you could confirm this. At least I found an error pattern so I hope thats one step to solve this strange error. I will open a ticket with MS to solve this, as it is not feasable to manually change all docs.
Thanks and Cheers
Norbert
I was considering that approach myself. There are a coniderable number of content types and workflows I also need to review prior to doing so.
I am not entirely sure, which are the problem documents either. However, I did save the problem document library as a template and used that to re-create another. and even though it creates the document library based on that template, it comes up with an error. I am going to test the syncing with that document library and if it syncs ok, will gadually move folders over in way, which will avoid loosing metadata.
Thanks for the message and i'll also post here if I find a solution.
Dear All,
I found a workaround for this problem but I still don`t know how/why this happened.
1. Use a drag&drop method to copy all problematic content from SharePoint Workspace to a local computer
2. Recreate a new library and delete the old one
3. Move everything back to a new library (usually you don`t need to tag documents again)
Hope this helps,
BR,
Dejan Lugonja
I still haven't got a resolution. It appears that all document libraries are fine apart from one of them, where I keep getting the same error. I have checked the event logs and the problem appears to have happened after there was an issue with the Profile Synchronisation service. Can you check the same? I looked at the date of the last document that was downloaded to the client and looked at SharePoint's application logs.
Thanks.
