Exchange 2007 only works after reboot
We are running SBS 2008 with Exchange 2007. Everything was working fine and then all of a sudden we stopped getting mail. I did a reboot on the server and it started to work. Then about 4 hours later it stopped. Did another reboot and it started working. This has been going on for the past few days where I have to reboot the server a few times a day to get the mail to flow.
I checked the event logs and there are no errors relating to Exchange.
Another thing that I might add is that there is only 3.5GB free on the c drive. All the mail and other data is stored on d with plenty of free space. Don't know if this has anything to do with it, but thought I should mention it.
I checked the event logs and there are no errors relating to Exchange.
Another thing that I might add is that there is only 3.5GB free on the c drive. All the mail and other data is stored on d with plenty of free space. Don't know if this has anything to do with it, but thought I should mention it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Also, is there anyway to "move" space from D without having to repartition?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So I ran the windirstat and found that the sql server database transaction log and the wsus folders have about 40GB total between the two of them. Is it safe the delete the sql log files. I am pretty sure that it is, but just want to confirm.
ASKER
Running the server clean up in the WSUS console now.
The WSUS tool will help with that Side of things.
As far as SQL goes, the SBS support team has a blog post that should help:
http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx
While you aren't yet suffering the symptoms, the underlying result is still the same. It cleans up the database pretty well.
Also, make sure your backups are working properly and uses VSS agents that let the applications know when it is safe to prune logs. The built in back up does, as do many 3rd party...but not all. That can be a big gotcha.
As far as SQL goes, the SBS support team has a blog post that should help:
http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx
While you aren't yet suffering the symptoms, the underlying result is still the same. It cleans up the database pretty well.
Also, make sure your backups are working properly and uses VSS agents that let the applications know when it is safe to prune logs. The built in back up does, as do many 3rd party...but not all. That can be a big gotcha.
Have a read of my blog post for the right way to shrink the SQL database (which isn't deleting it) and modifying the settings so that it doesn't grow to a monstrous size again.
Needs a bit of tweaking, but ultimately achievable.
Needs a bit of tweaking, but ultimately achievable.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@suzanne2003 - Can you please explain why Simon's comment is the only comment to be awarded points on this question as there are many other good comments worthy of point allocation, not just Simon's comment.
I would suggest a split between the following comments would be more appropriate:
http:#a38403891
http:#a38403892
http:#a38403941
http:#a38405268
Alan
http:#a38403891
http:#a38403892
http:#a38403941
http:#a38405268
Alan
ASKER