K
Kevin.Strange
Hi,
Over the past couple of weeks most of our users are getting an error on
Outlook 2003 (on XP SP3) after opening an attachment - seems to be of any
type though predominantly Excel and PDF's. They open an attachment, and
within 10 seconds or so, the warning "An attachment to this message may be
currently open in another program. If you continue, you may lose changes you
have made to the attachment using another program. Do you want to continue?"
This can occur even if they open the attachment and then do nothing else,
you can just sit and wait for the error to appear. However, it doesn't happen
all the time and there doesn't appear to be any pattern as to when it does.
It doesn't affect Vista/Outlook 2007. The user can generally click No and
the message will go away, though sometimes it returns immediately and the
only way to get rid of it is to close the attachment.
We're in the process of uninstalling the last batch of Microsoft updates to
see if any of these have caused it, but has anyone else experienced this
issue, and if so, have you solved it?
Thanks, Kevin.
Over the past couple of weeks most of our users are getting an error on
Outlook 2003 (on XP SP3) after opening an attachment - seems to be of any
type though predominantly Excel and PDF's. They open an attachment, and
within 10 seconds or so, the warning "An attachment to this message may be
currently open in another program. If you continue, you may lose changes you
have made to the attachment using another program. Do you want to continue?"
This can occur even if they open the attachment and then do nothing else,
you can just sit and wait for the error to appear. However, it doesn't happen
all the time and there doesn't appear to be any pattern as to when it does.
It doesn't affect Vista/Outlook 2007. The user can generally click No and
the message will go away, though sometimes it returns immediately and the
only way to get rid of it is to close the attachment.
We're in the process of uninstalling the last batch of Microsoft updates to
see if any of these have caused it, but has anyone else experienced this
issue, and if so, have you solved it?
Thanks, Kevin.