John Yassa's Blog

Home » Posts tagged 'exchange'

Tag Archives: exchange

550 5.7.1 RESOLVER.RST.AuthRequired; authentication required

When you Send to DL in Exchange 2007 or Exchange 2010 , you recieve the error 550 5.7.1 RESOLVER.RST.AuthRequired; authentication required

Reason:
By default Exchange 2007 or Exchange 2010 requires that a sender be authenticated before being able to successfully send to a distribution list. Consequently external users are unable to send emails to it.

Solution:
1- From the properties of the distribution list in Exchange AD: Exchange General tab, Un-tick From authenticated users only
2- From the properties of the distribution list in Exchange Management Console: Mail-flow settings tab, Message Delivery Restrictions, un-tick Require that all senders are authenticated.

 

Can’t mount Database with error ,Unable to mount database. (hr=0x80004005, ec=-550)

Couldn’t mount the database that you specified. Specified database: DB2; Errorcode: An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database ‘DB2’ was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s):

An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)

Before you can mount a database restored from a backup, it needs to be in a clean shutdown state. You can use the Eseutil tool to check whether a database is in a clean shutdown state – if it is not in a clean shutdown state you can perform a repair to get the database into consistency.

Soft Recovery using Eseutil

The first thing you want to do is verify that the database is in a dirty shutdown state. We can do this using the eseutil /mh command. For example:

the output should be as below:

as long as you can it shows that the DB is closed dirty shut down
also you can see the logs that is missing
we can replay the log files into the DB (if they only exist) using the command eseutil /r /l /d

For example, my log file prefix is E03, and my database and logs are stored in G:\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\DAGDB1

after it finsihed you can the first command eseutil /mh to confirm that the DB is now in clean shut down state

if after these steps , you try to mount the DB  if it fails to mount then you will have to do a hard repair using the command  eseutil /p

after it finsihed you can the first command eseutil /mh to confirm that the DB is now in clean shut down state , then try to mount the DB , it should mount with you with no problem

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: