SLOW to open Outlook

[MiniComus]

Client: Outlook 2002, sp2 which is running on XP-Pro
Server: Exchange 2000, sp3 which is running on 2000 Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for logging onto
network, but when user tries to open Outlook, it takes 10-
30 minutes to open the application and her PC is locked-up
until Outlook finally opens. It seems to be faster if she
logs-on before/after the rush of incoming employees at
open of business.

Client is responsible for scheduling for CEO as well as
scheduling for 2 conference rooms. Client uses Outlook to
open mailboxes for each of above PLUS her own mailbox, so
client has 4 different mailboxes open in same instance of
Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in general
or Outlook/Exhange specifically. Exchange shows that her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook (again -
we're talking about 10-30 minutes), and what can I do to
decrease this delay?

 

[Ben M. Schorr, MVP-OneNote]

Might be a name resolution issue. Can you ping the Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

 

[MiniComus]

Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was able to
resolve the name. The ping came back just fine.

Any other ideas?

-----Original Message-----
Might be a name resolution issue. Can you ping the Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Client: Outlook 2002, sp2 which is running on XP-Pro
Server: Exchange 2000, sp3 which is running on 2000 Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for logging onto
network, but when user tries to open Outlook, it takes 10-
30 minutes to open the application and her PC is locked- up
until Outlook finally opens. It seems to be faster if she
logs-on before/after the rush of incoming employees at
open of business.

Client is responsible for scheduling for CEO as well as
scheduling for 2 conference rooms. Client uses Outlook to
open mailboxes for each of above PLUS her own mailbox, so
client has 4 different mailboxes open in same instance of
Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in general
or Outlook/Exhange specifically. Exchange shows that her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook (again -
we're talking about 10-30 minutes), and what can I do to
decrease this delay?

.

 

[Ben M. Schorr, MVP-OneNote]

Well...if it passed that simple test then it gets into more complicated
things. You may want to start here:
http://www.labmice.net/BackOffice/Exchange2000/performance.htm

Be forewarned this may be a long project.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was able to
resolve the name. The ping came back just fine.

Any other ideas?

-----Original Message-----
Might be a name resolution issue. Can you ping the Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Client: Outlook 2002, sp2 which is running on XP-Pro
Server: Exchange 2000, sp3 which is running on 2000 Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for logging onto
network, but when user tries to open Outlook, it takes 10-
30 minutes to open the application and her PC is locked- up
until Outlook finally opens. It seems to be faster if she
logs-on before/after the rush of incoming employees at
open of business.

Client is responsible for scheduling for CEO as well as
scheduling for 2 conference rooms. Client uses Outlook to
open mailboxes for each of above PLUS her own mailbox, so
client has 4 different mailboxes open in same instance of
Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in general
or Outlook/Exhange specifically. Exchange shows that her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook (again -
we're talking about 10-30 minutes), and what can I do to
decrease this delay?

.

 

[MiniComus]

Simple test, yes, but still a great idea. Thanks for that.

So you would tend to search for a solution first on
the "Exchange" (server) side of the problem, as opposed to
looking for the solution from the "Outlook" (client) side?

Also - this project has already been a long one!

-----Original Message-----
Well...if it passed that simple test then it gets into more complicated
things. You may want to start here:
http://www.labmice.net/BackOffice/Exchange2000/performance ..htm

Be forewarned this may be a long project.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was able to
resolve the name. The ping came back just fine.

Any other ideas?

-----Original Message-----
Might be a name resolution issue. Can you ping the Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the

newsgroup.
Mahalo!

Client: Outlook 2002, sp2 which is running on XP-Pro
Server: Exchange 2000, sp3 which is running on 2000 Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for logging onto
network, but when user tries to open Outlook, it

takes
10-

30 minutes to open the application and her PC is

locked-
up

until Outlook finally opens. It seems to be faster

if
she

logs-on before/after the rush of incoming employees at
open of business.

Client is responsible for scheduling for CEO as well as
scheduling for 2 conference rooms. Client uses

Outlook
to

open mailboxes for each of above PLUS her own

mailbox,
so

client has 4 different mailboxes open in same

instance
of

Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in general
or Outlook/Exhange specifically. Exchange shows that her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook (again -
we're talking about 10-30 minutes), and what can I

do
to

decrease this delay?


.

.

 

[Ben M. Schorr, MVP-OneNote]

Well...do you have the same problem with other client machines? Guess I
should ask that first.

You might also take a look at your RPC binding order.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;163576

--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Simple test, yes, but still a great idea. Thanks for that.

So you would tend to search for a solution first on
the "Exchange" (server) side of the problem, as opposed to
looking for the solution from the "Outlook" (client) side?

Also - this project has already been a long one!

-----Original Message-----
Well...if it passed that simple test then it gets into more complicated
things. You may want to start here:
http://www.labmice.net/BackOffice/Exchange2000/performance .htm

Be forewarned this may be a long project.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was able to
resolve the name. The ping came back just fine.

Any other ideas?


-----Original Message-----
Might be a name resolution issue. Can you ping the
Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct
requests for assistance.
Please post questions and replies here in the newsgroup.
Mahalo!


Client: Outlook 2002, sp2 which is running on XP-Pro
Server: Exchange 2000, sp3 which is running on 2000
Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for logging onto
network, but when user tries to open Outlook, it takes
10-
30 minutes to open the application and her PC is locked-
up
until Outlook finally opens. It seems to be faster if
she
logs-on before/after the rush of incoming employees at
open of business.

Client is responsible for scheduling for CEO as well as
scheduling for 2 conference rooms. Client uses Outlook
to
open mailboxes for each of above PLUS her own mailbox,
so
client has 4 different mailboxes open in same instance
of
Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in
general
or Outlook/Exhange specifically. Exchange shows that
her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook
(again -
we're talking about 10-30 minutes), and what can I do
to
decrease this delay?


.

.

 

[MiniComus]

There have been some sporadic complaints about it taking a
little while to open Outlook, but with others it never
seems even remotely consistent. With this particular
user, it is just about all the time that she has
problems. I also am pretty sure that I'd have heard a lot
more complaints from ANYONE who had a 10-minute Outlook
sign-on, so I think it's mainly just this one user.

Note that this particular user is the only user in our
network who accesses multiple mailboxes. To me this means
that it could be a problem across the whole network and
across all users, but it manifests itself much more
obviously on her Outlook because the problem is multiplied.

Other than the multiple mailboxes, though, her PC should
be nearly identical to everyone else's. Maybe I should
try setting up my own Outlook client to hit those other
mailboxes and see if my computer bogs down. That's about
all I can think of on this one...

And thanks again!

I will have a look at the article you most recently
forwarded tomorrow. I gotta run for the day today!

-----Original Message-----
Well...do you have the same problem with other client machines? Guess I
should ask that first.

You might also take a look at your RPC binding order.
http://support.microsoft.com/default.aspx?scid=kb;EN- US;163576

--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Simple test, yes, but still a great idea. Thanks for that.

So you would tend to search for a solution first on
the "Exchange" (server) side of the problem, as opposed to
looking for the solution from the "Outlook" (client) side?

Also - this project has already been a long one!

-----Original Message-----
Well...if it passed that simple test then it gets into more complicated
things. You may want to start here:

http://www.labmice.net/BackOffice/Exchange2000/performance

.htm

Be forewarned this may be a long project.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the

newsgroup.
Mahalo!

Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was

able
to

resolve the name. The ping came back just fine.

Any other ideas?


-----Original Message-----
Might be a name resolution issue. Can you ping the
Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct
requests for assistance.
Please post questions and replies here in the newsgroup.
Mahalo!


Client: Outlook 2002, sp2 which is running on XP- Pro
Server: Exchange 2000, sp3 which is running on 2000
Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for

logging
onto

network, but when user tries to open Outlook, it takes
10-
30 minutes to open the application and her PC is locked-
up
until Outlook finally opens. It seems to be

faster
if

she
logs-on before/after the rush of incoming

employees
at

open of business.

Client is responsible for scheduling for CEO as

well
as

scheduling for 2 conference rooms. Client uses Outlook
to
open mailboxes for each of above PLUS her own mailbox,
so
client has 4 different mailboxes open in same instance
of
Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in
general
or Outlook/Exhange specifically. Exchange shows that
her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook
(again -
we're talking about 10-30 minutes), and what can

I
do

to
decrease this delay?


.



.

.

 

[Ben M. Schorr, MVP-OneNote]

If the problem mostly occurs in the mornings (when all the users are logging
in simultaneously) then you may well have a server-side performance issue in
that the server is having trouble processing all the requests in a timely
manner.

Could also be a network performance issue.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

There have been some sporadic complaints about it taking a
little while to open Outlook, but with others it never
seems even remotely consistent. With this particular
user, it is just about all the time that she has
problems. I also am pretty sure that I'd have heard a lot
more complaints from ANYONE who had a 10-minute Outlook
sign-on, so I think it's mainly just this one user.

Note that this particular user is the only user in our
network who accesses multiple mailboxes. To me this means
that it could be a problem across the whole network and
across all users, but it manifests itself much more
obviously on her Outlook because the problem is multiplied.

Other than the multiple mailboxes, though, her PC should
be nearly identical to everyone else's. Maybe I should
try setting up my own Outlook client to hit those other
mailboxes and see if my computer bogs down. That's about
all I can think of on this one...

And thanks again!

I will have a look at the article you most recently
forwarded tomorrow. I gotta run for the day today!

-----Original Message-----
Well...do you have the same problem with other client machines? Guess I
should ask that first.

You might also take a look at your RPC binding order.
http://support.microsoft.com/default.aspx?scid=kb;EN- US;163576

--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

Simple test, yes, but still a great idea. Thanks for that.

So you would tend to search for a solution first on
the "Exchange" (server) side of the problem, as opposed to
looking for the solution from the "Outlook" (client) side?

Also - this project has already been a long one!




-----Original Message-----
Well...if it passed that simple test then it gets into
more complicated
things. You may want to start here:
http://www.labmice.net/BackOffice/Exchange2000/performance
.htm

Be forewarned this may be a long project.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct
requests for assistance.
Please post questions and replies here in the newsgroup.
Mahalo!


in message
Ben,
Thanks for the quick reply. I tried pinging our
exchange
server using the computer name and the client was able
to
resolve the name. The ping came back just fine.

Any other ideas?


-----Original Message-----
Might be a name resolution issue. Can you ping the
Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct
requests for assistance.
Please post questions and replies here in the
newsgroup.
Mahalo!


Client: Outlook 2002, sp2 which is running on XP- Pro
Server: Exchange 2000, sp3 which is running on 2000
Server

Client machine takes VERY long time to bring-up
Outlook
after initial boot-up. Boot-up is fine for logging
onto
network, but when user tries to open Outlook, it
takes
10-
30 minutes to open the application and her PC is
locked-
up
until Outlook finally opens. It seems to be faster
if
she
logs-on before/after the rush of incoming employees
at
open of business.

Client is responsible for scheduling for CEO as well
as
scheduling for 2 conference rooms. Client uses
Outlook
to
open mailboxes for each of above PLUS her own
mailbox,
so
client has 4 different mailboxes open in same
instance
of
Outlook. Other than the 4 different mailboxes
Outlook
opens whenever it gets around to coming-up, there
isn't
anything different about her config for the PC in
general
or Outlook/Exhange specifically. Exchange shows that
her
mailbox has quite a few "items", but no more than
mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook
(again -
we're talking about 10-30 minutes), and what can I
do
to
decrease this delay?


.



.

.

 

[ham]

rename your .pst file and remove the mailbox form outlook,
restart outlook. Repeat the process for all four
mailboxes, this should tell you which .pst file is
possibly corrupted.

-----Original Message-----
Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was able to
resolve the name. The ping came back just fine.

Any other ideas?

-----Original Message-----
Might be a name resolution issue. Can you ping the Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the

newsgroup.

Mahalo!

locked-

up

Outlook

to


.

.

 

[Ben M. Schorr, MVP-OneNote]

Not a bad idea, but she's an Exchange user and I don't think she's using
..PSTs for her data store.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

rename your .pst file and remove the mailbox form outlook,
restart outlook. Repeat the process for all four
mailboxes, this should tell you which .pst file is
possibly corrupted.

-----Original Message-----
Ben,
Thanks for the quick reply. I tried pinging our exchange
server using the computer name and the client was able to
resolve the name. The ping came back just fine.

Any other ideas?

-----Original Message-----
Might be a name resolution issue. Can you ping the Exchange server, by
name, from the affected client?

Go to a command prompt (C:\) and type

PING [exchangeserver]

Where [exchangeserver] is the name of your server.


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the

newsgroup.

Mahalo!


Client: Outlook 2002, sp2 which is running on XP-Pro
Server: Exchange 2000, sp3 which is running on 2000 Server

Client machine takes VERY long time to bring-up Outlook
after initial boot-up. Boot-up is fine for logging onto
network, but when user tries to open Outlook, it takes 10-
30 minutes to open the application and her PC is

locked-

up
until Outlook finally opens. It seems to be faster if she
logs-on before/after the rush of incoming employees at
open of business.

Client is responsible for scheduling for CEO as well as
scheduling for 2 conference rooms. Client uses

Outlook

to
open mailboxes for each of above PLUS her own mailbox, so
client has 4 different mailboxes open in same instance of
Outlook. Other than the 4 different mailboxes Outlook
opens whenever it gets around to coming-up, there isn't
anything different about her config for the PC in general
or Outlook/Exhange specifically. Exchange shows that her
mailbox has quite a few "items", but no more than mine,
which opens without much delay at all.

What is causing this HUGE delay in opening Outlook (again -
we're talking about 10-30 minutes), and what can I do to
decrease this delay?


.

.