Tag Archive: services


Running the Exchange 2007 BPA today brought back a few errors, let’s go about setting them right. the first is Max Database Cache Size.

Exchange BPA Warning

Exchange BPA Warning

As you can see there are other errors, for other posts. So, if you click the Tell me more about this link, it takes you to the MS Technet post here. They ramble on and on describing the problem and defaults, etc. Forget that, let’s just fix it (though I of course read it all).

MS Technet says “To better allow for cache growth, we recommend that the DatabaseMaxCacheSize value be increased from 128 MB to 512 MB on transport servers that have 4 GB or more of RAM.”

Well, I have 8 GB of RAM, and though I do not experience heavy message loads, I feel like the cache size should be higher than a low 128Mb (134 really).

MS Technet then says “To improve performance by using version buckets and to allow for increased database cache growth, increase the DatabaseMaxCacheSize value from 128 MB to 512 MB on Hub Transport or Edge Transport servers that have 4 GB or more of RAM.”

We will start by editing an Exchange config file with a value for DatabaseMaxCacheSize.

Start>Run and enter %ProgramFiles%\Microsoft\Exchange Server\Bin

Find the file EdgeTransport.exe.config and right click it, selecting edit (Use Notepad). If Edit is not an option, click Open With and select Notepad.

NOTE: I like to backup all system files before I edit them. I have a spceial folder that I keep edited files in case I need them. In this case, I copy EdgeTransport.exe.config and place it in my backup folder (removable HDD) and add .old to it.

On the page displayed, about half way down is a line:     <add key=”DatabaseMaxCacheSize” value=”134217728″ />

This is our value. Replace the 134217728 with 536870912.

Exit the EdgeTransport.exe.config and make sure you save it on the way out.

MS Technet then tells us to stop the Exchange Transport service and restart it by using a command prompt and net stop msexchangetransport && net start msexchangetransport

I would rather do the GUI, so I click Start>Run and type in Services.msc

Right click Microsoft Exchange Transport and click Restart.

Restart Transport

Restart Transport

Thats it. Rerun the BPA and the warning is gone.

If you notice stability issues with Exchange, revert this setting back to the old setting by editing, or restore the .old file.

Advertisements

The process cannot access the file because it is being used by another process (HRESULT: 0x80070020).

CentralAdmin Error

CentralAdmin Error

This is a simple file in use, except with ports- Windows cannot start centraladmin on port 4721 because it is already using that port. Your options include binding centraladmin to a different port, and restarting IIS, or finding out what is on that port, and fixing it.

Without doing anything, open a command prompt by clicking Start>Run> and typing cmd.

In the black box, type netstat -ano > C:\netstat.txt

Hit Enter.

Navigate to your C:\ drive. Double click the text file named netstat.

Scroll down the list untill you see the port 4721 on the end of an IP address in the second column. It will look something like this:

  TCP    0.0.0.0:4721           0.0.0.0:0              LISTENING       4612

The last number is the Process ID.

Now pres Crtl-Shift-Esc.

Click on the Services tab.

Scroll down until you find the PID that matches the one from our Netstat.

Task Manager

Task Manager

As you can see from my example,. it is Microsoft Exchange Mailbox Assistant. This “Performs background processing of mailboxes in the Exchange store”. I know from past experience that this is not a super critical process, like the Transport Service, though it will supply errors if turned off.

So we won’t turn it off, but lets pause it. This is in hopes that CentralAdmin will take the port back, and then MS Exchange will assign a new dynamic port to the mailbox assistant.

Open Services MMC under Administrative Tools. Find the Mailbox Assistant. Right click it and select Stop.

Go back to your command prompt window and type iisreset.

Now check on CentralAdmin, either by trying to navigate to it or opening IIS Manager. It is started. Now go back to Services, and restart the Mailbox Assistant. It started without trouble.

Let’s double check that the mailbox assistant is assigned a new port.

I check the PID, and cross reference it against a new netstat output and see:

  TCP    0.0.0.0:44824          0.0.0.0:0              LISTENING       5424

Exchange dynamically assigned the port of 44824- much better.

This process can be done with nearly anything. Often times you will install new software and it will take the port of some existing site- this is the process to correct it. Skype is a known culprit. Just make sure you research the  service you are stopping before cutting it off. Stopping SQL (SBSMONITORING) would probably be a bad thing, as would stopping some of the more important Exchange services or any system processes. In those cases, it might be better to change the site binding port.

%d bloggers like this: