Tag Archive: troublshoot

So you log into the SBS console and there is always a red X next to your server. When you navigate to Devices>Server, and click View Computer Alerts, you are confronted with an error:

The Best Practices Analyzer has completed a scan of your system and has found errors in your system configuration. For detailed information about the scan errors, manually run the Best Practices Analyzer tool. Error Count: 1

Well, let’s do what it says. Start>All Programs>SBS Tools>SBS 2008 BPA

If you dont have the BPA, you can download it here.

Click Go To Welcome Screen, then Select Options For a New Scan. Enter a label if you wish, I generally do not. Click Start Scan.

Wait 2-5 (mine takes 4:23) minutes, until it says complete, then hit view results. There is one critical issue. Mine happens to be

BPA Results

BPA Results

Yours might be different, but whatever the issue is, you should resolve it. My issue is that a DNS A resource points to two ip addresses: my server IP of and my RRAS IP of I wont be solving this at this time as it is not causing issues, but I will show you how to stop the daily alert from the BPA.

When you install the BPA, it sets a scheduled task to run nightly. This is cool, but I don’t need it running nightly- I run it once a week, or after major changes to Windows- why does it need to run daily. Go to Control Panel>Administrative Tools>Task Scheduler.

Click Task Scheduler Library- you should see a few scheduled tasks, one of them being SBS 2008 BPA. Right click the task, and click Delete and confirm.

Keep in mind that “Hide this alert from all results” from inside of the BPA will not stop the computer alert from displaying in the SBS Console.

UPDATE: One more thing you will need to do. Go to the SBS console, and click the Network tab. then click View Notification Settings on the right menu. The click Event Log Errors on the left manu. At the bottom, uncheck the BPA alert notification.

Notification Settings

Notification Settings

Exchange Management Console Database Recovery

Exchange Management Console Database Recovery

I now extracted a new copy of the mailbox database from the backup, using NTBackup again. I restored it to my desktop, not the original location. I opened MS Exchange 2007 MC, and clicked on Toolbox in the navigation pane. Then I clicked on Database Recovery Management. I left everything default and hit next, next.

  1. I clicked Create a Recovery Storage Group.
  2. I left everything as default, default name, and linked it to the First Storage Group, which now contains my current mailboxes.
  3. After the wizard completed, I navigated to the location of the storage group folder, which is inside my First Storage Group folder.
  4. I copy all of the files from the restored Exchange database folder- about 3 Gb in 25 files.
  5. I then try to mount the database from inside the Database Wizard- which comes back with some MapiCallError. Gah!
  6. So I run Repair Database. It gives me a warning- but at this point, who cares.
  7. I let it run, and it completes. And the database mounts successfully!

Now how do I get the mail back? I run the Merge or Copy wizard, which I zip through not really knowing what is going on- and after completion, it restored no mailboxes, the GUID did not match. So I take some more time, and click advanced options. I match and sort by Mailbox Name and try to merge again- still an error with the matching. So I go back into advanced options, and I Restore them to my admin mailbox. I create a folder called Restore, and select all the mailboxes to restore. This runs for a while, and I am seeing items appear.

And then they stop appearing, and my email slows to a crawl. Ugh, Exchange. I delete all of the exported items, half of which did not show up anyhow. So I decided to try a slower approach. I export ONE users mailbox into my mailbox at a time, and it worked. I then exported each of the items from that restored mailbox out of Outlook to a shared folder. I go to a workstation, and log in as that user, and then import their old mail items back into their Exchange mailboxes. It works, thank God. There is a way to do it from the server using EMS, but this requires Exchange Tools 32bit, which you can’t install on a 64bit server. So since I would need to go to another PC anyways, I might as well just restore them from PST files. A whole lot of this episode could have been avoided by knowing exactly what was going on- which I now do. If anyone needs any advice, please feel free to post here and I will do my best to provide the appropriate resources.

I will say that this was a really really tough job to do- going into it I had never even touched an Exchange database or transaction log except to break them. The issue was that last month I performed a full server format and install. The backups were not working, and the office needed services. so I formatted C: and reinstalled SBS2008. I set up the domain exactly the same- same DNS, IP configurations, even the same software and hardware.

As you might guess, a format and reinstall- even if it is EXACTLY the same- does not restore users mailboxes. So I went about trying to extract the mail items directly from the mailbox database files. This didn’t work, as EXmerge is discontinued. In order to use it to extract .PST files you need to install 32bit Exchange Tools, which I did not have the time nor patience for. If you need to find Exmerge it can be downloaded from Microsoft here, and documentation on the process can be found in KB259688.

I then set about recovering users email. I had just restored the server at this point, to what I though were exactly the same settings as before. Working with Exchange database’s can be nerve-racking if you don’t know what you are doing- they are huge, usually premissioned away from normal access, located in one of several places on a server. I though I would just try to stick the database back in and turn on Exchange to see if it worked. So I navigated to D:/Program Files/Microsoft/Exchange Server/Mailbox/. I then dismounted the Exchange databases from inside of EMC, and stopped Exchange services including Information Store and Transport. I renamed the First Information Store folder to First Information StoreOLD, and created a new folder. I then copied all of the Exchange files that I extracted from the backup, using legacy NTBackup. I had a script on the old server that ran a NTBackup of Exchange.

(This is a good practice by the way, which allows me to mess with Exchange backups without restoring other things on the server. NTBackup can be found here, and some tips on using it are here. Mind you the tutorial is for SBS 2003, but the general gist is applied to the newer version.)
So, after all of the files copied over, I restarted Exchange. I ran the BPA, and got some major errors about not being able to mount the stores. I then tried to run the database recovery tools on them, still getting the you-broke-exchange errors.

Uh-oh. What the heck am I doing? So I reversed all of that, and put it on a back burner for a bit. I calmly explained to users that they lost years worth of email and had to deal with it- oh boy. But wait… There is another solution, at least temporarily. Since the domain is the same, but the workstations had not yet been rejoined to the domain, old logon credentials might exist. I sat down with a user to log in, and got a security error. Darn. So I unplugged the workstation from the network, and we then logged on using old cached credentials.

We open up Microsoft Office Outlook. Hit File, Export (or appropriate), and exported Inbox, Sent Items, Contacts, and Calendars to .PST files. We saved them on the root of C: drive, anywhere in the current profile would be lost once we left the domain. At this point we plug the workstation in and then I join it to the domain using Computer>Properties>Network ID. The domain solace.local is already there, and that is the same domain name as well. So I delete the .local, and rejoin the solace domain. Reboot, have the user log in/create a new profile/change password/etc. Open up Outlook, and reverse the export process, importing the .PST files. All of their items were then added to their NEW Exchange mailbox.

The only problem came up when I got to the 20 users who did not have Outlook, and who worked remotely using OWA. How can you export .PST files from OWA? Well, you can’t. So these users I had to explain to them how badly I sucked, and that it wasn’t my fault, and that this sort of thing happens, and that no- we had not planned a disaster recovery plan. Pretty much anything so I could go hom and go to sleep.

I put this on the back burner for a week, asking users to contact people about resending them mail, or whatever they had to do to get by. I then set to researching Exchange Recovery Storage Groups. Great tutorials here and here.

I then realized that I had not applied SP2 to Exchange 2007, which had been applied before the re-install. Sweet- so I downloaded and ran the Exchange SP2 Install Tool from MS. Ran Exchange SP2, which succeeded. Restarted the server, made sure all my services were up and running- Transport was not, so I started that. As far as I could tell, everything was peachy. Gonna continue this in a new post..

%d bloggers like this: