"Sarah" <(E-Mail Removed)> wrote in message news:<a3f101c406c0$368a3050$(E-Mail Removed)>...
> On a few machines, I'm having trouble with opening an
> attachment. When I go to view attachments.. it gives me
> a prompt *didn't used to* to open or save, then when I
> click open, it opens the system32 folder.
>
> If I click on save, it says "Cannot save the URL to a
> file. Path does not exist. Make sure path is correct."
> This same email is able to be opened from other identical
> machines.
>
Check out this post...it worked great for me! (Post wraps...sorry)
http://groups.google.com/groups?q=ou...ftngp05&rnum=5
Since it wrapped, I'll put the full text below:
_______________________________________________
Hello Dan,
I have the same problem and I've found a work around for it but I
too
would like to know the cause and see a real solution. Anyway the work
around
is this:
Go to the user experiencing the problem's profile (this problem should
be
per user not per system) typically this is:
C:\Documents and Settings\%UserName%
In this folder is a hidden folder called "Local Settings" which you
need to
go into. In Local Settings go to Temporary Internet Files and there is
a
subdirectory that starts with OLK (generally followed by an apparently
random number). This OLK* temp folder holds a copy of all the
attachments
the user has viewed and it will be recreated (though the number will
be
different) next time the user opens one but deleting it will
temporarily fix
the problem you are having. I have no idea why this works and as
stated the
solution is temporary and thus it will need to be repeated each time
the
problem arises.
Similarly we have a problem when automating the sending of emails with
attachments that causes it to fail after a few have been sent. Again
deleting this folder seems to solve the problem, again I don't know
why. I
would really like for there to be a more permanent solution to this,
as of
now I'm going to see if we can just try to add the deleting of this
folder
to the login script and maybe delete it after each automated email
(with
attachment) is sent. Obviously this is a less than ideal solution
though.
If anyone else can provide further insight to this problem it would be
much
appreciated.