Posts: 4
Joined: 27.Jul.2005
From: Hard at work
Status: offline
Task 'Microsoft Exchange Server' reported error (0x8004011d): 'The server is not available. Contact your administrator is this condition persists.
thats what I get after I set up a new machine for a user. I have all the updates from microsoft. Followed their suggestions here : http://support.microsoft.com/default.aspx?kbid=327291 Was curious if anyone here had an Idea on what would cause this and how to resolve it, thank you!
Posts: 4
Joined: 27.Jul.2005
From: Hard at work
Status: offline
Yes, everything is correct for the domain here. I even tried directing Outlook to the ip instead of the server name. it is strange, since this is only one machine, and on all logins on the machine, it does it.
Posts: 4
Joined: 27.Jul.2005
From: Hard at work
Status: offline
Hmm, this is the first time, All data is server stored. Oddly enough, i set up another PC for this user, and all worked fine, first round. I dont know, thinking about just starting over again.
Posts: 4
Joined: 27.Jul.2005
From: Hard at work
Status: offline
Oddly, I didnt see anything, myself, or the other IT. Its a HP dc7100 small form, we stuffed a 3com NIC in it, it ran better, but didnt fix it. These built in broadcom's seem to suck. Either that, or our network sucks that bad
Posts: 26
Joined: 28.Jul.2005
From: South Africa
Status: offline
hmmm, yeah if u can browse other resources ie...Internet etc......then im not convinced that it is a harware issue.....
DO a bit more in depth testing and see what comes of it. Trace the process, maybe put a sniffer on the network and see hwta trafiic that PC generates when trying to make a connection to the Exchange..
FIXED! I fixed this (or a very similar) problem, this is how I did it:
Problem: Error (0x8004011D) Server Not Available when trying to Send and Receive in Outlook (Exchange Account on Local Server).
I tried creating a new profile or OST file as suggested in some posts, but this did not work (I didn’t think it would as the problem was occurring on all PC's on the network).
Solution: The solution was to restart the Microsoft Exchange Services on the server. Find the first such service that is set to start automatically and is started, then re-start it. You should be warned that this will restart a bunch of other services too, which is what you want. You may want to restart all the Microsoft Exchange Services just to be sure. Wholah, problem fixed!
Some more info: To restart a service, find it first. Do this by right-clicking on (My) Computer in the Start Menu and click on Manage. Then click on Services and Applications, then Services. Now find the Service, right click on it and click on Restart.
it's a general problem with outlook express, when we send mail to some one it generate an error. few days before i have faced such problem. i used a software to remove such issue in outlook. i found such software at:: www.edbrepairtool.com
I was getting this error and also getting error 0x80040115..
I use Microsoft Office 365 (MS's online Exchange server) so no way for me to 'restart' the server.
I found this article on Microsoft's website and followed the instructions. In the end, this fixed all my problems.
A little background on my problem: I was getting the two errors (the one this thread is on and the other I mentioned above.) Also, Outlook would not open as it said something was wrong with the .pst folder.
The only way to get Outlook to work was to go to the properties and set it to compatibility mode for Win 7. That was annoying because each time I opened Outlook I got the UAC (or whatever it's called) window and had to click the 'Yes' button to let it open.
Once I followed the steps to repair the .pst file (had a tough time finding it! Found it by going to Outlook, then clicking Tools>Account Settings>Data Files>Add..>(.pst) then write down the address where the files are located), it would connect to MS Exchange (Office 365) no problems. It sent all the messages no problems. (the SCANPST tool said it found minor issues with my file and that repairing was optional.. I opted to repair after making a backup, per on-screen suggestions.)
I also went back and switched off the compatibility mode and now it all works just like it used to!
I post all this info in hopes of saving someone else the headache I went through. I am not in IT in any way, shape or form, nor do I have any desire to be.
Hi, this problem occurs when EDB database gets corrupted.
i too had the same problem then i followed following steps (manual): first check all these option : Start MS ExchangeES, Start MSExchangeMTA, Start MSExchangeSA, Start MSExchangeIS
then go to >> Exchange Manager >> Servers >> (Server Name) -> Storage Group -> Right-click on Mailbox Store and select “Mount Store” if dismounted.
then C:\Program Files\Exchsrvr>bin\eseutil / mh mdbdata\priv1.edb
This manual procedure for Exchange EDB recovery is sometimes good but does not assures 100% recovery so it is better not to use it and go for better alternative as mentioned. As ESEUTIL deletes the bad pages instead of recovering it.
ESEUTIL /P is then followed by ISINTEG that works at application level and perform integrity check with the database repaired by ESEUTIL