I was trying to set some metadata attributes programmatically, but wasn't getting any results, by which I mean nothing happened. At all.
For example, the following code below would give me a confirmation dialog, but it wouldn't change the properties.
Finally, just to see what would happen, I decided to change the properties manually...and received an error message (see image).
Please advise.
Thanks!
--sun
@confirm
SetAttr META contentstatus:+draft
Does it work if you close the viewer pane?
No. I tried the code multiple times with the viewer pane closed, and that didn't work.
After setting it manually, I get an error as soon as I click Apply, so closing the viewer pane doesn't do me any good at that point.
Thanks, anyway.
Does the error only occur with that particular document?
Are you able to change any of the other fields successfully?
Results with a different document are the same. First, I tried it with the metadata pane closed by default. Then I opened the metadata pane and tried to change several other properties (see image).
Do you actually have Word installed on that machine? I don't know if this is true but it's possible setting properties on Office docs only works with Office installed.
Yes, I have Word 2010 installed, and I'm running 64-bit Windows 7.
Have you given up on me? It's been a week since I heard anything from you, and my metadata problem hasn't resolved itself. 
Just for kicks, I tried manually changing the metadata on a random Word file -- and yes I do have it installed -- but the same error occurred.
Please advise.
UPDATE! Those files are on a networked server. I'm an Administrator, and I have full control, but DOpus is not installed on the server. Instead, DOPus is installed on my desktop, and I've been using it to access the server as though it were just any old network location.
Just now, I tried to manually modify some metadata in a Word file on my desktop...and it worked! So:
[ul]ºThe files I need to manipulate are on a networked server
ºI have full control of the server
ºDOpus is not installed on the server -- nor will it ever be[/ul]
Now what? Any ideas?
It wouldn't make a difference if Opus was on the server or not.
What kind of server is it? Which OS and filesystem?
Can you edit attributes in those files via Word itself? Or via the system Properties dialog?
Yes, I am able to edit attributes both through the System Properties dialog and from within Word itself.
Server Info:
·Microsoft WSS 2003 R2
·Standard x64 Edition
·Service Pack 2
Also, SharePoint (MOSS 2007) is installed, but we're not currently using it.
Maybe Windows Storage Server 2003 R2 is behaving differently to a normal Windows network share in some way which is tripping things up.
It might be worth running Process Monitor, with its filter set to only show filesystem access below the folder in question, to see which operations dopus.exe (and anything else) is attempting on the file, and where it fails.
My bad. When I saw Windows Storage Server, that seemed weird to me, and I had to check it again.
It's actually just Windows Server 2003 R2. All the other info is the same. Does that make a difference in your recommendations? Not sure I can install Process Monitor without getting buy-in from IT Dept. (Just because they let me have my own server doesn't mean I can do anything I want with it. 
)
Process Monitor will be useful if it's Windows Server, too.
You'd want to install Process Monitor on your client machine, not on the server, so that you can see what Opus (on your client machine) is requesting and what the results are.
