Exchange Server 2003 cannot mount store.Events 9175 and 9518 logged


I have a sbs 2003 server running exchange 2003.
Yesterday the server crashed and i had to restore it to a different hardware from an acronis image.
The acronis image was 2 days old.I managed to successfully restore the image to the new server maintaining the same partition names (c: and e: for the data).I put the drivers of the network card and gave the same ip address as before.All is working correctly except exchange 2003 which refuses to mount the store giving errors 9175 and 9518.I tried restoring the previous day backup from ntbackup selecting the option that “this is the last backup” with no success.
Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      MAPI Session
Event ID:      9175
Date:            27/9/2011
Time:            8:51:13 pµ
User:            N/A
Computer:      SERVER01
The MAPI call ‘OpenMsgStore’ failed with the following error:
The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

For more information, click

Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      9518
Date:            27/9/2011
Time:            8:50:43 pµ
User:            N/A
Computer:      SERVER01
Error 0xfffffb40 starting Storage Group /DC=local/DC=venetos/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=VENETOS/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=SERVER01/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group – Initialization of Jet failed.

For more information, click


I tried moving the log files from the “C:\Program Files\Exchsrvr\MDBDATA”  to another location and restarted the “Information Store Service” and voila it managed to successfully mount the database! Recovery procedure with eseutil was not needed.

Turn on numlock at Windows 7 startup

Recently i had an annoying problem with a computer.Despite the fact that i had turned on the option on bios to enable numlock at startup, numlock was not enabled for some reason.After a little searching i found that in Windows 7 i have to change an option located in registry.Remember to backup your registry before making any change!

InitialKeyboardIndicators” String needs a value of “2

So open “regedit” and search for “InitialKeyboardIndicators” and on each string change the value to “2“.

How to automatically terminate hung program in Windows 7 / Vista / XP

Often programs on windows can hung , not responding and even using task manager you cannot close them.Here is a small trick which you can use to Auto Kill the programs which it gets hung or goes into status of “Not Responding”.

Steps to set auto kill not responding programs

  • Backup your registry first.
  • Go to Run and enter “Regedit“.
  • Browse to HKEY_CURRENT_USER\Control Panel\Desktop

Windows 7  / Windows Vista

  • In Windows 7 we will need to add the following values :
  • WaitToKillAppTimeout=2000
  • AutoEndTasks=1
  • HungAppTimeout=1000
  • LowLevelHooksTimeout =1000

To add a value follow the steps below :

  • Right click on the left panel as seen in the image
  • Select New > String value.
  • String name should be one of the above.
  • Now double click and add the value and click ok. Repeat this for all.

High, System Interrupts, cpu usage on Windows XP

Sometimes you may face very slow response from your computer although it has a good amount of memory,cpu etc.Running Sysinternals Process Explorer for further investigation, we can see that System Hardware Interrupts consume a large amount of cpu.This can lead to a very slow response of your computer and may also trick you thinking that you may a have a virus.

The reason that this can occur is that windows try to access hard drive using PIO mode instead of DMA mode.To fix this download the following vbscript run it on your computer and then restart the system.

Download vbscript