• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 217
  • Last Modified:

2003 Exchange Down after Acronis Disk management attempt

Our 2003 Exchange server is  Down after Acronis Disk management attempt
Here is our layout
C: (OS)
E: (Exchange installed + data files)

I installed Acronis Disk Manager to free up some space on C:\ and reduced the disk space on E: to allow some room

Normally this isnt an issue, but after the reboot Acronis started the process and then errored out. i start up the OS and my E: drive is gone! Under disk management I was able to find it and assign the drive letter E back to it, all the MS exchange services are stopped when I try to start them I get...

could not start...>XXXXXXXX.. on the local computer ..

any ideas, I've restore from a back up already.. exchange was working when i assigned the drive letter back but I tried the disk manager again thinking it was a faul and now I got the same results and exchange is out

Ideas?
0
ravenrx7
Asked:
ravenrx7
  • 6
  • 2
1 Solution
 
ravenrx7Author Commented:
I did notice under the services for MS exchange and etc, the location of that service was located on D:\ which isnt correct, Acronis has really screwed on this one. I know the drive for my data and exchange was E:
0
 
ravenrx7Author Commented:
I changed the drive letter to D: and I was able to start the services but exchange still isnt working
0
 
ravenrx7Author Commented:
I was able to get the server up and running, Im sending and receiving email but one on mobile devices and on OWA, if I go to a client like outlook 2010, it says connected but the emails are not sync'ed ..

Ideas?
0
 
Alan HardistyCommented:
Time to resort to your last full backup before you installed Acronis, which I would hope you took before doing something potentially lethal like messing with the disk partitions.
0
 
ravenrx7Author Commented:
what no..Ive got everything up and working.. my issue now is we are receiving mail via OWA and mobile devices, but not via outlook clients, well some work, some dont. I read up and it they we talking about the clients running in cache mode
0
 
Alan HardistyCommented:
Okay - if all is okay then you will need to export Outlook to .PST files (in case you have something in Outlook not in Exchange), then close outlook, delete the .OST file locally, re-open Outlook and it should re-populate the .OST file (suck down the info from the server).
0
 
ravenrx7Author Commented:
Ok that makes sense but for 100+ clients?
0
 
ravenrx7Author Commented:
deleting the .ost file did work thank you.. is there a way to automate this i wonder
0
 
lucid8Commented:
I am not sure you would want to automate the deletion of OST files since you would need to ensure the Exchange clients were not operational and then there is the oops I didn't mean to do that factor.  

That said if you really wanted to you could do something as simple as a batch file that would delete the OST files on each machine, you just need to map the location of each machines OST

But again I wouldn't do this since the OST can be your friend, i.e. as Alan pointed out in a failure like this you can have users connect to Outlook in Offline mode to access the OST contents and then export to PST as a fallback method for any missing items for each user
0
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now