Exchange 2003

All posts tagged Exchange 2003

Can’t remove the Exchange Virtual Server

Posted by Johan Veldhuis on 10-06-2011
Posted in: Exchange 2003. Tagged: , . Leave a Comment

During the removal of an Exchange 2003 cluster I had the issue that I couldn’t remove the Exchange Virtual Server from the Cluster Administrator.

In the event log nothing special was logged so it was time to dig into the log files which are created during this process. Since the removal of Exchange Virtual Server is a cluster related task the cluster log file was needed. This is located in the c:\windows\cluster directory.

When having a look at the log you will see that several settings are checked before the Exchange Virtual Server is removed.

[11:21:42] Leaving ScTestAceOnObject
[11:21:42] ANONYMOUS LOGON does have READ permissions for MDB objects on the organization
[11:21:42] Checking to see whether the Exchange Domain Servers group has been DENIED Receive-As permissions on the Servers container(s)
[11:21:42] Checking the ACL on the Servers container in the admin group “First Administrative Group”
[11:21:42] Entering ScTestAceOnObject
[11:21:42] Attempting to get DOB for DN “/dc=LOCAL/dc=Corp/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=Corp/cn=Administrative Groups/cn=First Administrative Group/cn=Servers”
[11:21:42] Attempting to read security descriptor from DOB
[11:21:42] Attempting to initialize CAce object
[11:21:42] Testing to see if given ACE is present
[11:21:42] Test succeeded; fACLPresent = TRUE, fExtraRights = FALSE
[11:21:42] The ACE tested for is present in the ACL of this object
[11:21:42] Leaving ScTestAceOnObject
[11:21:42] The Exchange Domain Servers group has been DENIED Receive-As permissions on the Servers container(s)
[11:21:42] The required permissions have already been set
[11:21:42] Leaving ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[11:21:42] Entering ScFindRoutingGroupThatContainsServer
[11:21:42] Leaving ScFindRoutingGroupThatContainsServer
[11:21:42] ScPRQ_ServerIsNotHomeServerForPostmasterOfNonEmptyOrg (f:\tisp2\admin\src\udog\excommon\prereq.cxx:2981)
Error code 0X80072030 (8240): There is no such object on the server.
[11:21:42] CCompServer::ScCheckEVSPrerequisites (f:\tisp2\admin\src\udog\exsetdata\components\server\compserver.cxx:1405)
Error code 0X80072030 (8240): There is no such object on the server.
[11:21:42] ScSetupExchangeVirtualServer (f:\tisp2\admin\src\udog\exsetdata\exsetds.cxx:1541)
Error code 0XC103FC97 (64663): Setup encountered an error while checking prerequisites for the component “Microsoft Exchange Server”: 0X80072030 (8240): There is no such object on the server.
[11:21:42] Leaving ScSetupExchangeVirtualServer

For example several ACL’s are verified. Besides the ACL checks the removal process will verify if the postmaster mailbox is homed on this server. By default the account used for installing Exchange 2003 will automatically be the postmaster. If the mailbox can’t be found, because it’s deleted, the process will be aborted.

But how can you solve it? Well first and easiest method maybe to restore the account and mailbox from the backup. If this is not possible you might decide to re-assign the postmaster mailbox to another account.

To re-assign the mailbox to another account you must use ADSIEDIT. Before making any changes with ADSIEDIT make sure you have a correct and recent back-up of your Active Directory.

Once you have confirmed this it’s time to make the change. Open the Configuration partition of Active Directory and expand the following nodes:

  • CN=Services
  • CN=Microsoft Exchange
  • CN=Organization Name, for example Corp

Get the properties of CN=Global Settings and search for the attribute called MsExchAdminMailbox. You will see the value of this attribute has been a deleted object:

In this case the attribute has the value CN=Exchadmin\0ADEL:bbf20ca9-7def-4e0f-bdd9-f9107c1643d6,CN=Deleted Objects,DC=Corp,DC=local. The DEL means the object doesn´t exist anymore. To solve this issue replace the value with a value of an existing user, for example CN=Postmaster,DN=ServiceAccounts,DC=Corp,DC=local.

 After AD replication has occurred you should be able to remove the Exchange Virtual Server using the Cluster Administrator tool.

Uninstall of Scanmail 8 doesn’t remove everything

Posted by Johan Veldhuis on 30-05-2011
Posted in: Exchange 2003. Tagged: , , . Leave a Comment

During the removal of an Exchange 2003 cluster I found an issue after the removal of Trend Micro Scanmail (SMEX) 8.0. After the deinstallation was completed the Cluster Administrator started with an error. Once of the things I expected to cause the issue was the resource object from SMEX which was still there. This could be solved easily by removing the default procedure for removing cluster resources.

Despite removing the resource the Cluster Administrator kept prompting with and error. After some research I discovered that the issue was caused by a resource type clusRDLL which was still their.

To cleanup this resource type you will need to use the cluster command:

cluster restype clusRDLL /delete /type

After this command was executed the error did dissapear and I could remove the Exchange 2003 Virtual Server.

Trend Micro has published a knowledge article about this issue:

Uninstalling Scanmail for Exchange (SMEX) 8.0 from cluster servers open

MapiExceptionNotFound: Unable to delete mailbox

Posted by Johan Veldhuis on 14-05-2010
Posted in: Exchange 2003, Exchange 2010. Tagged: , , . Leave a Comment

During a cross-forest test migration from Exchange 2003 to Exchange 2010 I got the following error:

Warning: Unable to update AD information for the source mailbox at the end of the move.  Error details: An error occurred while updating a user object after the move operation. –> Failed to find the address type object in Active Directory for address type “SMTP:AMD64″.
Failed to cleanup the source mailbox after the move.
Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)

