Outlook 03,07 "another workstation has modified it"

[ptm82379]

Ok this is making me mad now.

I am starting migration and my testers are still having problems.

Their pst files lock up and the "another workstation has modified it" error pops up

Before you head me off I know that pst's are not supposed to be stored in a network setting but I dont have a choice.

Is there A way to fix or work around this.

Does it have to do with roaming profiles?

If you start task mgr and end the outlook process it usually fixes the problem but the majority of my users cannot do this.

Please help me out guys.

 

[ptm82379]

nobody???

 

[ptm82379]

I still have a couple of guys that run scanpst.exe daily. This is still a big problem for me. I have got to come up with a solution other than storing pst's locally. Any ideas???

 

[ptm82379]

Getting some new ones now...We ended up putting the pst in a network folder that can only be accessed by that user, no one else. We are still getting the "another workstation has modified it" error but some new ones now

 

[ccatlett1984]

Maybe start by giving a better idea of how your email system is setup internally?

 

[ryo]

do you already check,,when you sharing and put the .pst file into network folder. that's have permissions access?? because i ever do the same case with you, when i migrate the pst file,not issue i get.

 

[ptm82379]

do you already check,,when you sharing and put the .pst file into network folder. that's have permissions access?? because i ever do the same case with you, when i migrate the pst file,not issue i get.

Yes, Permissions were set to allow only the specified user access to the file. We tried it with no permission rules with the same result, so we changed permissions to test...getting the same result.

I might add that we have 200 other users on XP and this has NEVER been an issue.

 

[ptm82379]

bump for fresh ideas

 

[ryo]

bump for fresh ideas

http://www.sevenforums.com/tutorials/73585-pst-file-corrupted-repair.html

maybe this can help you..try this step and post your progress.

 

[ptm82379]

Been there... I run scanpst daily...Mine did it again yesterday right after a reminder.

 

[tw33k]

Do they each have their own pst or are they sharing? Why do you need the pst on a network drive?

 

[Barman58]

Couple of things to try - if you are using a UNC address to access the share try the mapped drive route ans vice versa - the issue could be connection type related.

Also check the permissions on all the files in the user folder-both the NTFS and Sharing permissions - most work on a outlook file is actually on temporary files so that they need protecting also - I assume that each user has their own share for locating the PST?

 

[ptm82379]

Correct Barman58 they have their own shares. I have tried both routes on UNC pathing and Mapped drives. Actually the mapped drive route gave me more issues than drilling down in UNC. I think the problem lies here as well. I will check all permissions again but I dont think there are any issues there.

Thanks for your input

 

[ccatlett1984]

I wish they would make it Best Practice to put the .pst file on a network share, that way if the pc dies the user isn't screwed. At my old job, we had a "h:\" mapped through a startup script when the user logged into the computer, that is where the .pst file was placed. It does sound like a permissions issue with the share itself. Try browsing to the the share as the user, then create a new folder. Put the .pst into that folder and see what happens.

 

[ptm82379]

I wish they would make it Best Practice to put the .pst file on a network share, that way if the pc dies the user isn't screwed. At my old job, we had a "h:\" mapped through a startup script when the user logged into the computer, that is where the .pst file was placed. It does sound like a permissions issue with the share itself. Try browsing to the the share as the user, then create a new folder. Put the .pst into that folder and see what happens.

I did. I created a folder and set permissions so that only that user could do anything with or to it. I still got the "another workstation modified it"

We have to do it to keep track of sensitive emails. If that were left up to the user then everyone who crashes is indeed screwed (not to mention us). That is funny...I use h:\ as a network drive as well.