John Yassa's Blog

Home » Posts tagged 'exchange 2003'

Tag Archives: exchange 2003

Exchange 2003 Disaster Recovery (How to Reinstall Exchange 2003 over a Damaged Installation)

Assume that you have Exchange server 2003 , and you have lost the operating system but you still have the EDB and STM files for the databases, what can you to be up and running as fast as you can, below is the steps that can be used to rescue the exchange in our case

1.    Have a windows server installed and patched to match existing Exchange server
You will want to have the OS already installed and patched to match the existing Exchange server’s patch level.

2.  Reset Exchange Server AD account
When you make the decision to bring up the DR server you will need to reset the Exchange server’s AD account (in ADUC right click the server and choose reset account). Then rename the standby server to match the old Exchange server and join it to the domain. Change the IP address of the standby server to what the old production server was. This way you do not need to make any DNS or firewall changes

3.  Install Exchange 2003
Use setup.exe /disasterrecovery to install Exchange without creating any databases. Make sure your installation matches your old configuration (database and logs on same drives as they were in before).
Make sure that you click Action-Disaster Recovery for the Messaging and Collaboration services and for Exchange System Management Tools
Install Exchange 2003 SP2 using the /disasterrecovery switch
a. Check the following registry subkey for ServicePackBuild
i. HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup
b. If the key does not exist add the following
i. Reg_Dword : ServicePackBuild
1. Hexadecimal value : 1DD6
Install all post SP2 exchange hotfixes that were installed on prior server
http://technet.microsoft.com/en-us/library/aa997239(v=exchg.65).aspx

4. Run Eseutil /mh
Run Eseutil /mh to check if the database is shutdown in a dirty state. If the database is in a dirty state it will not mount.
If the database is shutdown in a clean state attempt to mount the Store. If successful then mail should start flowing.
Install SSL certificates on new server.

5.  If the mount attempt fails or if the Eseutil /mh shows the database is in a dirty state we will need to look at the store
If ESEUtil /mh shows the database in a dirty state proceed with step one.
If ESEutil /mh shows the database as clean but the mount fails, skip step one.
1. Attempt a Soft Recovery (A transaction log replay process that occurs when a database is re-mounted after an unexpected stop)
a. Run ESEUtil /r ENN
i. ESEUTIL /r enn /L[path to log files] /s[path to checkpoint file] /d[path to database file]
2. Verify the integrity of the database
a. Run ESEUtil / g
3. Further steps to recover would be dictated by the results of the ESEUtil /g
a. Error id’s located in this technet article
i. http://technet.microsoft.com/en-us/library/aa996027.aspx

Unable to mount any mailbox store in a storage group (event id 9518 + event id 454 + event id 494)

yesterday one fo our servers got hang , so we had to hard restart the server

once the server got up again we found that all mailbox stores under one storage group failed to brign online

and we found that the below 3 event log appeared in the event viewer :

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 494
Date:  6/24/2012
Time:  1:46:51 AM U
ser:  N/A Computer: server1
Description: Information Store (8676) Storagegroup1: Database recovery failed with error -1216 because it encountered references to a database, ‘G:\EXCHSRVR\StorageGroup1\MAilboxstore1.edb’, which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the “more information” link at the bottom of this message.
————————————————————————————————-
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date:  6/24/2012 Time:  1:46:51 AM
User:  N/A
Computer: server1
Description: Information Store (8676) storagegroup1: Database recovery/restore failed with unexpected error -1216.
————————————————————————————————-
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date:  6/24/2012 Time:  1:46:51 AM
User:  N/A
Computer: server1
Description: Error 0xfffffb40 starting Storage Group /DC=com/DC=domain/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=name/CN=Administrative Groups/CN=First Administrative Group/CN=Servers/CN=server1/CN=InformationStore/CN=storagegroup1on the Microsoft Exchange Information Store. Storage Group – Initialization of Jet failed.
————————————————————————————

we have tried to do soft recovery for mailbox store mailboxstore1 by running command eseutil /r “logbase” /l “Log path” /d “Database path”

but it failed and could repair the Database softly

the problem here was because the path of the DB and the path of the Logs wasn’t the same, so we moved the DB files to the same path as the logs and try the command one more time, and it success and could mount the all mailbox stores

An old password still works after you change it in Outlook Web Access

Assume that a user changes their password in Outlook Web Access (OWA) in one of the following versions of Microsoft Exchange Server:

  • Microsoft Exchange Server 2010
  • Microsoft Exchange Server 2007
  • Microsoft Exchange Server 2003

In this case, you may notice a 15-minute period during which the user can log on to their mailbox by using either the old password or the new password. However, if the user uses a MAPI client (such as Microsoft Outlook) to access the mailbox or if the user tries to access other files and resources, the user is authenticated only if they use the new password.

This latency exists by design for Internet Information Services (IIS) performance reasons and is controlled by the following registry setting.
Warning   If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

  1. Start Registry Editor (Regedt32.exe) on the server that is running IIS and through which the user gains access to OWA.
  2. Locate the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
  3. On the Edit menu, click Add Value, and then add the following registry value:
    Value Name:  UserTokenTTL   (Note This is case-sensitive!) Data Type:   REG_DWORD Value Range: 0 – 0x7FFFFFFF (Note This unit is in seconds.)
  4. Exit Registry Editor, and then restart IIS.

Mail stuck in queue with status “messages with unreachable destination”

Messages in this queue cannot reach their final destination server. For example, Exchange cannot determine a route or a connector to the final destination, or all available routes or connectors are marked as down.

Messages can accumulate in this queue if no route exists for message delivery. Also, if an Exchange connector or a remote delivery queue is unavailable or if it is in a retry status for a while, and no alternative available route exists to the connector or the remote destination, new messages may be moved to this queue. The administrator can then address the problem or define an alternative route.  Use the WinRoute tool to help determine available routes and route status.

To troubleshoot the queue that is causing this issue, restart the SMTP Virtual Server to reset the connector status and to retry the  messages that are queued. To restart the SMTP virtual server, follow these steps:

  1. Click Start, point to Programs, point to Microsoft Exchange,    and then click System Manager.
  2. Expand the Servers container, expand your Exchange Server computer, expand    Protocols, and then expand SMTP.
  3. Right-click the SMTP virtual server, and then click Stop.
  4. Right-click the SMTP virtual server    again, and then click Start.
%d bloggers like this: