Microsoft Exchange

Microsoft Exchange rpc client access service high cpu

Posted on by Imran Rashid
Reading Time: < 1 minute

Using Microsoft Exchange 2010 SP1 or SP2 with roll up packs installed. The RPC Client for Microsoft Exchange is taking up large amounts of CPU causing your exchange server CPU to hang at 100%.

This could be due to a couple of reasons, one is Pubic Folders and the second OAB, so this would be a starting point.

If you don’t have a Public Folder store, create one and monitor the CPU whilst you mount it. If CPU decreases but starts to increase again, dismount the Public Store and leave dismounted. CPU should start to stabalise. You may need to restart the Microsoft Exchange RPC client service.

Also, if you are using Citrix/Xenapp, if you find that lsass.exe takes up large amounts of CPU, this may resolve the issue after the Citrix servers are rebooted.

Increase Exchange 2007 mailstore limit

Posted on by Imran Rashid
Reading Time: < 1 minute

Locate the registry key for the mail store by browsing to the below location.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<SERVER NAME>\Private-00000-0000-000e-0000-0000000000 (To locate the private guid for your mailstore click here)

If the value ‘Database Size Limit in GB’ already exists, change the value to the new size in GB.

If the value does not exist within the registry, add the DWORD value ‘Database Size Limit in GB’ and set the value as required. Select decimal before setting the value.

For the change to affect straight away, you must restart the information store service. An event id of 1216 will be logged within the event log to confirm the change has been made.

If you can not restart the information store service  at this time, you can wait until the automated Exchange online defrag takes place over night.

Locate guid of mailstore Exchange 2007

Posted on by Imran Rashid
Reading Time: < 1 minute

1) Launch Exchange command shell
2) Type the below command, amending, database name, server name etc as required and press enter.

Get-MailboxDatabase -Identity “<server name>\<storage group name>\<database name>” | Format-Table Name, GUID

3) If you experience issues with the above command such as error domain controller not found, another way to locate the guid is by typing the below command. This will list all mailstores along with the guid.

Get-MailboxDatabase | Format-List

Move Exchange 2007 Transaction Logs

Posted on by Imran Rashid
Reading Time: < 1 minute

If you wish to move the Exchange 2007 transaction logs from one disk to another, for example disk C to D, follow inctructions below:

1) Dismount your exchange database from within the Exchange 2007 console.
2) Launch Exchange Management shell command from the start menu
3) Run the below command: (Replace the Storage Group Name and the location to where you wish to move the log files to.)

Move-StorageGroupPath -Identity “Storage Group Name” -LogFolderPath “D:\ExchLogs”

4) Press enter after typring the command above
5) You will receive a message after a few minutes ‘Are you sure you want to perform this action. Moving path of storage group’. Type the letter ‘y’ and press enter
6) When done all logs files from your old destination will move to your new location. May take some time depending on the number of log files.
7) Mount your exchange database

The action couldnt be completed. Try again later

Posted on by Imran Rashid
Reading Time: < 1 minute

When you carry out a search within OWA using Exchange 2010 SP1 you receive the below error:

‘The action couldnt be completed. Try again later’

This problem is a result of installing/upgrading a multi-role server (a server that has the Mailbox, Client Access, and Hub Transport roles installed) to SP1 and then removing the Hub Transport and Client Access roles, thereby leaving the server with only the Mailbox role installed.

There is a symbolic link for each language referenced in the registry, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Language. The symbolic links (ActiveX CLSID of the class used) allow for word breaking and stemming for the locale corresponding to the language.

During the Exchange 2010 Service Pack 1 uninstall process for the Hub Transport role, setup removes the symbolic links, regardless of the fact that the Mailbox role is still present. The removal of the symbolic links causes the generation of content indexing files to fail.

Microsoft have provided a script to resolve this. Click here BUT firstly reboot your Exchange server and test OWA search again. If this does not resolve the issue, run the scripts documented in the link above and test again. If this does not resolve the issue, you may need to reboot the exchange server for changes to take affect.