tag:blogger.com,1999:blog-15200454.post1799359625334247264..comments2023-09-12T09:38:46.195-04:00Comments on SharePoint: Exception (0x81071003): Unable to update the information in the Microsoft Office documentMorten Marquardhttp://www.blogger.com/profile/07373568346464812598noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-15200454.post-33551994416783900502009-11-20T06:29:43.411-05:002009-11-20T06:29:43.411-05:00I have this problem too. I was able to fix it usin...I have this problem too. I was able to fix it using OLE Automation object which removes all custom properties of the document. But I can't do anything when I haven't MS Word installed. Maybe somebody knows how to get rid of these fields?Maksym Dykhtiarukhttps://www.blogger.com/profile/17261362151611002695noreply@blogger.comtag:blogger.com,1999:blog-15200454.post-5982653933111254092009-08-10T14:44:44.415-04:002009-08-10T14:44:44.415-04:00Re-installing MSXML 6.0 worked for me.
ThanksRe-installing MSXML 6.0 worked for me.<br /><br />ThanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-15200454.post-20834671491536808852009-05-07T22:19:00.000-04:002009-05-07T22:19:00.000-04:001) The issue was with property promotion/demotion ...1) The issue was with property promotion/demotion of this file while saving metadata during check-in process.<br />2) I saved this file as .XLSX in 2007 format and uploaded it; I successfully checked in the file.<br />3) Then I downloaded this copy on my local system; opened it and saved it in .XLS format.<br />4) This copy was then uploaded and successfully checked in to the library in question. (all the metadata properties were pre filled in advance from the earlier .XLSX file downloaded from SP site); hence any issues related to property promotion and demotion were removed.Himani Sharmahttps://www.blogger.com/profile/01120735018189594482noreply@blogger.comtag:blogger.com,1999:blog-15200454.post-47426843851381326942008-04-15T07:29:00.000-04:002008-04-15T07:29:00.000-04:00Thanks lennin. That's very helpful, indeed!However...Thanks lennin. That's very helpful, indeed!<BR/>However, do you know why this problem might occur in the first place. Is this to do with the way the document was created etc.?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-15200454.post-88134008339743312802008-01-22T12:34:00.000-05:002008-01-22T12:34:00.000-05:00Edit the document, (in Office 2003) Go to File, Pr...Edit the document, (in Office 2003) Go to File, Properties, Custom Properties then choose any property like client and type any value, then click add then close the dialog and save the document. After this you should be able to upload/save the document in the document library without problems.Lenninhttps://www.blogger.com/profile/14846580258794510974noreply@blogger.comtag:blogger.com,1999:blog-15200454.post-8880663824698059232007-10-23T09:32:00.000-04:002007-10-23T09:32:00.000-04:00Try (re)installing MSXML 6.0 on the sharepoint ser...Try (re)installing MSXML 6.0 on the sharepoint server.<BR/>This should help...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-15200454.post-31563494082323726332007-09-28T07:20:00.000-04:002007-09-28T07:20:00.000-04:00Dear Matt,I found a potential workaround that some...Dear Matt,<BR/>I found a potential workaround that somehow fixed my problem.<BR/><BR/>What I did was to modify the TemplatesPath when loading the document in VBA - og voila, the problem disappeared. Excellent.<BR/><BR/>Quite strange thoughMorten Marquardhttps://www.blogger.com/profile/07373568346464812598noreply@blogger.comtag:blogger.com,1999:blog-15200454.post-43338889725009548262007-09-17T13:24:00.000-04:002007-09-17T13:24:00.000-04:00Did you ever find out why this was happening and w...Did you ever find out why this was happening and what you could do to work around it?<BR/><BR/>ThanksUnknownhttps://www.blogger.com/profile/03722907961250968763noreply@blogger.com