XP-Home SP3, Outlook 2007

Outlook disappears from the SysTray persistently. This is not due to
windows explorer crashing.

Is this a known defect.
--
TUT

"Progress always involves risk; you can't steal second base and keep your
foot on first."

Urbane Tiger a.com> wrote:

I've not heard of it. The only time Outlook disappears from the tray for me
is when I close it. Do you have any error messages displayed? Does
anything appear in the Event log?

No messages, nothing in logs that I can see.

The process is running I can see it with ProcessExplorer, if a new mail
arrives the popup pops and the envelope is in the tray. I can click the new
mail icon in the tray read the mail, answer it if need be, and the envelope
goes away as it should.

If I start Outlook from Quick Menu then it starts immediately, I don't think
it allows multiple instances - that's fine by me, I only want one. When I
minimize I get nothing in the tray.

When this happens I just use the QuickLaunch, no loss of performance, its
just not where I expect it to be sometimes I kill it with ProcessExplorer
and restart from QuickLanch - voila its back in the tray. So its no big
deal.

Urbane Tiger a.com> wrote:

Well, I'm stumped. Have you customized the notifications in the system
tray? If so, does removing all customizations (i.e., always showing all
icons) change anything?

No that's not it

But what I've noticed is that sometimes Outlook is running as a Service -
you can see that with Process Explorer, can't remember if it runs under a
service host or direct under services

I fixed it by installing Dave Levinson's Shutdown addon - apparently its a
common problem for Outlook to be execute out of sight.

--
TUT

"Man who says something cannot be done should not interrupt man doing it" --
Chinese Proverb

--------------------------------------------------------------------------
"Brian Tillman" yahoo.com> wrote in message
news:#Knpemv9IHA.1448@TK2MSFTNGP02.phx.gbl...

Urbane Tiger a.com> wrote:

Outlook never runs as a service, as far as I can tell. It's clearly not
listed in the Services console.

Still running after being closed is not the same as running as a service.
It usually means you have a misbehaving add-in that isn't allowing Outlook
to close properly.

Before I added Shutdown the only addon was Outlook Connector, does it that
misbehave?

Next week, when I'll have more time, I'll uninstall the Shutdown addon and
try to induce the Outlook as a service behavior and document here.
--
TUT

"Progress always involves risk; you can't steal second base and keep your
foot on first." -- Frederick Wilcox

--------------------------------------------------------------------------

If you look at this http://rapidshare.com/files/136711452/Procexp.txt.html

then you'll see 5 OUTLOOK processes, three parented by wlmail and two
parented by explorer

there are no OUTLOOK icons in the Systray nor the Taskbar

can someone please explain what's going on, its driving me nuts - the only
add on I have is Outlook Connect

--
TUT

"Man who says it cannot be done, should not interrupt man doing it." -
Chinese proverb
--------------------------------------------------------------------------

"Urbane Tiger" a.com> wrote in message
news:#f9cy6A$IHA.1452@TK2MSFTNGP02.phx.gbl...

Urbane Tiger live.com.au> wrote:

Check your "URL:MailTo Protocol" file type association (the "open" action).
In IE, check the settings for E-mail in Tools>Internet Options>Programs.

It is : "C:\PROGRA~1\MI1933~1\Office12\OUTLOOK.EXE" -c IPM.Note /m "%%1"

It is : Microsoft Office Outlook.

HTML Editor is : swriter
Newsgroups is : Windows Live Mail.
Internet Call is : Skype,
Calendar is : Microsoft Office Outlook
Contacts is : Microsoft Office Outlook

I think WLMail is a player in this game. I think I only get these problems
with Outlook if WLMail is running when I start or stop Outlook - if it is
not present then I don't think I get the problems.

Similarly if I exit WLMail and Outlook is loaded then WLMail will tell me
that it can't compress its database, because another program is using a
file. I would not have though the two app's shared much of anything, apart
from functionality.