When I looked in the old and new environment I found out that the mailbox both existed in the old and new environment. In this  case you might have a big issue even when the mail is delivered in the Exchange 2003 environment  and the homeMDB attribute is not updated. Updating the attribute may take a while due to AD replication, in this case mail is not delivered in the new mailbox and so mails will not be placed in the new mailbox.

To prevent this issue Microsoft has released a hotfix for Exchange 2003 which can be found on the website below.

open

Supported upgrade paths

Posted by Johan Veldhuis on 22-09-2009
Posted in: Exchange. Tagged: , , , . Leave a Comment

As Exchange 2010 is almost there you may got the question from which version of Exchange can I upgrade to 2010 and which versions can run besides each other. Below an overview of this and the prerequisites you must met:

old versionnew versioncoexistence supportedprerequisites
Exchange 2000Exchange 2007
yes
Exchange mode must be native
Exchange 2003Exchange 2007
yes
Exchange mode must be native
Exchange 2003 SP2Exchange 2010
yes
Exchange mode must be native.
At least one Windows 2003 SP2 GC per AD site
Forest level must be Windows Server 2003
Exchange 2007 SP2Exchange 2010
yes
At least one Windows 2003 SP2 GC per AD site
Forest level must be Windows Server 2003

When you would like to have more info after having a look at the table have a look at the sites below:

Exchange 2007
Upgrading to Exchange 2007 open
Coexisting with Exchange Server 2003 and Exchange 2000 Server open

Exchange 2010
Planning Roadmap for Upgrade and Coexistence – Exchange 2003 open
Planning Roadmap for Upgrade and Coexistence – Exchange 2007 open

Problems removing Exchange 2003 cluster

Posted by Johan Veldhuis on 14-04-2009
Posted in: Exchange 2003. Tagged: , , . Leave a Comment

During one of my forum visits I found a really interesting issue. Someone tried to remove his old Exchange 2003 cluster but received the following error when trying to dit it:

Found no Disk resource for the disk that contains the folder ‘W:\EXCHSRVR’

When looking in the Cluster Administrator the resource was not visible, very strange. So we needed to remove the pointer to the w:\ disk by using ADSIEDIT.

Before performing such an action you will first need to create a backup of your AD.

Next execute the following steps:

- open adsiedit
- choose connect to
- change the domain to configuration
- expand CN=Configuration …
- expand CN=services
- expand CN=Microsoft Exchange
- expand CN=First organization (or your organization if different)
- expand CN=servers
- expand CN=servername
- expand CN=Information Store

There you will find the First Storage group and other storage group. Get the properties of them both the storage group and the databases in it it and check if none of them points to the w:\disk
But in this case it was something else where we need to have a look at, perform the same steps as above but stop after expand CN=servers and continue with the steps below:

- get the properties of theservername
- search for the value MsExchDataPath
- check if the pointer is not listed

After this try to remove the Exchange cluster again.

Exchange 2003 keeps resending the same mail

Posted by Johan Veldhuis on 04-03-2009
Posted in: Exchange 2003. Tagged: , . Leave a Comment

Today I had a nice issue with Exchange. For some kind of strange reason Exchange 2003 kept sending the same mails.  Even when deleting the mails from the queue in the Exchange System Manager. A result of this was that the bandwidth was almost used 100% so I adjusted the simultaneous connections etc, without any effect.

So I decided to search for a solution for this issue. I found a post on expert-exchange which described almost the same issue. It adviced to use MFCMAPI to cleanup the temp table. The specific messages may get stuck in that table

After applying the solution the issue was solved indeed, below you will find the steps to solve the issue:

  • download and install MFCMAPI
  • choose session and select logon and display store tables
  • if there are multiple profiles found you will be asked to select a profile, in this case select the administrator profile
  • an overview of the mailbox and public folders will be displayed. Select MDB  and choose the option get mailbox table
  • an overview of all mailboxes found in the store will be displayed. Search for the mailbox of SMTP
  • search in the left pane for Temp Tables
  • delete all sub folders below the Temp Tables, when asked if the messages need to be hard deleted choose to do this
  • restart the SMTP service

Microsoft Exchange System Manager for Windows Vista 1.0

Posted by Johan Veldhuis on 21-08-2008
Posted in: Software. Tagged: , , , . Leave a Comment

Microsoft has release version 1.0 of the Exchange System Manager for Windows Vista. With this tool you can manage your Exchange 2003 server from a Vista machine. There are a few restrictions in the software, belof a few of them:

  • SMTP current session node is not supported (SMTPadmin.dll cannot be registered).
  • NNTP property view is not supported (NNTPadmin.dll cannot be registered).
  • Installing Exchange System Manager on the same computer as Microsoft Office Outlook is not supported, because MAPI CDO cannot be installed.
  • You may encounter the following issues during uninstall:
    • If Exchange System Manager is open during the uninstall process, Microsoft Management Console (MMC) is likely to crash. To resolve this, manually close the Exchange System Manager.
    • If the MAPI CDO package was uninstalled manually before uninstalling the Exchange System Manager, a runtime error may appear. This error can be ignored and the uninstall process will complete successfully.

    • Would you like to have this tool, then use the link below to download it.

    open

    Install Exchange 2007 in a Exchange 2003 environment

    Posted by Johan Veldhuis on 28-04-2008
    Posted in: Tutorials. Tagged: , , , , . Leave a Comment

    It’s time for a new tutorial, this time about installing Exchange 2007 in a Exchange 2003 environment. This can be use to migrate to Exchange 2007 and want to use the existing domain. Besides this way you can also choose for an option to migratie via a cross-forest migration, the last option is really cool because you can migrate users between forests.

    open