Can't open any "My Documents" Vista Bugs and Problems Discuss Can't open any "My Documents" in the Windows Vista forums; When I try to open Office documents. a window pops up saying I don't have authority or the document is encrypted. That also applies to Adobe saved documents....

[jphuffs]

When I try to open Office documents. a window pops up saying I don't have authority or the document is encrypted. That also applies to Adobe saved documents.

[Znod]

You can try giving yourself full permissions on the folders and taking ownership of them.

[jphuffs]

Sounds good. How do I do that?

[Znod]

Right click on a folder, then go Properites > Security to give yourself full permissions. After doing so, click on Advanced (under Security) and use Owner to take ownership.

[Snuffy]

TAKEOWN [/S system [/U username [/P [password]]]]
/F filename [/A] [/R [/D prompt]]

Description:
This tool allows an administrator to recover access to a file that
was denied by re-assigning file ownership.

Parameter List:
/S system Specifies the remote system to
connect to.

/U [domain\]user Specifies the user context under
which the command should execute.

/P [password] Specifies the password for the
given user context.
Prompts for input if omitted.

/F filename Specifies the filename or directory
name pattern. Wildcard "*" can be used
to specify the pattern. Allows
sharename\filename.

/A Gives ownership to the administrators
group instead of the current user.

/R Recurse: instructs tool to operate on
files in specified directory and all
subdirectories.

/D prompt Default answer used when the current user
does not have the "list folder" permission
on a directory. This occurs while operating
recursively (/R) on sub-directories. Valid
values "Y" to take ownership or "N" to skip.

/? Displays this help message.

NOTE: 1) If /A is not specified, file ownership will be given to the
current logged on user.

2) Mixed patterns using "?" and "*" are not supported.

3) /D is used to suppress the confirmation prompt.

Examples:
TAKEOWN /?
TAKEOWN /F lostfile
TAKEOWN /F \\system\share\lostfile /A
TAKEOWN /F directory /R /D N
TAKEOWN /F directory /R /A
TAKEOWN /F *
TAKEOWN /F C:\Windows\System32\acme.exe
TAKEOWN /F %windir%\*.txt
TAKEOWN /S system /F MyShare\Acme*.doc
TAKEOWN /S system /U user /F MyShare\foo.dll
TAKEOWN /S system /U domain\user /P password /F share\filename
TAKEOWN /S system /U user /P password /F Doc\Report.doc /A
TAKEOWN /S system /U user /P password /F Myshare\*
TAKEOWN /S system /U user /P password /F Home\Logon /R
TAKEOWN /S system /U user /P password /F Myshare\directory /R /A

[Znod]

I like my way better.

[jerrybasham]

Originally Posted by Znod

Right click on a folder, then go Properites > Security to give yourself full permissions. After doing so, click on Advanced (under Security) and use Owner to take ownership.

That doesn't work. Something is screwy in this OS
and is causing inaccessability to owner's documents
at intermitant times. I have no access to any of
my documents (work, school, etc) and my computer is
now useless to me except as a web browser.

This is the most disgusting thing to happen since
the crashy days of 95 and 98 when reinstallations
were the only solution to get a machine going again.

I sent a bug report to MS and snapshots of the
error messages.

Meanwhile, I have to start over on over four hundred
lost documents; my boss is rather livid. And so am
I.

-- Jerry

[crabby]

You havent replied to this post for 2 months... did it work in the past?

Well... if owning the documents doesnt work there is definately an issue somewhere.

I note you have not posted any of these errors here?

If you could, we may be able to research into it more.

crabby

[jerrybasham]

It's a simple applet that says "access to (name of
folder and file path) is denied."

I did a search for "access denied" and this thread
came up this morning. I was not aware that when
the posts were first made is an issue. Maybe
there's some updated info somewhere at this site,
but for now this is all I found; that's why I
began a new thread in this same "bugs" area.

Nevermind. I'll google around and look at the
Microsoft newsgroups, too.

It's just that this is the first time in all my
computing experience that I'm actually having a
Windows bug cost me real money at work. I have
to take responsibility, though, because I'm the
one who bought this thing knowing it was a new
OS, unproven, etc. I was fine with XP at work,
but had to have the latest (but now so greatest).

[jerrybasham]

Well, I found the reason, here:

http://www.jimmah.com/vista/Security/junctions.aspx