Time Machine restore

24" iMac (late 2007)
Mac OS 10.6.1

Recently (since update to Snow Leopard?) I've found that I can't restore
folders that require administrative folders when logged into my working
administrative account.

All other administrative functions appear to work normally, but TM
restores fail with the message:

'The operation can¹t be completed because you don¹t have permission to
access ³<folder name>².'

If I switch to my "pristine" admin account, everything "just works" (tm).

Clearly there is something borked in (or with) my working admin account,
but I don't know what or where.

/etc/sudoers has not been touched since last June. where else should I
look?

TIA

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF

In article <tph-5253DB.09370311092009@localhost>,
Tom Harrington <> wrote:

> In article <tom_stiller->,
> Tom Stiller <> wrote:
>
> > 24" iMac (late 2007)
> > Mac OS 10.6.1
> >
> > Recently (since update to Snow Leopard?) I've found that I can't restore
> > folders that require administrative folders when logged into my working
> > administrative account.
> >
> > All other administrative functions appear to work normally, but TM
> > restores fail with the message:
> >
> > 'The operation can¹t be completed because you don¹t have permission to
> > access ³<folder name>².'
>
> Just to corroborate, I saw exactly the same thing a couple of days ago.
> I saw it on folders that shouldn't have required admin access, though--
> a folder in my home directory. I ended up using the command line to
> restore.

Actually, I had the same problem, but the "folder" was an encrypted
sparsebundle image and I thought the additional complication might
obscure the problem so I reported a simple folder in the /Applications
directory.
>
> > If I switch to my "pristine" admin account, everything "just works" (tm).
>
> Same here.
>
> > Clearly there is something borked in (or with) my working admin account,
> > but I don't know what or where.
> >
> > /etc/sudoers has not been touched since last June. where else should I
> > look?
>
> I haven't figured it out yet. I may end up just filing a bug with Apple.

I would too, but I'm not sure it it's _really_ a SL problem, or if
something else happened between the time of my last successful restore
and the installation of SL.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF

In article <tph-5253DB.09370311092009@localhost>,
Tom Harrington <> wrote:

> In article <tom_stiller->,
> Tom Stiller <> wrote:
>
> > 24" iMac (late 2007)
> > Mac OS 10.6.1
> >
> > Recently (since update to Snow Leopard?) I've found that I can't restore
> > folders that require administrative folders when logged into my working
> > administrative account.
> >
> > All other administrative functions appear to work normally, but TM
> > restores fail with the message:
> >
> > 'The operation can¹t be completed because you don¹t have permission to
> > access ³<folder name>².'
>
> Just to corroborate, I saw exactly the same thing a couple of days ago.
> I saw it on folders that shouldn't have required admin access, though--
> a folder in my home directory. I ended up using the command line to
> restore.
>
> > If I switch to my "pristine" admin account, everything "just works" (tm).
>
> Same here.
>
> > Clearly there is something borked in (or with) my working admin account,
> > but I don't know what or where.
> >
> > /etc/sudoers has not been touched since last June. where else should I
> > look?
>
> I haven't figured it out yet. I may end up just filing a bug with Apple.

Follow-up:

I did a complete restore of my system from the Time Machine backup.

The good news is that I can now selectively restore files and folders
using my working administrator identity.

The bad news is that now i get a dialog proclaiming:
You have Mail version 4.1 (1076/1075.2). It can't be used on Mac OS X
10.6.1 (Build 10B504). For more information, click the Help button.

None of the options shown by the help button work. The last option is
to reinstall Mail. As an experiment, I first replaced the Mail app with
Mail 4.0 from my external backup disk. On launch it went through the
same mail import procedure as on the first launch of Mail after the
installation of SL.

I'm not sure what to do next, but it seems as though my system is now
operational again.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF

In article <tom_stiller->,
Tom Stiller <> wrote:

> The bad news is that now i get a dialog proclaiming: You have Mail
> version 4.1 (1076/1075.2). It can't be used on Mac OS X 10.6.1 (Build
> 10B504). For more information, click the Help button.

That is strange because mail was updated to 4.1 with the Leopard 6.0.1
upgrade.

--
Member National Rifle Association
Member American Civil Liberties Union
Member Human Rights Campaign

In article <michelle->,
Michelle Steiner <> wrote:

> In article <tom_stiller->,
> Tom Stiller <> wrote:
>
> > The bad news is that now i get a dialog proclaiming: You have Mail
> > version 4.1 (1076/1075.2). It can't be used on Mac OS X 10.6.1 (Build
> > 10B504). For more information, click the Help button.
>
> That is strange because mail was updated to 4.1 with the Leopard 6.0.1
> upgrade.

Stranger yet is that the external drive from which I dragged Mail 4.0
had been updated to SL as a test before I updated my working system.
Why wasn't it at version 4.1? Why wouldn't the Mail app that reported
itself as version 4.1 work on SL 10.6.1?

I have never had a problem with a system upgrade before, but strange
things are happening.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF

On Sep 11, 11:26*pm, Tom Stiller <tom_stil...@yahoo.com> wrote:
> In article <tph-5253DB.09370311092009@localhost>,
> *Tom Harrington <t...@pcisys.no.spam.dammit.net> wrote:
>
>
>
>
>
> > In article <tom_stiller-A97F0C.11004911092...@news.verizon.net>,
> > *Tom Stiller <tom_stil...@yahoo.com> wrote:
>
> > > 24" iMac (late 2007)
> > > Mac OS 10.6.1
>
> > > Recently (since update to Snow Leopard?) I've found that I can't restore
> > > folders that require administrative folders when logged into my working
> > > administrative account. *
>
> > > All other administrative functions appear to work normally, but TM
> > > restores fail with the message:
>
> > > 'The operation can¹t be completed because you don¹t have permission to
> > > access ³<folder name>².'
>
> > Just to corroborate, I saw exactly the same thing a couple of days ago.*
> > I saw it on folders that shouldn't have required admin access, though--
> > a folder in my home directory. *I ended up using the command line to
> > restore.
>
> > > If I switch to my "pristine" admin account, everything "just works" (tm).
>
> > Same here.
>
> > > Clearly there is something borked in (or with) my working admin account,
> > > but I don't know what or where.
>
> > > /etc/sudoers has not been touched since last June. *where else should I
> > > look?
>
> > I haven't figured it out yet. *I may end up just filing a bug with Apple.
>
> Follow-up:
>
> I did a complete restore of my system from the Time Machine backup.
>
> The good news is that I can now selectively restore files and folders
> using my working administrator identity.
>
> The bad news is that now i get a dialog proclaiming:
> You have Mail version 4.1 (1076/1075.2). It can't be used on Mac OS X
> 10.6.1 (Build 10B504). For more information, click the Help button.
>
> None of the options shown by the help button work. *The last option is
> to reinstall Mail. *As an experiment, I first replaced the Mail app with
> Mail 4.0 from my external backup disk. *On launch it went through the
> same mail import procedure as on the first launch of Mail after the
> installation of SL.
>
> I'm not sure what to do next, but it seems as though my system is now
> operational again.
>
> --
> Tom Stiller
>
> PGP fingerprint = *5108 DDB2 9761 EDE5 E7E3 *7BDA 71ED 6496 99C0 C7CF

I'm getting the same error: "You have Mail version 4.1 (1076/1075.2).
It can't be used on Mac OS X
10.6.1 (Build 10B504)" after a complete restore from a time machine
backup.
Did you find a way to solve your problem???

Kind Regards,

Niels