Outlook 03,07 "another workstation has modified it"

tw33k · 09 Apr 2010

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

Barman58 · 09 Apr 2010

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 · 12 Apr 2010

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 · 12 Apr 2010

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 · 12 Apr 2010

ccatlett1984 said:

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.