I recently migrated my Vista machine which runs Office 2007 from one domain
to another. I am a local administrator on my machine. After I changed domains
I found that I could open Outlook and read all my contacts/calendar... from
the original .pst file but was unable to edit or create new items without the
error which I stated in the Subject heading. I tried
uninstalling/reinstalling without resolution of the problem. I also created a
fresh(blank) .pst file and still I could not enter new data into a blank
..pst! Curiously, if I log onto the old domain (on the same computer), Outlook
can open the identical .pst file but is able to edit and create new items.

Since reinstalling did not help, I'm at a loss for what to do next. Is this
a problem with the Profile that was created when I logged on to a new domain?
--
Michael

hi

locate your .pst file, right click/properties/security - check
permissions, edit or add
permissions as required



"michael" wrote:

I recently migrated my Vista machine which runs Office 2007 from one domain
to another. I am a local administrator on my machine. After I changed domains
I found that I could open Outlook and read all my contacts/calendar... from
the original .pst file but was unable to edit or create new items without the
error which I stated in the Subject heading. I tried
uninstalling/reinstalling without resolution of the problem. I also created a
fresh(blank) .pst file and still I could not enter new data into a blank
.pst! Curiously, if I log onto the old domain (on the same computer), Outlook
can open the identical .pst file but is able to edit and create new items.

Since reinstalling did not help, I'm at a loss for what to do next. Is this
a problem with the Profile that was created when I logged on to a new domain?
--
Michael

Nope, permissions are just fine.

I can't get it to work even with a fresh (new) .pst file. However, if I log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights on
both domains).


--
Michael


"Anthony Baratta" wrote:

hi

locate your .pst file, right click/properties/security - check
permissions, edit or add
permissions as required



"michael" wrote:

I recently migrated my Vista machine which runs Office 2007 from one domain
to another. I am a local administrator on my machine. After I changed domains
I found that I could open Outlook and read all my contacts/calendar... from
the original .pst file but was unable to edit or create new items without the
error which I stated in the Subject heading. I tried
uninstalling/reinstalling without resolution of the problem. I also created a
fresh(blank) .pst file and still I could not enter new data into a blank
.pst! Curiously, if I log onto the old domain (on the same computer), Outlook
can open the identical .pst file but is able to edit and create new items.

Since reinstalling did not help, I'm at a loss for what to do next. Is this
a problem with the Profile that was created when I logged on to a new domain?
--
Michael

"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]

Did you name the profile the same name?

Try creating a new profile, using a different profile name.

Nikki

"Brian Tillman [MVP - Outlook]" wrote in message
...
"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I
log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's
works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights
on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]

Oh, another thing to look for:

Did you copy this pst onto your desktop from a CD?

If so, then select the properties of the file and turn off the
Read Only check mark. To select the properties, just
right click the file and select "Properties".

Nikki

"Nikki Peterson" wrote in message
...
Did you name the profile the same name?

Try creating a new profile, using a different profile name.

Nikki

"Brian Tillman [MVP - Outlook]" wrote in message
...
"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I
log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's
works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights
on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]

You're right about the permissions being the problem but not in a way I
suspected. Recall that the problem occurred when logged on to one domain but
not the other. The reason was that the "problem" domain as an ActiveDirectory
which suppressed the use of .pst files across the whole enterprise. The
Permission issue was a global one and not a local one.

I'm not sure there is a "fix" for that short of getting the the Permission
changed
--
Michael


"Brian Tillman [MVP - Outlook]" wrote:

"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]

Thanks. Turns out to be an ActiveDirectory Permissions thing rather than a
local problem.


--
Michael


"Nikki Peterson" wrote:

Oh, another thing to look for:

Did you copy this pst onto your desktop from a CD?

If so, then select the properties of the file and turn off the
Read Only check mark. To select the properties, just
right click the file and select "Properties".

Nikki

"Nikki Peterson" wrote in message
...
Did you name the profile the same name?

Try creating a new profile, using a different profile name.

Nikki

"Brian Tillman [MVP - Outlook]" wrote in message
...
"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I
log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's
works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights
on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]

I had similar issue every time trying to copy email for Inbox to a local
folder. I was getting this error message:
"cannot move the items. you don't have appropriate permission to perform
this operation"

I could create pst file, create folders into it but wasnt able to move any
item in it.

Turned out network admins had disabled pst files.


Solution:

Quick approach
Open regedit and search and delete these two entries,
PSTDisableGrow
DisablePST

Better approach
I found 2 places in registry for each entry (a total of 4). i created Reg
Delete command in cmd file and added the cmd file to startup program. This
way if network admins push this entry again through group policy or whatever,
I will revert the changes back.

Add these two lines of code to a cmd file.
Reg Delete
"Hkey_Current_User\Software\Microsoft\Office\12.0\ Outlook\12.0\Outlook" /v
DisablePST /f
Reg Delete "HKey_Current_User\SOftware\Microsoft\Office\12.0\ Outlook\PST" /v
PSTDisableGrow /f

Add this cmd file to startup program.

Remember to add a line similar to above for all the entries you find in
registry.



"michael" wrote:

You're right about the permissions being the problem but not in a way I
suspected. Recall that the problem occurred when logged on to one domain but
not the other. The reason was that the "problem" domain as an ActiveDirectory
which suppressed the use of .pst files across the whole enterprise. The
Permission issue was a global one and not a local one.

I'm not sure there is a "fix" for that short of getting the the Permission
changed
--
Michael


"Brian Tillman [MVP - Outlook]" wrote:

"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]

On Jul 27, 9:56*pm, Fearless
wrote:
I had similar issue every time trying to copy email for Inbox to a local
folder. I was getting this error message:
"cannot move the items. you don't have appropriate permission to perform
this operation"

I could create pst file, create folders into it but wasnt able to move any
item in it.

Turned out network admins had disabled pst files.

Solution:

Quick approach
Open regedit and search and delete these two entries,
PSTDisableGrow
DisablePST

Better approach
I found 2 places in registry for each entry (a total of 4). i created Reg
Delete command in cmd file and added the cmd file to startup program. This
way if network admins push this entry again through group policy or whatever,
I will revert the changes back.

Add these two lines of code to a cmd file.
Reg Delete
"Hkey_Current_User\Software\Microsoft\Office\12.0\ Outlook\12.0\Outlook" /v
DisablePST /f
Reg Delete "HKey_Current_User\SOftware\Microsoft\Office\12.0\ Outlook\PST" /v
PSTDisableGrow /f

Add this cmd file to startup program.

Remember to add a line similar to above for all the entries you find in
registry.



"michael" wrote:
You're right about the permissions being the problem but not in a way I
suspected. Recall that the problem occurred when logged on to one domain but
not the other. The reason was that the "problem" domain as an ActiveDirectory
which suppressed the use of .pst files across the whole enterprise. The
Permission issue was a global one and not a local one.

I'm not sure there is a "fix" for that short of getting the the Permission
changed
--
Michael

"Brian Tillman [MVP - Outlook]" wrote:

"michael" wrote in message
...

Nope, permissions are just fine.

Clearly not, if you can't open the PST.

I can't get it to work even with a fresh (new) .pst file. However, if I log
on to the old domain, I can edit/add objects(contacts, calendar events...)
without a problem to the same file. I can create a blank .pst and it's works
fine. Log back on to the new domain and I get the error we're discussing.

As far as user/domain rights, I have local admin rights(identical rights on
both domains).

Take ownership of the PST and you should be OK.
--
Brian Tillman [MVP-Outlook]- Hide quoted text -

- Show quoted text -

Thanks for the Procedure! Has the same Prob. Tnx!