Outlook shutdown failure after downgrading from 2003 to 2000

N

Nic

A user had been using outlook 2003 to access e-mail on an exchange 2000
server. The user was then moved to an older PC with an older version of
outlook (Outlook 2000). Now outlook 2000 will not close or shutdown
properly. We have tried applying Office 2000 SP3, but this has made no
difference. The "Please wait while Microsoft Outlook exits" dialog box
remains on screen - the only way out is to log off the PC, or terminate the
application within task manager. This has happened to multiple users who
have used outlook 2003 to access their mailboxes, and then returned to
outlook 2000.

Any ideas anyone?!???
 
L

Lanwench [MVP - Exchange]

Nic said:
A user had been using outlook 2003 to access e-mail on an exchange
2000 server. The user was then moved to an older PC with an older
version of outlook (Outlook 2000). Now outlook 2000 will not close
or shutdown properly. We have tried applying Office 2000 SP3, but
this has made no difference. The "Please wait while Microsoft
Outlook exits" dialog box remains on screen - the only way out is to
log off the PC, or terminate the application within task manager.
This has happened to multiple users who have used outlook 2003 to
access their mailboxes, and then returned to outlook 2000.

Any ideas anyone?!???

Are you using roaming profiles?
What's in the profile? If it's just Exchange only, this shouldn't be a
problem. If you're using PST files, what kind (new 2003 unicode format?
won't open in older versions...) and where are they located? Have you tried
recreating the profiles?
 
N

Nic

No, we're not using roaming profiles, or PSTs. I have come across this
problem before where once a user has opened his/her mailbox on exchange using
a more up to date version of outlook, it makes some kind of change to the
mailbox itself which then causes some problems with older versions when the
user reverts to a PC with an older version of Outlook installed. I am
assuming that there might be some kind of patch for Exchange, or for Outlook
which will cure the problem.

Since writing my initial question this morning, I have discovered that the
users concerned do not have a problem when using Outlook 2002 (XP), but still
get the problem when using Outlook 2000. I have also tried applying SP3 to
the Office 2000 Pro installation on the PCs in question, but this has not
fixed it either.

It may be that performing some kind of "profile recreation" will work, but
at least one user has simply been moved from Outlook 2003 to a fresh
installation of Outlook 2000 - therefore the profile was created and symptoms
occured on a fresh profile in the first instance.

I am further assuming that what is happening is a little like the old Word
version incompatibilities. Basically that the mailbox itself has been
modified in it's structure when Outlook 2003 was used and that therefore the
older Outlook 2000 is having trouble finalising any file close on the mailbox
within the Exchange database.

Any other suggestions?
 
L

Lanwench [MVP - Exchange]

Nic said:
No, we're not using roaming profiles, or PSTs. I have come across
this problem before where once a user has opened his/her mailbox on
exchange using a more up to date version of outlook, it makes some
kind of change to the mailbox itself which then causes some problems
with older versions when the user reverts to a PC with an older
version of Outlook installed. I am assuming that there might be some
kind of patch for Exchange, or for Outlook which will cure the
problem.

I have never seen that, ever.
Since writing my initial question this morning, I have discovered
that the users concerned do not have a problem when using Outlook
2002 (XP), but still get the problem when using Outlook 2000. I have
also tried applying SP3 to the Office 2000 Pro installation on the
PCs in question, but this has not fixed it either.

It may be that performing some kind of "profile recreation" will
work, but at least one user has simply been moved from Outlook 2003
to a fresh installation of Outlook 2000 - therefore the profile was
created and symptoms occured on a fresh profile in the first instance.
Bizarre...

I am further assuming that what is happening is a little like the old
Word version incompatibilities. Basically that the mailbox itself
has been modified in it's structure when Outlook 2003 was used and
that therefore the older Outlook 2000 is having trouble finalising
any file close on the mailbox within the Exchange database.

Again, I think you're barking up the wrong tree here.
Are you using group policies on your domain that might have something to do
with this?
Any other suggestions?

Detect & Repair in OL2000? I don't have OL2000 here (it's old - you ought to
get everyone on OL2003) but I think it's still an option....
 
R

Russ Valentine [MVP-Outlook]

Where I work, if Outlook 2003 has ever touched an Exchange Server mailbox,
any Outlook 2000 profile will hang on exit if it ever accesses that same
mailbox.
No one can fix it. I suspect that's why Microsoft created Task Manager.
I was told it had something to so with this:
http://support.microsoft.com/default.aspx?kbid=829418
But still no one can fix it.
 
L

Lanwench [MVP - Exchange]

