During the past week, my colleague and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" workstation build (as opposed to our laptops). While doing that, we ran into a few errors by following these steps:
- Open up an MS word document via windows explorer (which uses WebDAV).
- Make a change.
- Save it.
We came to realize that some times (usually the first time) we saved the document, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.
We didn’t understand the root issue at this point, but we figured that we should make sure that the latest MS Office service pack had been installed on that work station. The IT folks went and did that. We went through the test again and we discovered a new problem. When we saved it, we now got this error:
This time, it seemed like every change was, in fact, saved, whether we answered Yes or No to the scripts question.
We finally had a look at the actual version of Office and it turns out that the workstation was running MS Office 2000 with service pack 3 which shows up under Help -> About as "Office 2002".
The moral of the story: I will always use Office 2003 as my minimum baseline office version when using WebDAV and MOSS.
</end>
(For search engine purposes, this is the error’s text):
Line: 11807
Char: 2
Error: Object doesn’t support this property or method
Code; 0
Do you want to continue running scripts on this page?
A sharepoint hotfix KB934525 changed the way that my older versions of Office interact with the document library. The hotfix was installed this weekend, and now my clients with older versions of Office (we use Office XP) are getting this exact error. On my personal computer I use Office 2007 and there is no error.
In my case, this is specifically caused by two custom fields I added to the properties of documents in the library. Because these fields are unset when saving a document a second web page pops up asking for the values to set for those fields. Prior to the hotfix this worked ok. After the hotfix I get the error with older versions of Office.
Office 2007 embeds the fields in the application and gives the user to choose the values when saving the document.
To avoid the error, login to sharepoint and set the values in the document properties. The user can then edit and save the document in Office XP without any error.
Geoff