Exchange – Event ID 25006

KB ID 0000910 

Problem

Freshly installed Exchange 2013 Server (was migrated from Exchange 2007) and it threw out this error.

Log Name: Application
Source: MSExchangeTransport
Event ID: 25006
Task Category: Configuration
Level: Error
Keywords: Classic
User: N/A
Computer: PNL-Exchange.petenetlive.net
Description:
The path to the Queue Quota component log has not been set. Queue Quota component log will not be written.

Solution

1. A quick internet search told me to check what had been set with the following commands,

[box]

Get-TransportServer |
fl Queue*

OR

Get-TransportService |
fl Queue*

[/box]

2. Above we can see three things, Get-TransportServer is a command that is going to be depreciated, there is NOTHING set for the QueueQuotaLogPath, and QueueQuotaLogEnabled is set to true (it’s turned on). Even if we use the newer syntax (below) the result is the same.

3. OK, first I created a folder on the Exchange server and tried to manually set the log path. Then I tried to set QueueQuotaLogEnabled to ‘False’ to see if that cured the problem. It would not let me do either.

Some more searching led me to find that these properties can not be changed (at the moment anyway), as they are both flagged as ‘This parameter is reserved for internal Microsoft use’.

Table Reference

WlmLogPath Optional This parameter is reserved for internal Microsoft use.
QueueQuotaLogEnabled Optional This parameter is reserved for internal Microsoft use.
QueueQuotaLogMaxAge Optional This parameter is reserved for internal Microsoft use.
QueueQuotaLogMaxDirectorySize Optional This parameter is reserved for internal Microsoft use.
QueueQuotaLogMaxFileSize Optional This parameter is reserved for internal Microsoft use.
QueueQuotaLogPath Optional This parameter is reserved for internal Microsoft use.

So, in typical Microsoft fashion, it looks like we will have to put up with this error, until they make those parameters editable. If that changes, send me an email (link below).

Related Articles, References, Credits, or External Links

NA

Exchange 2019, 2016, 2013 – Allowing a Host/IP to Relay Mail

KB ID 0000891 

Problem

There a a few more hoops to jump through to allow a host to relay though Exchange 2013. For earlier versions of Exchange see the links below.

Allow Relay from an IP With Office 365 (Exchange Online)

Allow Relay from an IP with Exchange 2010

Allow Relay from an IP with Exchange 2007

Allow Relay from an IP with Exchange 2003

Allow Relay from an IP with Exchange 2000

Solution

How to create a ‘Relay’ Receive Connector

 

1. Connect to the Exchange admin center > Mail flow > receive connectors > Add.

2. Give the connector a name (take note of it, you will need it in a minute) > Select ‘Frontend Transport’ > Custom > Next.

3. Accept the default of TCP Port 25 (SMTP) > Next.

4. REMOVE the 0.0.0.0-255.255.255.255 range. (WARNING: If you do not do this you will become an open relay).

5. Add in the IP address of the host (from which you want to allow relaying) > Save.

6. Open the properties of the connector you just created > Security > Under Authentication select ‘Externally Secured (for example with IPSEC) > Under Permission groups, select ‘Exchange servers’ and ‘Anonymous users’ > Save.

7. At this point, you may find that when you test from the host you get the following error;

421 4.4.1 Connection timed out

I would suggest you change some parameters of the receive connector. Execute the following PowerShell command;

[box]

Get-ReceiveConnector -Identity “Relay-Connector-Name” | Set-ReceiveConnector -TarpitInterval 00:00:00 -ConnectionTimeout 00:30:00 -ConnectionInactivityTimeout 00:20:00 -MaxAcknowledgementDelay 00:00:00 -MaxInboundConnection 10000 -MaxInboundConnectionPercentagePerSource 100 -MaxInboundConnectionPerSource unlimited

[/box]

8. Restart the Microsoft Exchange Transport Service on the Exchange server.

[box]Restart-Service MSExchangeTransport[/box]

Exchange 2013 – Test Email Relaying from your ‘Allowed IP’

1. Go to the machine you have allowed relaying from, and attempt to ‘relay’ mail. In the example below I’m attempting to send an email to test@relay.com. In the first example we cannot relay, so something has been misconfigured.

2. However this time we CAN relay so our connector is configured properly.

 

Related Articles, References, Credits, or External Links

NA

Exchange 2010 Install Error – ‘Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server’

KB ID 0000577 

Problem

I had a nice clean install on a greenfield site today, Exchange 2010 Standard c/w SP1 on Server 2008 R2, so I was not happy when this happened!

Error:
The following error was generated when “$error.Clear();
if ($RoleStartTransportService)
{
start-SetupService -ServiceName MSExchangeTransport
}
” was run: “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”.

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

Solution

A quick google on this error, turned up loads of posts that said, “This is because you’ve disabled (Unticked) IPv6 on the properties of the nerwork card”, like so;

However as you can see, mine had NOT BEEN DISABLED

Every post and answer that had been accepted said either, retick this box, or manually start the Microsoft Exchange Transport service, this also failed. Turns out the problem WAS related to IPv6, This server was multi homed (I don’t know if that’s relavant).

What Fixed it for me:

1. On the Exchange server, Start >In the Search/Run box type regedit {Enter}.

2. Navigate to:

[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Tcpip6 > Parameters [/box]

Create a new 32 BIT DWORD value called “DisabledComponents”, and set its value to 0xffffffff (Hexadecimal) or 4294967295 (Decimal).

3. Finally locate the server’s hosts file (C:WindowsSystem32Driversetchosts) and make sure if there is an IPv6 entry for ::1 it has been commented out (i.e. the line has a hash symbol at the start of it).

 

Related Articles, References, Credits, or External Links

NA