Russ said:
Where I work, if Outlook 2003 has ever touched an Exchange Server
mailbox, any Outlook 2000 profile will hang on exit if it ever
accesses that same mailbox.
No one can fix it. I suspect that's why Microsoft created Task
Manager.
I was told it had something to so with this:
http://support.microsoft.com/default.aspx?kbid=829418
But still no one can fix it.

Hmm - well, I don't use Exchange 5.5 anywhere anymore, so that might explain
it.
This look related at all?
http://support.microsoft.com/?id=834466
Have you ever called PSS on this? It's curious!
 
R

Russ Valentine [MVP-Outlook]

I told our IT guys about this hotfix. They weren't interested.
So I just exit Outlook with TM.
 
L

Lanwench [MVP - Exchange]

Russ said:
I told our IT guys about this hotfix. They weren't interested.

That's a shame. Are they interested in the fact that Exchange 5.5 (extended
support) reaches end-of-life this December? :)

So I just exit Outlook with TM.

Whatever works!
 
R

Russ Valentine [MVP-Outlook]

No. I work at a hospital. We aren't afraid of end-of-life. We just consider
it another daily challenge.
--
Russ Valentine
[MVP-Outlook]
"Lanwench [MVP - Exchange]"
Russ said:
I told our IT guys about this hotfix. They weren't interested.

That's a shame. Are they interested in the fact that Exchange 5.5
(extended
support) reaches end-of-life this December? :)

So I just exit Outlook with TM.

Whatever works!
Russ Valentine [MVP-Outlook] wrote:
Where I work, if Outlook 2003 has ever touched an Exchange Server
mailbox, any Outlook 2000 profile will hang on exit if it ever
accesses that same mailbox.
No one can fix it. I suspect that's why Microsoft created Task
Manager.
I was told it had something to so with this:
http://support.microsoft.com/default.aspx?kbid=829418
But still no one can fix it.

Hmm - well, I don't use Exchange 5.5 anywhere anymore, so that might
explain
it.
This look related at all?
http://support.microsoft.com/?id=834466
Have you ever called PSS on this? It's curious!


Nic wrote:
No, we're not using roaming profiles, or PSTs. I have come across
this problem before where once a user has opened his/her mailbox
on exchange using a more up to date version of outlook, it makes
some kind of change to the mailbox itself which then causes some
problems with older versions when the user reverts to a PC with
an older version of Outlook installed. I am assuming that there
might be some kind of patch for Exchange, or for Outlook which
will cure the problem.

I have never seen that, ever.


Since writing my initial question this morning, I have discovered
that the users concerned do not have a problem when using Outlook
2002 (XP), but still get the problem when using Outlook 2000. I
have also tried applying SP3 to the Office 2000 Pro installation
on the PCs in question, but this has not fixed it either.

It may be that performing some kind of "profile recreation" will
work, but at least one user has simply been moved from Outlook
2003 to a fresh installation of Outlook 2000 - therefore the
profile was created and symptoms occured on a fresh profile in
the first instance.

Bizarre...

I am further assuming that what is happening is a little like the
old Word version incompatibilities. Basically that the mailbox
itself has been modified in it's structure when Outlook 2003 was
used and that therefore the older Outlook 2000 is having trouble
finalising any file close on the mailbox within the Exchange
database.

Again, I think you're barking up the wrong tree here.
Are you using group policies on your domain that might have
something to do
with this?

Any other suggestions?

Detect & Repair in OL2000? I don't have OL2000 here (it's old - you
ought to
get everyone on OL2003) but I think it's still an option....

:

Nic wrote:
A user had been using outlook 2003 to access e-mail on an
exchange 2000 server. The user was then moved to an older PC
with an older version of outlook (Outlook 2000). Now outlook
2000 will not close or shutdown properly. We have tried
applying Office 2000 SP3, but this has made no difference. The
"Please wait while Microsoft Outlook exits" dialog box remains
on screen - the only way out is to log off the PC, or terminate
the application within task manager. This has happened to
multiple users who have used outlook 2003 to access their
mailboxes, and then returned to outlook 2000.

Any ideas anyone?!???

Are you using roaming profiles?
What's in the profile? If it's just Exchange only, this shouldn't
be a problem. If you're using PST files, what kind (new 2003
unicode format? won't open in older versions...) and where are
they located? Have you tried recreating the profiles?
 
L

Lanwench [MVP - Exchange]

Russ said:
No. I work at a hospital. We aren't afraid of end-of-life. We just
consider it another daily challenge.

Heh. Well, I suppose we are all racing headlong into the inevitable
shuffling off of the mortal coil. Does put a different perspective on DLL
conflicts and hard drive failures.
Russ said:
I told our IT guys about this hotfix. They weren't interested.

