John Yassa's Blog

Home » 2012

Yearly Archives: 2012

Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server

When you try to install MS Exchange 2010 SP2 in windows server 2008 R2
you may face the below error (below screen shoot)
Also getting the error: Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server. I’ve attempted wiping the entire HDD, re-installing Windows Server, and then re-doing the Exchange install, only to get theexact same error the second time. All drivers are loaded properly and everything else (IIS/DNS/AD) is working fine.

untitled

This problem can be caused by disabling ipv6.
The below URL is how to disable IP V6 on the mentione
http://support.microsoft.com/kb/929852

After disableing IPv6 everything working fine

Find The Total Number Of Mailboxes In Your Domain

How can you quickly find the total number of mailboxes in your Domain? You can do it now by running a shell command.

Get-Mailbox -ResultSize unlimited | Measure-Object

You can further customize the command to your  requirements. Let’s say that you want to find out the mailboxes in one particular database or one particular server. You can find it by adding more switches to the above command. Run the following…

Get-Mailbox –database dbname -ResultSize unlimited | Measure-Object

Get-Mailbox –Server servername -ResultSize unlimited | Measure-Object

There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)

When you install Exchange 2010 SP2 , you face an error There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)

“$error.Clear();
if (!(get-service MSExchangeADTopology* | where {$_.name -eq “MSExchangeADTopology”}))
{
install-ADTopologyService
}
” was run: “There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)”.
There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)

It seems the error is caused while trying to add a firewall rule, indicated by Interop.NetFw.INetFwRules.Add (INetFwRules is the rules collection of the built-in Windows Firewall).

I had a quick check with the firewall settings on the machine and it turned out the Windows Firewall was disabled. I figured that perhaps adding the rules failed because setup couldn’t communicate with the firewall service.

I enabled the Windows Firewall and this time the upgrade process went fine

 

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.

 

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

Exchange Mangement console shows error “the ws-management service cannot process the request, the system load quota of 1000 request per 2 seconds has been exceeded” when you open it

When you open Exchange Management Console , it refuse to load and shows the following error “The WS-Management service cannot process the request. The user load quota of 1000 requests per Z seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least Z milliseconds”

after search, an IISRESET or IISRESET /NOFORCE just solved my probelm and i could browse the Exchange Management Console normally

 

Disable “Automatically update e-mail addresses based on email address policy”

If you need to diable the “automatcially update e-mail addresses based on email address policy” option using powershell

1- For 1 user:
Set-mailbox  “MailboxAddress” -EmailAddressPolicyEnabled $false

2- For the whole mailboxes:
Get-mailbox | Set-mailbox  $_.Identity -EmailAddressPolicyEnabled $false

3- For some users within same OU:
Get-mailbox -OrganizationalUnit “OU name”| set-mailbox EmailAddressPolicyEnabled $false

4- For some users with the same domain name:
Get-mailbox -filter {EmailAddresses -like ‘*@Domain.com’} | Set-mailbox  $_.Identity -EmailAddressPolicyEnabled $false

After creating mailbox store , you face the error when you try to mount (MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)

After creating a new mailbox store , you try to moun the mailbox store , but it failed with the below errors:

Failed to mount database ‘<test3>’.

<test3> Failed Error: Couldn’t mount the database that you specified. Specified database: <test3>; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation  failed with message: MapiExceptionNotFound: Unable to mount database(hr=0x8004010f, ec=-2147221233) [Database: <test3>, Server:<Servername>].

An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database.(hr=0x8004010f, ec=-2147221233) [Database: <test3>, Server: <Servername>

An Active Manager operation failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233) [Server: <Servername>] MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f,ec=-2147221233)

This issue occurs when the value of the ConfigurationDomainController parameter and the value of the PreferredGlobalCatalog parameter are different. In this scenario, the Mailbox database operation fails because of the replication latency that occurs between the configured domain controllers and the preferred global catalog.

I have tried to run the command get-ADServerSettings, and i got null result for the (Preferred Domain Controller)

To resolve this issue, set the preferred Active Directory server in Exchange Management Shell to the following cmdlet: Set-ADServerSettings –PreferredServer <DC FQDN>

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

Publish Multiple OWA & ECP Virtual Directories on one Exchange 2010 CAS Server

Suppose you host more than one domain at your Exchange server , and each company need to have its OWA URL , below is steps how you can implement more than one OWA & ECP on one Exchange 2010 server

1- Create a new WEB SITE
– New IP
– Ports 80 / 443
– Name WebMAIL
– Default Path – C:\inetpub\wwwroot

2- Install Certificate (HTTPS) for External User

3- Copy the Folders:
C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa
C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp
to
Ex:
C:\Program Files\Microsoft\Exchange Server\V14_domainname\ClientAccess\Owa
C:\Program Files\Microsoft\Exchange Server\V14_domainname\ClientAccess\ecp

4- ON IIS – ISAPI and CGI Restrictions
Give Permission ALLOW to this DLL
C:\Program Files\Microsoft\Exchange Server\V14_domainname\ClientAccess\Owa\auth\owaauth.dll

5- On Exchange Power Shell
new-owairtualDirectory -WebSiteName “WebMAIL” -Path “C:\Program Files\Microsoft\Exchange Server\V14_domainname\ClientAccess\Owa”

New-ecpVirtualDirectory -WebSiteName “WebMAIL” -Path “C:\Program Files\Microsoft\Exchange Server\V14_domainname\ClientAccess\ecp”

6- Fix Virtual Directory Path
Exchange
Exchweb
Public
In IIS – change – The Virtual Directory Path
….\V14\ClientAccess\Owa
to
….\V14_domainname\ClientAccess\Owa

7- In Exchange Console
– Server Configuration > Client Access > <server> > Outlook Web APP > owa (Mail) > Properties Authentication > Use one or more standard authentication methods > FBA

– Server Configuration > Client Access > <server> > Exchange Control Panel > ECP (Mail) > Properties Authentication > Use one or more standard authentication methods > FBA

8- Reset IIS

Now try to browse the URL of the new OWA

%d bloggers like this: