Jump to content

Recommended Posts

Posted

Hello All,

 

Due to a staff restructure at our place we are down two member of staff, as a result I have inherited a decrepid exchange 2000 server to look after.

 

Before I write the rest of this message I will explain that I have no previous experience of MS Exchange and am making things up as I go along.

 

Yesterday afternoon outlook 2003 dropped connections to exchange and upon restarting could not connect. I found this problem to be insufficient space on the drive storing the Information Store and databases, the drive is a 10GB drive so hardly surprising :D. As a workaround I put an IDE drive into the server and used System manager to move the locations of the information store and databases. All seemed well at around 7:30pm last night, exchange was even running noticably faster.

 

However when I arrived to work this morning, the server had clearly rebooted and the mouse pointer had frozen :eek:. Restarting the server has brought it back online for now.

 

I know its a real crystal ball question, but does anyone have any idea what may have caused this or be able to give me some pointers on how I can run some diagnostics to try and find the problem.

 

There didnt seem to be any relevent entries in any of the event logs before the crash (around 1:45am)

 

Thanks for reading (if you did)

 

Mathew

Posted

Whats its setup for auto updates....its set to download only right...?

 

I'd stress the instability, lack of modern security and lack of support to the SMT as cause for an upgrade....

Posted
Whats its setup for auto updates....its set to download only right...?

 

I'd stress the instability, lack of modern security and lack of support to the SMT as cause for an upgrade....

 

Auto upgrades is just set to notify at the moment.

 

In reply to your comment regarding SMT well what can I say, my wardrobe is full of those t-shirts.

Posted

hmm, okay - nothing at all in the logs - could just be a freak out, they can happen.

 

if you have a window when you can take the server down, could try running memtest86, etc

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...