OUTLOOK.EXE not shutting down in Task Mgr/Proesses

[denmarfl]

Running Outlook 2007; Vista 32Bit. Of late, if I open Outlook and it loads
slowly.....or, loads but does not show the reading Pane (its Blank), when I
shutdown Outlook....look at Task Mgr Prosesses.....I see OUTLOOK.exe still
running in the Processes List. If I manually END TASK, Outlook will usually
open fine. But the process will repeat itself after just a few openings.

I have 1) Run Scanpst, 2) I have run Microsoft Small Office REPAIR.

Suggestions to correct? Thanks

 

[K. Orland]

Try the troubleshooting steps listed here:

http://www.howto-outlook.com/faq/outlookdoesntclose.htm

 

[denmarfl]

I have disabled Add-ins, I have disabled AntiVirus....I have NO PDA, IPOD or
FAX Programs, I have no RRS running...problem continious. Here is what I
have noticed. I know when Outlook.exe doesn't close in Processes\Task Mgr.
I'll manually END PROCESS Outlook.exe in Task Mgr so I know its closed. I
can start Outlook 3 or 4 times fine. Then Outlook will opens VERY Slowly,
and I don't see the SEND\RECEIVE notification in the bottom right corner, and
when Outlook finally loads its at a point beyond the SEND\RECEIVE process.
If I close it following this un-normal Loading, go to Task Mgr, Outlook.exe
is in the Process List.

Does this maybe provide add'l helpful information that may lead to a fix?

 

[K. Orland]

Have you seen anything Outlook or Office related in your Application Event
Viewer?

 

[denmarfl]

Looking at Event Viewer.....I see a "Bunch" of LEVEL Warnings.....with todays
date & Times....SOURCE...Microsoft Office 12 Sessions; EVENTS show 7003 (all
entries are the same). Bottom of Event Viewer reads "ID 6, Appl Name:
Microsoft Office Outlook Version 12.0.6316.5000, Microsoft Office Version :
12.0.6215.1000. This session was Terminated unexpectively. When I clicked on
EVENT LOG ONLINE HELP.....it opened...Sorry, nothing found.

I am certain these 7003 errors are the problems I am experiencing......As I
look back to yesterday 7/29, when I encountered no problems (and I added nor
did I delete, or chnage anythingon my PC)....I saw no 7003 errors.

 

[Brian Tillman]

I am certain these 7003 errors are the problems I am
experiencing......As I look back to yesterday 7/29, when I
encountered no problems (and I added nor did I delete, or chnage
anythingon my PC)....I saw no 7003 errors.

Did you try starting Outlook with the /safe command switch to see if that
made a difference?

 

[K. Orland]

Do you have Windows Desktop Search installed? If you do, uninstall it to see
if that improves anything.

 

[denmarfl]

How would I know? I looked thru Prossess and Services.....and saw nothing
that read Windows Desktop Search. What would be the correct way to look for
this service running? Is it perhaps labeled with a different name?

 

[denmarfl]

Is that when you use RUN and type Office 12/Safe??????? What is the exact
command...and it would be entered in RUN?

 

[Brian Tillman]

Is that when you use RUN and type Office 12/Safe??????? What is the
exact command...and it would be entered in RUN?

In the Open field of the Run dialogue, enter

outlook.exe /safe

Be sure to include the space.

 

[K. Orland]

This wouldn't be a service or profile. Check Add/Remove Programs in the
Control Panel.

 

[Scotch]

Hello denmarfl

I just came across your post.

You are describing exactly the same symptoms which I and, it seems, many
other users have experienced - and which are described in the separate thread
headed "Outlook 2007 reading pane gone blank" - which I began in this forum
on 17 March and has to date attracted 63 follow-up posts. I hope you should
be able to find the thread easily using the search facility.

I would speculate that your problems may be related to MS updates KB946983
and/or KB952142. You could try uninstalling those updates and see whether
the problems go away, which is my own experience. If not, you can easily
re-install the updates again.

If you do a web search on 'KB946983' and/or 'KB952142', you will see that
those two updates appear to have many unintended effects for Outlook users
worldwide and that I am not the first person to suggest removing them until
the causes are fixed or until an alternative solution is officially published.

It might be useful if anyone who reads this and finds that the solution
works (or that it doesn't, or that there is now a better way) could please
add a message here saying so.

Hope this is helpful.

Cheers,
Scotch