A strange behaviour of my OL2007 under Vista:
Onc I quit OL it cannot be restarted, other than by logging out and in again.
If I try to restart, the turning ring turns for a couple of seconds and then
nothing...
Does someone recognizes this and knows the solution?
TIA, Oriolus

Oriolus wrote:

A strange behaviour of my OL2007 under Vista:
Onc I quit OL it cannot be restarted, other than by logging out and
in again.

Open Task Manager (CTRL-Shift-Esc) and click the Processes tab. Look for
OUTLOOK.EXE. If you find it, select it, and choose End Process. Outlook
should start again when you click its icon.
--
Brian Tillman

"Brian Tillman" wrote:

snip
Open Task Manager (CTRL-Shift-Esc) and click the Processes tab. Look for
OUTLOOK.EXE. If you find it, select it, and choose End Process. Outlook
should start again when you click its icon.
--
Brian Tillman

Thanks Brian,
I foud out myself that this is an option, but is this a bug, and should this
be forwarded to Microsoft? Can I do that in a way?
Or, as a work around, have I to quit Outlook in a different way to not
necessarily use the task manager, that only should be used if one gets stuck?
TIA

Oriolus wrote:

I foud out myself that this is an option, but is this a bug, and
should this be forwarded to Microsoft?

Perhaps.

? Can I do that in a way?

If you have a retail version of Outlook, open a support incident.

Or, as a work around, have I to quit Outlook in a different way to not
necessarily use the task manager, that only should be used if one
gets stuck?

Use the Task Manager only if OUtlook gets stuck. Reasons why it might can
be found he http://www.howto-outlook.com/faq/outlookdoesntclose.htm
--
Brian Tillman

"Brian Tillman" wrote:

snip
Use the Task Manager only if OUtlook gets stuck. Reasons why it might can
be found he http://www.howto-outlook.com/faq/outlookdoesntclose.htm
--
Brian Tillman

It's not that I cannot close Outlook, it's the problem that I cannot open it
again after closing. You are right that by using the taskbar to quit a
'hanging' OUTLOOK.EXE, I can restart it again. So the problem is created as
if OL2007 isn't properly closed. Many times even, if I log out and in again,
Windows reports on trying to open OL2007 (by shortcut in StartUp folder) that
OL2007 wasn't properly closed in the previous sesion, and asks if I want OL
to check the database for integrety (errors). As far as I can remember there
never was an error to be repaired when I tried to get OL restarted until I
found (and you suggested) to use the taskbar in stead of logging out and in
again.
Is there a MS representative reading this post?
Welcoe to comment!
TIA, Oriolus

Oriolus wrote:

So the problem is created as if OL2007 isn't properly closed.

See if any of the informaiton here helps:
http://www.howto-outlook.com/faq/outlookdoesntclose.htm
http://www.slipstick.com/problems/close.htm
--
Brian Tillman

"Brian Tillman" wrote:

Oriolus wrote:

So the problem is created as if OL2007 isn't properly closed.

See if any of the informaiton here helps:
http://www.howto-outlook.com/faq/outlookdoesntclose.htm
http://www.slipstick.com/problems/close.htm
--
Brian Tillman

Great Brian, I downloaded KnockOut. Thanks a lot.
Strange that Microsoft doesn't do anything to solve this problem and that
other people should create helpful software to circumvent Microsofts
shortcomings. And it's not OL2007 only; no, already ten years seem to
experience this problem in all previous versions...
Again thank you for your adequate help!
Oriolus

Oriolus wrote:

Great Brian, I downloaded KnockOut. Thanks a lot.
Strange that Microsoft doesn't do anything to solve this problem and
that other people should create helpful software to circumvent
Microsofts shortcomings.

In the vast majority of cases, the fault les with third-party software that
is supposed to interact with Outlook and does not do so correctly. You
cannot blame Microsoft for that.
--
Brian Tillman

"Brian Tillman" wrote:

snip
In the vast majority of cases, the fault les with third-party software that
is supposed to interact with Outlook and does not do so correctly. You
cannot blame Microsoft for that.
--
Brian Tillman

I don't understand: OL2007 and Vista are both Microsoft products. If I quit
OL, is by doing so a 3rd party (software) involved? I read something about
anti virus or spyware. I can imagin that for a short time those programs do
some inspection if OL is getting ne mail etc. But cannot OL detect whether
the database (i.e. the .pst file(s) e.a.) is in use, wait a while before
quitting, and if it lasts too long, tell me that OL cannot quit at the
moment, but will do that as soon as the database e.a. are released? Why can
KnockOut simply do that job, but not OL itself?
Probably this goes to far in detail, but TMHO: if Microsoft needs 3rd
parties, it should co-operate in such a way that not a '4th' party is needed
to solve its problems...

Oriolus wrote:

I don't understand: OL2007 and Vista are both Microsoft products. If
I quit OL, is by doing so a 3rd party (software) involved?

Depends on whether or not you installed third-party software that integrates
with Outlook. Did you?

I read something about anti virus or spyware. I can imagin that for a
short
time those programs do some inspection if OL is getting ne mail etc.
But cannot OL detect whether the database (i.e. the .pst file(s)
e.a.) is in use, wait a while before quitting, and if it lasts too
long, tell me that OL cannot quit at the moment, but will do that as
soon as the database e.a. are released?

That can't happen because the third-party software isn't allowing the
Outlook process to terminate. Outlook requires exclusive access to the PST,
so there are no other applications accessing the PST. The third-party
application iis preventing Outlook from running its exit routines.

Why can KnockOut simply do that job, but not OL itself?

KnockOut is forcing process termination which, by the way, could result in
PST corruption, since it's not a normal process run-down.

Probably this goes to far in detail, but TMHO: if Microsoft needs 3rd
parties, it should co-operate in such a way that not a '4th' party is
needed to solve its problems...

Outlook doesn't "need" third-party software. If other companies want to
write software that integrates into Outlook and they don't do it correctly,
that's not Microsoft's problem and they have no obligation to make it their
problem. Again, it's usually NOT Outlook's problem but improperly written
software that someone other than Microsoft wrote.
--
Brian Tillman