Outlook Disconnected

Hi there, I have just returned to work this morning after the festive season to find that all systems are go here.  Everything is up and running as normal, except that everyone's Outlook is displaying "disconnected" in the lower right corner.

On the server everything looks fine at first glance, and from the workstations they are able to ping the server name, ping the server IP and also ping the mail domain.

I have tried googling the issue and I can only find "maybe a virus scanner is interfering".  That is not the issue here as the workstations are not running any.

This seems like it should be a fairly simple issue given that everything seems to be running fine, I just don't know where to start.

Thanks guys!
Angry_StuAsked:
Who is Participating?
 
Alan HardistyCo-OwnerCommented:
Can you change the logon account for the Microsoft Exchange Transport Service to use the local system account, then try to restart it, then try to start th Information store.
I think you might be up and running again after this.
0
 
ICaldwellCommented:
Did you click on "Disconnected" on the lower right and make sure work offline is not checked?
0
 
Angry_StuAuthor Commented:
I had a look at that and work offline is not checked on any of them.

I just had a look at event viewer on the server and there are some exchange events on there.

See image.
ExchgError.jpg
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
giltjrCommented:
On the Exchange server do a netstat -an and make sure Exchange is listening on the appropriate ports, 143  or 993 are normally used with outlook.

Could a firewall had been enabled on the server?

You can always get something like wireshark (http://www.wireshark.org) install it on a client and do a packet capture and see if the Exchange server is responding.  If it is NOT responding, then you may want to install Wireshark or MS NetMon on the sever and do a packet capture there.
0
 
ICaldwellCommented:
You can view your outlook RPC calls by clicking Start, Run, and type Outlook /rpcdiag

You will receive an extra box with tells you about the connections to the exchange server..
0
 
Alan HardistyCo-OwnerCommented:
Check all your Exchange Services have started (Start, Run, Services.msc)
If they are all started (at least the ones that are automatic), then check that the store is mounted.  This is the other reason why all your outlook clients won't be connected.
Store dismounts can be caused by having too much data in the store and if you have reached a limit, you can adjust the limit up to 75Gb by tweaking the registry and preventing daily store dismounts:
http://www.petri.co.il/change_store_size_limits_ex2003_sp2.htm
If you have hit the current limit, then right-click on the store and choose mount.  This should mount the store and get you up and running.  If it is down again tomorrow, then you are being dismounted because of the size of the store.
Make sure you have Exchange 2003 Service Pack 2 installed and then adjut the registry settings to a larger size than currently set (about 18gb by default) and don't just type in 75 as this won't give you any room to play.
0
 
Angry_StuAuthor Commented:
giltjr:    Thanks for your response.   I tried a netstat -an and it literally takes 6 seconds or so to finish the list, there are that many.    It exceeds the text limit of the command prompt window so I cannot see if those ports are open.

itkamaraj:   Thanks for the links.  The issue is not the first link (corrupted profile) because it is organisation-wide, and there are those events in event viewer indicating it must be a server-side issue.   The second link solution related to a wireless network issue.   We are not using wireless and as I say, they are able to ping the server just fine.

ICaldwell:   Cheers, I have run the command as you said and there are no connections in the window that opens.   When I click the 'reconnect' button, nothing at all happens and still no connections appear.  That feels to me, since they can communicate with the server itself (it is also the file server and they can access all their network files) that it could be an issue with an exchange service?
0
 
Alan HardistyCo-OwnerCommented:
Angry_Stu - have you seen my comment?
0
 
Angry_StuAuthor Commented:
alanhardisty:   Thanks mate.    Under services, not all are running.   See image below.   Also, when I try to start the information store service I get an error, also below.

I have also screenied the storage group status, since it says "Unknown".   When I right-click on the store I can click "properties" and "help".   I can't see anywhere to mount these things, but that's probably because I have exchange server 2007 (my bad, I should have metioned this intially).
ExchgServices.jpg
ExchgFail.jpg
ExchgStorage.jpg
0
 
Alan HardistyCo-OwnerCommented:
Okay - now we are getting somewhere.  We also know you have Exchange 2007.
What events do you have in the Application Event Log?
The MIcrosoft Exchange Transport Service would seem to be the problem.  Anything in the App log about why this won't start?
If not, please try to start it and check the logs afterwards.
0
 
Alan HardistyCo-OwnerCommented:
Have you installed all the latest Rollups for Exchange 2007 and/or Exchange 2007 Service Pack 2?
0
 
ICaldwellCommented:
Just out of curiosity.. have you attempted to reboot the server?
0
 
Angry_StuAuthor Commented:
In the Application Event log, I have just refreshed it and it is still coughing out that error I posted up initially.   I will add this again below for convenience.    When I tried to start the transport service it gave me the exact same error as when I tried to start the information store service.

Event viewer after trying to start these services just displays that exact same error again.   See below.
ExchgError.jpg
ExchgFail.jpg
0
 
giltjrCommented:
You can issue the following then:

netstat -an | findstr /c:"143" | findstr /c:"LISTEN"

then:

netstat -an | findstr /c:"993" | findstr /c:"LISTEN"

First command will filter out only lines with the number 143 and the word LISTEN (in upper case) in them, the second will use the number 993.
0
 
Angry_StuAuthor Commented:
Just for clarity, that second image still says "imformation store service" because I reused the image, When I try and start the transport service the error is identical but says "transport service".

I can go and get a screenie of it if you need, just letting you know I did actually try and start the correct service :)
0
 
Alan HardistyCo-OwnerCommented:
Please just change the logon account for the Microsoft Exchange Transport Service as per my last post and try to start the service.  Then try the Store and see what gives.
0
 
Angry_StuAuthor Commented:
Brilliant!
0
 
Angry_StuAuthor Commented:
alanhardisty, you are a modern genius :)

Thank you so much, you have saved me from a public lynching!

giltjr:  Thanks for that info, that will definately come in handy later.   I didn't know that you could filters in the netstat command, I have written that stuff down :)
0
 
Alan HardistyCo-OwnerCommented:
Thanks ;-)
Glad you are sorted and we managed to save your bacon.  It is always a good way to start the New Year by having your server go wrong and you haven't touched it!  Let's hope 2010 does not continue this way for you.
Alan
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.