0

Our server crashed a few days ago, cause was a HDD failure. The server seems to be almost fully functional (except that the Exchange DB is corrupt now, but that's another story)

The main problem now is that Windows system applications like cmd.exe, sfc.exe etc. won't run because of error "The application failed to initialize properly (0xC0000142)"(STATUS_DLL_INIT_FAILED).

We have not found a way to fix this error. We've been reading every single post about this error code on google but we found no solution yet. Maybe an expert around that could give some tips and hints?

The most unfortunate thing is that the backup system failed silently 1 month ago. The last bare metal backup is 1 month old, and so is the Exchange db and everything else.

Now I have this semi working server in front of me and I don't know how to fix this mess.

My plan now is to install a fresh Windows Server on a new pair of HDDs, manually reconstruct active directory user and then try to somehow restore the Exchange DB and make it match, but after some researching this seems to be almost impossile. A cross forrest migration is not possible because the crashed server refuses to run anything that requires the command line, so I can't run all the commands and scripts required in a cross forrest migration.

I believe I'm screwed, right? We have 15 users and the Exchange 2010 DB is 16GB big, by the way.

Any help would be really appreciated.

Improve this question
2
  • Try installing a service pack on your barely functioning server. This should replace critical binaries that are either corrupt or missing. If this helps with basic functionality, you can start taking things one step at a time.
    – Jeremy Lyons
    Apr 10, 2013 at 17:53
  • I’m voting to close this question because this is an old question and it's not applicable anymore. The original system either has been fixed or got scratched and reinstalled. This 8-years-old question should not have been bumped to the home page.
    – Massimo
    Sep 12, 2021 at 1:51

1 Answer 1

Reset to default
0

It sounds to be like the system files are corrupt due to previous HD failure. Reinstall the OS by running the "repair" command from booting for windows server 2008 R2 disk. This will reinstall the OS files while leaving your data in place.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .