TweakNow 2006 problem

Hi,

A while ago I ran the reg cleaner of TweakNow 2006 on my PC and it screwed up Outlook 2003 to the point that I can only run it in safe mode. I tried it again on another PC and the same thing happened. I reinstalled the entire Office suite 3 times but Outlook still refuses to work in normal mode. I guess something in the registry is missing or needs to be corrected. Does anyone have any experience with this problem?

 

Since it works in Safe mode, I would suspect a bad add-in. (safe mode doesn't use them)

I would disable them all:

1. Open Outlook
2. Select 'Options' from the 'Tools' menu
3. On the 'Options' dialog, select the 'Other' tab
4. Press the 'Advanced Options' button
5. On the 'Advanced Options' dialog, press the 'Add-In Manager' button
6. Uncheck all add-ins
7. Apply your settings.

Now, you can try starting outlook in normal mode. If it works, enable each add-in, one at a time until you find the problem one.

If that's not the problem, we can clean up views and the profile, but we'll cross that bridge when we get to it.

 

Thanks for the quick response.

There's only one add-in (Exchange Extensions Property pages) and that was unchecked.

 

Okay, then the next step I would try is this:

Start --> Run

outlook /cleanviews
outlook /cleanprofile

(one at a time, of course)

 

Okay, did that!

Either one pops up Outlook.

 

Okay, now, I can't recall whether this is Outlook in safe mode or not.... can we launch Outlook normally, now?

 

It pops up and after about 6 to 7 seconds an error message pops up that Outlook has encountered a problem and needs to close. That was the exact reason why I started the safe mode thing in the first place.

 

Ahh!
Well, usually when this happens, the reason is recorded in the event logs.

Let's look there for more information:

1. Right-click 'My Computer' and select 'Manage'
2. On the 'Computer Management' window. expand 'Event Viewer'
3. Select the 'Application' log
4. Look for red x's that correspond with the Outlook crashes.
5. Post back with the event ID number, the source, and the exact error description. (It may be easier to just take a screenshot)

 

Here's the screenshot.

Thanks again for all your help.