M
Mark
I have two systems that this has reproed on, although I'm
not positive it's OneNote that is causing the problem. I
had Office 2003 (Minus OneNote) installed on both
machines and had been using Outlook for months with no
issues. I then say a co-worker using OneNote and decided
to give it a try, so I downloaded and installed it from
my MSDN account. I installed OneNote then checked for
updates and there was a Office SP1 that I hadn't
installed, so I then applied the SP 1 update to all the
Office components that I had installed. This is when all
my woes began. It happened first on my desktop.
Everytime I open Outlook it crashes immediately, asking
to send an error report and re-open Outlook. This
morning after a reboot on my laptop, I can't open Outlook
there either. As soon as it opens it crashes! As soon
as it re-opens after the crash, it crashes again!
The only information I can find in the crash report is
the Exception Information code: 0xC0000094.
I need help on this desperately. I can't be the only
person to have had this issue, now that it's happened on
2 machines.
Thanks,
Mark.
not positive it's OneNote that is causing the problem. I
had Office 2003 (Minus OneNote) installed on both
machines and had been using Outlook for months with no
issues. I then say a co-worker using OneNote and decided
to give it a try, so I downloaded and installed it from
my MSDN account. I installed OneNote then checked for
updates and there was a Office SP1 that I hadn't
installed, so I then applied the SP 1 update to all the
Office components that I had installed. This is when all
my woes began. It happened first on my desktop.
Everytime I open Outlook it crashes immediately, asking
to send an error report and re-open Outlook. This
morning after a reboot on my laptop, I can't open Outlook
there either. As soon as it opens it crashes! As soon
as it re-opens after the crash, it crashes again!
The only information I can find in the crash report is
the Exception Information code: 0xC0000094.
I need help on this desperately. I can't be the only
person to have had this issue, now that it's happened on
2 machines.
Thanks,
Mark.