M
Mark
I'm using the newest version (I believe) of the Outlook Connector for
Domino - 4/7/2004 - with Windows XP SP2 and Outlook 2003 SP1. While I
think this add-in was the best idea ever, I'm having a bit of a
problem.
As soon as I change a contact, task, email, or calendar entry,
outlook.exe starts taking up 99% of my CPU and won't ever relinquish
it until I shut it down.
I've been searching near and far for about a week now, and I can't
seem to find anyone else who's had this problem (with my config).
I've tried random things to try and fix it (updating service packs,
deleting/recreating .pst files, reinstalling notes client,
reinstalling office, letting outlook recreate certain .dat or .cmd
files according to other posts) to no avail.
Most recently I downloaded some utils to see exactly what Outlook.exe
was doing with 99% of my CPU and got some relief to see that it was a
low priority thread that wasn't doing much. So I have two questions:
1. Is anyone else seeing this?
2. Is this the way it was designed to work? (since it's a low
priority thread and it appears to have little effect on allowing other
applications to operate properly)
Any help is greatly appreciated.
Mark
Domino - 4/7/2004 - with Windows XP SP2 and Outlook 2003 SP1. While I
think this add-in was the best idea ever, I'm having a bit of a
problem.
As soon as I change a contact, task, email, or calendar entry,
outlook.exe starts taking up 99% of my CPU and won't ever relinquish
it until I shut it down.
I've been searching near and far for about a week now, and I can't
seem to find anyone else who's had this problem (with my config).
I've tried random things to try and fix it (updating service packs,
deleting/recreating .pst files, reinstalling notes client,
reinstalling office, letting outlook recreate certain .dat or .cmd
files according to other posts) to no avail.
Most recently I downloaded some utils to see exactly what Outlook.exe
was doing with 99% of my CPU and got some relief to see that it was a
low priority thread that wasn't doing much. So I have two questions:
1. Is anyone else seeing this?
2. Is this the way it was designed to work? (since it's a low
priority thread and it appears to have little effect on allowing other
applications to operate properly)
Any help is greatly appreciated.
Mark