That's a shame. Are they interested in the fact that Exchange 5.5
(extended
support) reaches end-of-life this December? :)

So I just exit Outlook with TM.

Whatever works!
Russ Valentine [MVP-Outlook] wrote:
Where I work, if Outlook 2003 has ever touched an Exchange Server
mailbox, any Outlook 2000 profile will hang on exit if it ever
accesses that same mailbox.
No one can fix it. I suspect that's why Microsoft created Task
Manager.
I was told it had something to so with this:
http://support.microsoft.com/default.aspx?kbid=829418
But still no one can fix it.

Hmm - well, I don't use Exchange 5.5 anywhere anymore, so that
might explain
it.
This look related at all?
http://support.microsoft.com/?id=834466
Have you ever called PSS on this? It's curious!


Nic wrote:
No, we're not using roaming profiles, or PSTs. I have come
across this problem before where once a user has opened his/her
mailbox on exchange using a more up to date version of outlook,
it makes some kind of change to the mailbox itself which then
causes some problems with older versions when the user reverts
to a PC with an older version of Outlook installed. I am
assuming that there might be some kind of patch for Exchange,
or for Outlook which will cure the problem.

I have never seen that, ever.


Since writing my initial question this morning, I have
discovered that the users concerned do not have a problem when
using Outlook 2002 (XP), but still get the problem when using
Outlook 2000. I have also tried applying SP3 to the Office
2000 Pro installation on the PCs in question, but this has not
fixed it either.

It may be that performing some kind of "profile recreation" will
work, but at least one user has simply been moved from Outlook
2003 to a fresh installation of Outlook 2000 - therefore the
profile was created and symptoms occured on a fresh profile in
the first instance.

Bizarre...

I am further assuming that what is happening is a little like
the old Word version incompatibilities. Basically that the
mailbox itself has been modified in it's structure when Outlook
2003 was used and that therefore the older Outlook 2000 is
having trouble finalising any file close on the mailbox within
the Exchange database.

Again, I think you're barking up the wrong tree here.
Are you using group policies on your domain that might have
something to do
with this?

Any other suggestions?

Detect & Repair in OL2000? I don't have OL2000 here (it's old -
you ought to
get everyone on OL2003) but I think it's still an option....

:

Nic wrote:
A user had been using outlook 2003 to access e-mail on an
exchange 2000 server. The user was then moved to an older PC
with an older version of outlook (Outlook 2000). Now outlook
2000 will not close or shutdown properly. We have tried
applying Office 2000 SP3, but this has made no difference.
The "Please wait while Microsoft Outlook exits" dialog box
remains on screen - the only way out is to log off the PC, or
terminate the application within task manager. This has
happened to multiple users who have used outlook 2003 to
access their mailboxes, and then returned to outlook 2000.

Any ideas anyone?!???

Are you using roaming profiles?
What's in the profile? If it's just Exchange only, this
shouldn't be a problem. If you're using PST files, what kind
(new 2003 unicode format? won't open in older versions...) and
where are they located? Have you tried recreating the profiles?
 
N

Nic

Thanks for all your input guys - I have to point out that I am not using
Exchnage 5.5 either - although the last time I came across this problem I
was, this time we're on Exchange 2000.

I'm glad to see someone else has expereinced the problem, but also sorry
that you're suffering too! I know one man who may be able to fix this
problem for me, but he's on holiday.... I'll ask him when he gets back!


Russ Valentine said:
Well put.
--
Russ Valentine
[MVP-Outlook]
"Lanwench [MVP - Exchange]"
Heh. Well, I suppose we are all racing headlong into the inevitable
shuffling off of the mortal coil. Does put a different perspective on DLL
conflicts and hard drive failures.
 
G

gcopeland

www.adminnotes.com/hotfix/2004/04/outlook_2000_ha.html This will take
you where you need to go, if you havent allready fixed the problem that
is.
Nic said:
Thanks for all your input guys - I have to point out that I am not using
Exchnage 5.5 either - although the last time I came across this problem I
was, this time we're on Exchange 2000.

I'm glad to see someone else has expereinced the problem, but also sorry
that you're suffering too! I know one man who may be able to fix this
problem for me, but he's on holiday.... I'll ask him when he gets back!


Russ Valentine said:
Well put.
--
Russ Valentine
[MVP-Outlook]
"Lanwench [MVP - Exchange]"
Russ Valentine [MVP-Outlook] wrote:
No. I work at a hospital. We aren't afraid of end-of-life. We just
consider it another daily challenge.

Heh. Well, I suppose we are all racing headlong into the inevitable
shuffling off of the mortal coil. Does put a different perspective on DLL
conflicts and hard drive failures.
 
Top