S
Steve Bursch
I am using Outlook 2000 SP-3 on Windows XP Pro. It was
running fine for many months but then recently developed
a problem during program launch.
Upon launch, I get the following error dialog box message
from Outlook:
"An extension failed to initialize. Can't open file:
C:\Documents and Settings\Steve Bursch\Local
Settings\Application Data\Microsoft.... The file may not
exist, you may not have permission to open it, or it may
be open in another program. Right-click the folder that
contains the file, and then click Properties to check
your permission for the folder. You don't have
appropriate permission to perform this operation."
The problem occurs everytime I launch MS Outlook, even if
it's the very first program I launch after booting the
system. If I respond "OK" to the error dialog, Outlook
appears to complete its launch, but it's unclear whether
it's okay to continue using it. It seems to be okay, but
I'm not sure.
Unfortunately, the error dialog message does not include
the full pathname of the file that's in trouble.
Consequently, I don't know how to troubleshoot the
problem. Using "Detect and Repair..." from the Office
Help menu did not fix the problem. Does anyone have any
advice for me?
Thanks...Steve Bursch
running fine for many months but then recently developed
a problem during program launch.
Upon launch, I get the following error dialog box message
from Outlook:
"An extension failed to initialize. Can't open file:
C:\Documents and Settings\Steve Bursch\Local
Settings\Application Data\Microsoft.... The file may not
exist, you may not have permission to open it, or it may
be open in another program. Right-click the folder that
contains the file, and then click Properties to check
your permission for the folder. You don't have
appropriate permission to perform this operation."
The problem occurs everytime I launch MS Outlook, even if
it's the very first program I launch after booting the
system. If I respond "OK" to the error dialog, Outlook
appears to complete its launch, but it's unclear whether
it's okay to continue using it. It seems to be okay, but
I'm not sure.
Unfortunately, the error dialog message does not include
the full pathname of the file that's in trouble.
Consequently, I don't know how to troubleshoot the
problem. Using "Detect and Repair..." from the Office
Help menu did not fix the problem. Does anyone have any
advice for me?
Thanks...Steve Bursch