Exchange Server 2010 SP1 Rollup 1 Hell

After running the automated update to Exchange 2010 SP1 Rollup 1, our exchange server stopped being able to mount the data store for the data databases.

The error we received looked like this:

Event 9512 MSExchange IS While starting database Mailbox Database 123456789, the following error occurred: Non-database file or corrupted database. 
Failed to configure MDB.

The Event ID was followed by 3154 then 209 then 2131.

Kind of bummed me out that yet again, an automated update would kill the Exchange server. But I this is something I am getting more and more used to with Microsoft and their updates.

To fix this issue we tried to follow the article here:

As this was suggested in some forums we found about the issue.

Method 1 was what we selected.

Method 1: Run Setup /PrepareAD

Run the Setup /PrepareAD command from the Exchange Server CD to prepare the Active Directory directory service for Exchange Server 2010 or Exchange Server 2007. This command restores the Exchange Servere configuration in Active Directory. For more information about how to prepare Active Directory, see the "How to Prepare Active Directory and Domains" topic in Exchange Server Help. To view this Help topic, follow these steps for the appropriate program.
Exchange Server 2010

  1. Start Exchange Server 2010 Help.
  2. Click the Contents tab, expand Deployment, expand New Installation, expandPreparing to Deploy Exchange 2010, and then click How to Prepare Active Directory and Domains.

However as you would expect with Microsoft, the information in the article is not accurate for the post SP1 release, let alone the Rollup 1 to SP1.

We tried running from the CD and found the error: "configuration version 13214 is higher than setup’s version 12640 therefore, Prepare AD can’t be executed.

We worked out that this is because there is a new version of “setup” that comes with the SP1 download. We had hoped that this would have been updated into the Exchange server V14 / Bin directory. But it appears not.

So next we had to download the SP full release version from here:

and extract the file (by clicking it) to a directory that would then allow us to run the “setup /prepareAD” from that location.

We did this, and got a message that looked like this:


We then restarted the service “Microsoft Exchange Information Store”


Found exactly the same errors:


so next we restarted the server.

Nothing. What we then discovered was that the file size of the .edb database associated with this mail data store database was 0 byte in size.


We tried without success to use database recovery tools, but it was obvious from the size of the transaction log files that the data was actually gone forever.


That only leaves us with 2 options.

1. Restore from backup (disaster style)

2. Backup outlook Profiles to .pst, then one by one recover to a new creation of the database name.

Either way, this experience was totally crap (typical Microosft). All we did was allow an automatic update from Microsoft to run on the server. It was the Rollup 1 for SP1 exchange server 2010.

My advice. Buy a Mac, and get yourself some iMail accounts! Who needs this crap!

Microsoft – You totally suck!

Windows 2008 Server IE Security Warnings All the Frigging Time!

Ever wondered how to stop IE from giving you the Add Site messages all the time on a windows 2008 Server?

Open Server Manager

Under Security Click – Configure ESC

And Just Turn it Off!


Yeah it is a little less secure when roaming the net. But I don’t roam the net on a server anyway! and yeah it is an overkill to turn it all off rather than tame it down…, but I was not the lame programmer who came up with a system so annoying that by the time you turn it off you are just pleased to see the end of the dam thing.

Kind of rings like UAC in Vista…

Just one more reason to consider a mac! (Mind you it is better in Vista SP2…. sorry did I say Vista, I meant Windows 7)

Troubles with Exchange 2010 and Exchange 2003 Routing Group Connector

We have an environment which includes a combination of Microsoft exchange server 2010 and Microsoft exchange server 2003 existing on the same domain.

The various reasons at the moment we want to leave both versions of exchange coexisting. What we have noticed is that there are at times delivery problems between the routing group connector that is automatically configured when you add an exchange 2010 server to an existing 2003 domain.

This was evident by checking the queue in the exchange 2003 server. It showed that a number of messages were pending delivery and of the status was in “retry”.

Naturally enough, Google was our first point of call on this matter and we discovered that there were many others are experiencing delivery problems between the two servers.

In our case, the problem may well have initially risen due to some necessary changes that we made with the default routing of e-mail being sent from our exchange 2003 server.

After we made the configuration changes and attempted a short-term fix to another problem by using a smart host server, we found that how playing around with the settings was likely a contributing factor to the routing group connector problem.

To solve this problem we performed the following actions.

1. We log on to the existing 2010 exchange server.

2. We started the application known as exchange management shell

3. We listed our existing exchange connectors by typing the following command

  • Get-RoutingGroupConnector

4. We expanded on this list to confirm the details by typing the following command

  • Get-RoutingGroupCOnnector | fl

the results looking something like this:

Identifying the name of the existing connector as: VSERVER13-DGM56G41

5. We use the following command to delete all remove the existing connector:

  • Remove-RoutingGroupConnector -identity “VSERVER13-DGM56G41”

6. Initially this area out referencing: Multiple Instances  So we had to look in more detail at the screen capture above of the listed connectors lost using be  |f1 command , to find the name referenced against Guid: a long string of numbers looking something like this :

We then use the following command referencing the GUID to remove that connector:

  • Remove-RoutingGroupConnector -identity “8276G-736b-37698726-3782661b78”

7. We then checked that the existing connector was removed by a gang typing:

  • Get-RoutingGroupConnector

The showed no results and we also verified in the exchange 2003 server that the exchange routing group connector had been removed from the list there.

    8. We then created a new wrapping group connector called “VSERVER13-DGM56G41”

The two servers that we were connecting were server1 (exchange 2003) and server2 (exchange 2010). We use the following command to complete this:

  • New-RoutingGroupConnector -Name “VSERVER13toDGM56G41” -SourceTransportServers “” -TargetTransportServers “” -Cost 100 -Bidirectional $true -PublicFolderReferralsEnabled $truethis created

9.Then we use the “Get-RoutingGroupConnector” commandto gain verify the existence of the new connector. Once verifiedour problems were solved… or was it???

We did fix the connector and again mail was delivered. What we then found was after some time the connector would fail. WTF you say… as I did! I hit google again and again and again, found loads of people talking about similar problems but none with suggestions other than what I had done above.

Then I discovered a hidden little nugget of gold. Turns out that Exchange 2010 (and possibly Exchange server 2007) will not accept remote mail unless the pickup queue is located on a server with a minimum of 4 GB free space. By default this is the C: drive.

Now there are a few things we found that impact that.

1. After the server is rebooted, and even with less than 4 GB it will accept mail for a short time. (This I suspect is just to trick the heck out of us).)

2. The free space will shrink and grow a little with server maintenance. So don’t just look at a disk with 5 GB and say, all is well.

3. There appears from what I can see to be absolutely NO announcements in the server log files about the queue shutdown. It just stops!

So free some space, or research on moving the queue pickup to another drive. (I will not list it here, but it is easy to find in Google). Good luck and may you be blessed with low disk space as the cause of your problems as I was!

Finally Solved!

Hyper-v Guest OS Failed to start – Failed to create memory contents file

When trying to start a Hyper-V server we received this error.

Failed to create memory contents file ‘F:\ProgramData\Microsoft\Windows\HyperV\Virtual Machines\….(some numbers)…\..morenumbers.bin’ of size 2048MB.

Screen Shot of error when Start Guest OS

The solution for this problem is simple. Make more space available on the drive with the Hyper-V VHD file. The message is indicating that the drive has run out of space.

It would be nice if Microsoft could dumb it down.