Exchange Hub Queue database renamed

Alert we are receiving like this[Transport Mail Database: MSExchangeTransport has detected a critical storage error but failed to complete the desired recovery action on Move due to error Cannot
move source directory: D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue to destination directory: D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\Queue.old
Please respond and share your thought.
Regards
Mihir

This is the automatic transport database recovery feature in exchange 2010
When a fatal/permanent JET exception (logical corruption) has appeared in the database, the feature will be triggered so that the queue, log and
system folders are moved (add .OLD to path), a warning event will be fired to inform administrator that the transport database folders have been moved. After that, worker process will be restarted, and then try to attach a new database
If the transport component can’t move the old folder, the possible cause is that the target folder has already existed as the “Move”
action will only perform once, the subsequent recovery action will fail along with event 17104 until the previous queue database backup has been renamed or deleted
You can see the entire recovery procedure in event 17102
If you want to stop this feature, please set the value of the “QueueDatabaseRecoveryAction” key to “None” in transport application
config file:
C:\Program Files\Microsoft\Exchange Server\Bin\EdgeTransport.exe.config
<add key="QueueDatabaseRecoveryAction" value="None" />
Notes: The default setting is “Move”
Notes: After you stop the feature, transport service won’t
try to recover the queue if the corruption happens again. It’ll just log the error event in the application log and stop the transport service. Then, you need to follow the link from Anil to delete the old database, or repair it before the service can
be started again
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

How To reduce Mail Queue Database File?

Hello Team,
I setup exchange server 2013,i check daily mail queue database file increase .
So how to decrease database file?i
Thanks,
Jemin Prajapati

Hi Jim,
While moving old queue, we will loose some mail during this operation.
Can we do this activity without any downtime or without loosing any mail.
Please confirm we only need to move mail.que and rest of other file (log and temp) will remain the same.
What I am thinking how new queue will sync with old logs and other files.
Thanks
Hi
If the new queue work without any problem, we could refer to the following steps:
Use “Net stop MSExchangeTransport” to stop Exchange transport service.
Overwrite all the existing empty queue database files and transaction log files on the target Exchange transport server by using all the files from "C:\QueueRecovery". By default, the queue database and transaction logs exist in C:\Program Files\Microsoft\Exchange
Server\TransportRoles\data\Queue.
A new queue database is created when the Microsoft Exchange Transport service is restarted. This can occur at any time after we have finished copying the queue database files to the target transport server.
Use “ Net pause MXExchangeTransport ” to pause message flow through Hub Server
Use the Queue Viewer or the Get-Queue cmdlet in the Exchange Management Shell to monitor the delivery queues on the target Exchange transport server. Wait until no messages remain in any of delivery queues on the server as indicated by a message count of
0.
Then we use “Net stop MSExchangeTransport” to stop Exchange transport service.
Overwrite all the existing empty queue database files and transaction log files on the target Exchange transport server by using all the files from "C:\QueueRecovery". By default, the queue database and transaction logs exist in C:\Program Files\Microsoft\Exchange
Server\TransportRoles\data\Queue.
Use “Net start MSExchangeTransport” to enable Exchange transport service.
We could refer to the following link to learn more details:
http://technet.microsoft.com/en-us/library/bb124343(v=exchg.80).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

How to get rid of the message Client submission probe stuck in the Exchange Server Queue?

We have Exchange 2013 in Hybrid with Office 365.
How to get rid of the message in the Exchange Server Queue?
Mounting the database fixed it.
Thanks!!!

Mounting the database fixed it.

Exchange 2010 SP1 database size limit?

I have seen several posts concerning exchange 2010 Standard database limit being 50GB but can be increased by modifying the registry. We were migrated from Exchange 2003 to Exchange 2010 by a vendor. My current database is 188.1GB. I searched the registry
for the changes to increase the database form the 50GB limit but it does not look like they made the changes. What has me baffled is how can my database be 188.1 GB if they did not modify the registry?
Thank you,
Cecil

So you only use Database Size Limit in GB registry if you want to hard set the size? From some of the posts I had seen they were saying it was 50 GB by default and could be expanded to 1TB by modifying the registry. I did not understand
why the instructions included modifying the registry if it was not needed. I am by no means trying to dispute it just trying to understand.
Thanks for the reply.
Cecil

JE 5.0.55 and 4.1.21 available, critical fix for Database renaming

All,
I'd like to point out the critical bug fix that has to do with database renaming. This is fixed in JE 5.0.55 and JE 4.1.21. See below.
--mark
Berkeley DB Java Edition 5.0.55
http://www.oracle.com/us/products/database/berkeley-db/index.html (BDB product page)
http://www.oracle.com/technetwork/database/berkeleydb/overview/index.html (BDB overview)
http://www.oracle.com/technetwork/database/berkeleydb/overview/index-093405.html (BDB JE overview)
Berkeley DB Java Edition 5.0.55 is a patch release consisting of fixes for a number of issues. We strongly recommend that users of the 5.0.x version upgrade to this release. These fixes include:
[#21537] Fixed a critical bug that causes a database to be entirely deleted after a crash (or abnormal shutdown, i.e., when not calling Environment.close). The bug occurs when the database is renamed just prior to the crash (or abnormal shutdown). This bug was introduced in JE 5.0.48.
[#21492] Fixed an inefficiency in the Checkpointer which manifests itself as a large amount of time being spent in com.sleepycat.je.recovery.DirtyINMap.removeNextNode() calling java.util.HashMap$HashIterator.remove() calling java.util.HashMap.removeEntryForKey().
[#21106] An enhancement has been made to DbVerify to show a histogram of BIN counts by utilization percentage.This is a sample of the output:
    Verifying database p10
    Checking tree for p10
    BTree: Composition of btree, types and counts of nodes.
            binCount=3,207
            binEntriesHistogram=[40-49%: 3,093; 50-59%: 10; 60-69%: 22; 70-79%: 26;
    80-89%: 21; 90-99%: 35]
            binsByLevel=[level 1: count=3,207]
            deletedLNCount=0
            inCount=49
            insByLevel=[level 2: count=48; level 3: count=1]
            lnCount=209,716
            mainTreeMaxDepth=3Find the complete list of changes in the change log.
http://download.oracle.com/otndocs/products/berkeleydb/html/je/je-5.0.55_changelog.html
Read the detailed product documentation included in the download package or on the web.
http://www.oracle.com/technetwork/database/berkeleydb/downloads/index-098622.html
http://download.oracle.com/docs/cd/E17277_02/html/index.html
Download the source code.
http://download.oracle.com/otn/berkeley-db/je-5.0.55.tar.gz
http://download.oracle.com/otn/berkeley-db/je-5.0.55.zip
http://download.oracle.com/maven/com/sleepycat/je/5.0.55/je-5.0.55.pom
Review the frequently asked questions (FAQs):
http://www.oracle.com/technetwork/database/berkeleydb/je-faq-096044.html
Join OTN and participate in the Berkeley DB JE Support Forum discussions. Our engineering and support staff are highly active on these forums, if you have questions please ask them there first.
Berkeley DB Java Edition
For further information, or questions about licensing and sales of JE, please contact us at:
mailto:[email protected]
Thank you for your support of Berkeley DB Java Edition.

The format change is for BDB Java Edition 5.0 only, and does not apply to other BDB products. It's forward compatible, which means that a BDB JE application using JE 5.0 can use environments written with older versions of JE. However, it's not backwards compatible; once your environment has been opened by JE 5.0, it's been converted to the new format, and can no longer be readable by older versions of JE.
Just for the benefit of others who may not have read the changelog, here's the full text:
JE 5.0.34 has moved to on-disk file format 8.
The change is forward compatible in that JE files created with release 4.1 and earlier can be read when opened with JE 5.0.34. The change is not backward compatible in that files created with JE 5.0 cannot be read by earlier releases. Note that if an existing environment is opened read/write, a new log file is written by JE 5.0 and the environment can no longer be read by earlier releases.
There are two important notes about the file format change.
The file format change enabled significant improvements in the operation performance, memory and disk footprint, and concurrency of databases with duplicate keys. Environments which contain databases with duplicate keys must run an upgrade utility before opening an environment with this release. See the Performance section for more information.
An application which uses JE replication may not upgrade directly from JE 4.0 to JE 5.0. Instead, the upgrade must be done from JE 4.0 to JE 4.1 and then to JE 5.0. Applications already at JE 4.1 are not affected. Upgrade guidance can be found in the new chapter, "Upgrading a JE Replication Group", in the "Getting Started with BDB JE High Availability" guide.I may not have fully understood your question, so let us know if that doesn't answer it.
Edited by: Linda Lee on Dec 1, 2011 10:41 AM

Exchange User Mailbox Database Group Lookup Reconciliation-parameters

Hi everyone,
I want to execute Exchange User Mailbox Database Group Lookup Reconciliation.
Parameters :
Code Key Attribute : __NAME__ (default)
Decode Attribute : __NAME__ (default)
IT Resource Name : Exchange IT Resource
Lookup Name : Lookup.Exchange.MailboxDatabase (default)
Object Type : __MAILBOXDATABASE__ (default)
Resource Object Name : Exchange User
Is there any incorrect parameter?
Thanks.
Best Regards.

Everything looks correct, all parameters have been provided correctly. Check values in "Exchange IT Resource" before executing scheduler.

During daily refresh/clone alter database rename file genrating logs under $ORACLE_HOME/dbs with name c-1437102747-20130920-16

Did anyone have seen this behavior?
DB version : 11.1.0.7
OS : HP-UX Itanum
EBS -11.5.10.2
We are doing daily refresh/clone of a database instance from production. Recently we are seeing the growth of $ORACLE_HOME/dbs directory during this
refresh.   During investigation we find out that
1) When we rename the database files after database restoration. Each below command genrating the 24MB of log file under $ORACLE_HOME/dbs.
Command :
alter database rename file '/db02/prod/XDB.dbf' to '/db02/test/XDB.dbf';
alter database rename file '/db02/prod/a_archive01.dbf' to '/db02/test/a_archive01.dbf';
Logfiles under $ORACLE_HOME/dbs on target :
-rw-r----- xxxxx 24379392 Sep 20 05:30 ./dbs/c-1437102747-20130920-02
-rw-r----- xxxxx 24379392 Sep 20 05:30 ./dbs/c-1437102747-20130920-03
2) After few minutes, these logs got removed from the directory.
3) Did not find anything unusual in the alert log.

These are controlfile autobackups.   Every time you make a physical change to the database structure, an autobackup is created. In 11.2, the frequency is reduced -- for example if you make 5 changes in quick succession, one autobackup is created.
CONTROLFILE AUTOBACKUP ON    would be visible when you do a SHOW ALL in rman.
Hemant K Chitale

Exchange 2010 Slow Database Mount Time - Almost 1 Hour

Hello -
We have 2 DAG nodes on the production site running EX2010 SP3 RU6
In preparation for Windows patching I moved the active copy of DB2 active from EX2 to EX1, this took approx 20 seconds as per usual
Patching happened, and EX2 got a reboot
Later that evening I moved the active copy of DB2 back from EX1 to EX2
The move took 59 minutes and 32 seconds
During which time the DB status showed as mounting on EX2 and mailboxes where inaccessible [luckily this was out of hours]
The DB is 185 GB with 4 GB of logs at that time
There weren't ESE events related to playing transaction logs
There have been ESE 629 events in the log for a while showing... "While attempting to move to the next or previous node in a B-Tree, the database skipped over 25583 non-visible nodes in 73 pages... The database may benefit from widening the online maintenance
window..." but these warnings show up really quickly on our site even with a new database
We also have a problem that emerged approx 2 weeks ago where CPU runs at 100% for prolonged periods [mainly store.exe for 10/20/30 mins] and people get slow response times in Outlook, it's running on 4 x vCPU's and 18 GB RAM
Could the really slow mount time be related to DB corruption?
Thanks

Thanks for the feedback
This is not related to a dirty shutdown
According to Get-MailboxDatabaseCopyStatus etc all DB copies are healthy
I tested the DB activation again last night
Mailbox Database 2 is normally active on EX2
So we made the copy on EX1 active [server is on the same network] and this took 3 secs
When it came to making the same DB active on EX2 again it took 1 hr 46 mins 34 seconds!
We ran the task from EMC and the GUI did not hang, all the while it kept counting the hours, minutes & seconds
During this time mailboxes were unavailable, and the DB status showed as Mounting in EMC
From the Event Log, when ESE event 326 is finally logged there are some timings…
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.031, [4] 0.000, [5] 0.000, [6] 0.094, [7] 0.000, [8] 6386.578,
[9] 0.016, [10] 0.000, [11] 0.000, [12] 0.047.
And step 8 [whatever that is] took 6386 seconds while everything else flew
Of the 2 other Mailbox DB’s… DB1 took 7 seconds to activate on EX2 and DB3 took 32 minutes 41 seconds
Any ideas what is going on?
Thanks
Log Name:      Application
Source:        MSExchangeRepl
Date:          12/08/2014 21:02:02
Event ID:      2090
Task Category: Action
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Database: Mailbox Database 2\EX2
Mailbox server:
EX2.company.com
A failover or switchover occurred. Database Mailbox Database 2\EX2 will be
mounted with no data loss.
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          12/08/2014 21:02:05
Event ID:      9539
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
The Microsoft Exchange Information Store database "c21e43b5-feb8-4bde-a993-aca830cd71a3: /o=Company X/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=xxx.company.com/cn=Microsoft
Private MDB" was stopped.
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          12/08/2014 21:02:05
Event ID:      1000
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Attempting to start the Information Store "Mailbox Database 2".
Log Name:      Application
Source:        ESE
Date:          12/08/2014 21:02:05
Event ID:      102
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine (14.03.0162.0000) is starting a new instance (4).
Log Name:      Application
Source:        ESE
Date:          12/08/2014 21:02:06
Event ID:      105
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine started a new instance (4). (Time=0 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.109, [4] 0.079, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.219, [10] 0.000, [11] 0.000.
Log Name:      Application
Source:        ESE
Date:          12/08/2014 22:48:33
Event ID:      326
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine attached a database (4, X:\Database\Mailbox Database 2\Mailbox Database 2.edb). (Time=6386 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.031, [4] 0.000, [5] 0.000, [6] 0.094, [7] 0.000, [8] 6386.578, [9] 0.016, [10] 0.000, [11] 0.000, [12] 0.047.
Saved Cache: 1

Cisco 5 with Exchange 2010 and Database Availability Groups

Hi,
Unity 5 was installed a long time. Recently installed with the latest ES88 to the system. The fact is we have Exchange 2007 (clustered) mailbox server in the network environment, and introduced the Exchange 2010 (with DAG activated).
So far we didn't do any "re-partnering" from the Exchange 2007 to Exchange 2010. The end users are working fine by leaving voice message and can retreive their voice without too much issue, no matter where the End Users account are located, Exchange 2007 or Exchange 2010.
But lately, there was some actions taken in the Exchange environment. Some Exchange 2010 mailstore databases in one of the Exchange 2010 server, with DAG has been activated.
In this case, we are now unable to leave any voice messages to the end usrs. All the voice messages are now being held in C:\CommServer\UnityMTA.
Want to ask, does Unity 5 and Exchange 2010 compatible with DAG? Also, is that my problem is caused by re-partnering server not taken place? If yes, which Exchange 2010 mailbox database server I should point to? Reason is, there will have 3 physical servers, and with several DB mailstore, if I select one of the physical server, and one of the D mailstore, will this be affected when the DAG is activated?
Thanks
Timothy

Hi Yancy,
If you're referring to integrating Microsoft Exchange 2010 with Cisco Unified Communications Manager (CUCM) 5.x for voicemail purposes, via a SIP Trunk, then you could certainly have a go at it (a Media Termination Point would be required and the codec would be G.711). However, I'm not aware of anyone having properly tested it with CUCM 5.x; given that it's not having software maintenance releases written for it anymore. CUCM 5.0 stopped having software maintenance releases written for it in June 2009, and CUCM 5.1 in February this year.
The following Tech Tip is likely to assist:
https://supportforums.cisco.com/docs/DOC-12544
Kind regards,
Craig

Difference between database rename and refresh

can any bodt tell the exact difference between database rename and refresh and the procedures between the both?

Oh
Rename--- as the name itself says rename the DB
your id is user583972
rename=change the user583972 to your NAME
Refresh=Copy from production and replicate in QA/DEV/TEST for the same purposes

"Message Queued for submission" performance counter high for Exchange Server 2010 Database

Hi,
We are receiving SCOM Alert as "Mail Submission service is experiencing issue: Messages Queued for Submission-sustained for 15 mins-RED (>25)".
After checking the "Messages queued for Submission" counter on the repective server it was found that the value is 66 but when we check the queue viewer we dont observe any messages stuck in Submission queue.
Would like to know what aspects can be checked here, in order to troubleshoot the issue?
The counter shows 0 value in perfmon for all other mailbox databases.
Thanks & Regards.

Hi,
This is a known issue with Exchange Server 2007 and Exchange Server 2010. We do not recommend that you use this counter for health alerts.
I recommend you refer to the following article:
http://support.microsoft.com/kb/2921142/en-us
It is caused by the MailSubmission service submits a message for delivery multiple times, the counter is incremented two times but decremented only one time. This situation can leave the counter with a positive value even though there
is no message in the queue. When you restart the service, the counter is reset.
Here is an similar thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/c9b485a5-ef0e-4b9a-851e-28c4a4c0606a/msexchangeis-mailbox-messages-queued-for-submission-keeps-increasing?forum=exchangesvradminlegacy
Thanks.
Niko Cheng
TechNet Community Support

Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Mounted

Good Morning everyone!!!
I Have SCOM 2007 R2 CU5 Envoirnment and i am monitoring Microsoft Exchange 2010 SP1 Messaging infrastracture,
I have Microsoft Exchange 2010 SP1 Monitoring MP, MP version is 14.2.71.0.
Case:-
When exchange is having issue with DAG, SCOM monitoring rule:- KHI: The database copy is not mounted on the local server. Another database copy may be mounted on a different server.
is generating the alert but alert Description is only " _ef4a8515_1cc0_48a9_aa12_92ba059a6eae_ " and rest of the things are blank
and because of this ticketing team is unable to process these alerts,
Impact:-
Whenever DAG is unavailable, messaging team is not getting notification and because of this. Exchange services are failing down,
Does anyone having this kind of issues on their exchange environment?
I am looking solution for this issue, please let me know if anyone is aware about this.
Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
your question. This can be beneficial to other community members reading the thread.

Does anyone has updated information regarding Exchange 2010 DAG monitoring fix, <o:p></o:p>
As i see there was exchange MP release on 31st Aug 2012
ID
Name
Targets
_ef4a8515_1cc0_48a9_aa12_92ba059a6eae_
KHI: The database copy is not mounted on the local server. Another database copy may be mounted on a different server.
Root Management Server
_EF51D339_22C5_49b3_8B6B_25002BE31D4A_
KHI: Retry Mailbox Delivery Queue Length - sustained for 90 minutes - Red(>1) - Hub Transport.
Root Management Server
_93558cf0_e063_45b1_b57a_0d4b53e0d615_
KHI: The Microsoft Exchange Information Store service (MSExchangeIS) isn't running.
Root Management Server
My monitoring is affected for these rules which i mentioned below, here alerts
information is shown as rule ID instead of Rule name. and we don’t get alert description
for above rules when the generate alerts.<o:p></o:p>
Response would be appreciated <o:p></o:p>
Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
your question. This can be beneficial to other community members reading the thread.

Mail only get delivered every 15 min From Exchange 2013 queue

I have a newly installed Exchange 2013 SP1 on server 2012. I have notice that when I get mail all the mail have the same time Stamp. I use the queue viewer and notice that mail are stuck in the SMTP delivery service. I restart the transport service and
the mail got delivered. this has now become an un going problem. I have to restart the transport service or wait every 15 min to get mail delivered. I am stuck can I get so help.

Hi,
Before going further, I recommend you check your connection log to find the root cause:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\Connectivity
For the event 6002 error, you can build a new database and check if the new warning event also indicates the new one:
If you have any question, please feel free to let me know.
I look at the log here is a copy I see some attempt to connect and failures. how do I address these Issues
#Software: Microsoft Exchange Server
#Version: 15.0.0.0
#Log-type: Transport Connectivity Log
#Date: 2014-04-24T00:00:44.596Z
#Fields: date-time,session,source,Destination,direction,description
2014-04-24T00:00:41.024Z,08D12C89C3C82025,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T00:00:41.024Z,08D12C89C3C82025,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T00:00:41.024Z,08D12C89C3C82025,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T00:00:41.273Z,08D12C89C3C82025,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T00:01:01.880Z,08D12C89C3C82026,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T00:01:13.658Z,08D12C89C3C82026,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T00:01:34.702Z,08D12C89C3C82026,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:14|NextRetryTime:2014-04-24T00:11:34.702Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:14|NextRetryTime:2014-04-24T00:11:34.702Z]
2014-04-24T00:01:34.702Z,08D12C89C3C82026,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T00:05:41.177Z,08D12C89C3C82028,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T00:05:46.824Z,08D12C89C3C82028,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T00:05:46.824Z,08D12C89C3C82028,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T00:05:47.027Z,08D12C89C3C82028,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T00:10:41.283Z,08D12C89C3C8202B,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T00:10:41.299Z,08D12C89C3C8202B,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T00:10:41.299Z,08D12C89C3C8202B,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T00:10:41.501Z,08D12C89C3C8202B,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T00:11:34.696Z,08D12C89C3C82045,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T00:11:34.696Z,08D12C89C3C82045,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T00:11:55.725Z,08D12C89C3C82045,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:15|NextRetryTime:2014-04-24T00:21:55.725Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:15|NextRetryTime:2014-04-24T00:21:55.725Z]
2014-04-24T00:11:55.725Z,08D12C89C3C82045,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T00:15:41.576Z,08D12C89C3C82047,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T00:15:41.951Z,08D12C89C3C82047,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T00:15:41.951Z,08D12C89C3C82047,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T00:15:42.154Z,08D12C89C3C82047,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T00:21:55.719Z,08D12C89C3C8204A,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T00:22:14.251Z,08D12C89C3C8204A,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T00:22:35.279Z,08D12C89C3C8204A,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:16|NextRetryTime:2014-04-24T00:32:35.279Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:16|NextRetryTime:2014-04-24T00:32:35.279Z]
2014-04-24T00:22:35.279Z,08D12C89C3C8204A,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T00:32:35.273Z,08D12C89C3C8204D,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T00:32:54.055Z,08D12C89C3C8204D,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T00:33:15.084Z,08D12C89C3C8204D,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:17|NextRetryTime:2014-04-24T00:43:15.084Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:17|NextRetryTime:2014-04-24T00:43:15.084Z]
2014-04-24T00:33:15.084Z,08D12C89C3C8204D,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T00:43:15.078Z,08D12C89C3C82050,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T00:43:32.893Z,08D12C89C3C82050,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T00:43:53.921Z,08D12C89C3C82050,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:18|NextRetryTime:2014-04-24T00:53:53.921Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:18|NextRetryTime:2014-04-24T00:53:53.921Z]
2014-04-24T00:43:53.921Z,08D12C89C3C82050,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T00:53:53.915Z,08D12C89C3C82053,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T00:54:11.699Z,08D12C89C3C82053,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T00:54:32.727Z,08D12C89C3C82053,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:19|NextRetryTime:2014-04-24T01:04:32.727Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:19|NextRetryTime:2014-04-24T01:04:32.727Z]
2014-04-24T00:54:32.727Z,08D12C89C3C82053,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T01:04:32.721Z,08D12C89C3C82054,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T01:05:02.828Z,08D12C89C3C82054,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T01:05:23.857Z,08D12C89C3C82054,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:20|NextRetryTime:2014-04-24T01:15:23.857Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:20|NextRetryTime:2014-04-24T01:15:23.857Z]
2014-04-24T01:05:23.857Z,08D12C89C3C82054,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T01:15:23.851Z,08D12C89C3C82055,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T01:15:29.685Z,08D12C89C3C82055,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T01:15:50.713Z,08D12C89C3C82055,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:21|NextRetryTime:2014-04-24T01:25:50.713Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:21|NextRetryTime:2014-04-24T01:25:50.713Z]
2014-04-24T01:15:50.713Z,08D12C89C3C82055,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T01:25:50.707Z,08D12C89C3C82056,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T01:26:03.203Z,08D12C89C3C82056,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T01:26:24.231Z,08D12C89C3C82056,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:22|NextRetryTime:2014-04-24T01:36:24.231Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:22|NextRetryTime:2014-04-24T01:36:24.231Z]
2014-04-24T01:26:24.231Z,08D12C89C3C82056,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T01:36:24.225Z,08D12C89C3C82057,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T01:36:43.132Z,08D12C89C3C82057,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T01:37:04.176Z,08D12C89C3C82057,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:23|NextRetryTime:2014-04-24T01:47:04.176Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:23|NextRetryTime:2014-04-24T01:47:04.176Z]
2014-04-24T01:37:04.176Z,08D12C89C3C82057,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T01:47:04.170Z,08D12C89C3C82058,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T01:47:04.201Z,08D12C89C3C82058,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T01:47:25.229Z,08D12C89C3C82058,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:24|NextRetryTime:2014-04-24T01:57:25.229Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:24|NextRetryTime:2014-04-24T01:57:25.229Z]
2014-04-24T01:47:25.229Z,08D12C89C3C82058,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T01:57:25.223Z,08D12C89C3C82066,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T01:57:37.485Z,08D12C89C3C82066,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T01:57:58.513Z,08D12C89C3C82066,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:25|NextRetryTime:2014-04-24T02:07:58.513Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:25|NextRetryTime:2014-04-24T02:07:58.513Z]
2014-04-24T01:57:58.513Z,08D12C89C3C82066,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T02:07:58.507Z,08D12C89C3C82069,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T02:07:58.647Z,08D12C89C3C82069,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T02:08:19.691Z,08D12C89C3C82069,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:26|NextRetryTime:2014-04-24T02:18:19.691Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:26|NextRetryTime:2014-04-24T02:18:19.691Z]
2014-04-24T02:08:19.691Z,08D12C89C3C82069,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T02:18:19.685Z,08D12C89C3C8206C,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T02:18:38.109Z,08D12C89C3C8206C,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T02:18:59.137Z,08D12C89C3C8206C,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:27|NextRetryTime:2014-04-24T02:28:59.137Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:27|NextRetryTime:2014-04-24T02:28:59.137Z]
2014-04-24T02:18:59.137Z,08D12C89C3C8206C,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T02:20:49.193Z,08D12C89C3C8206F,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:20:49.333Z,08D12C89C3C8206F,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:20:49.333Z,08D12C89C3C8206F,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:20:49.567Z,08D12C89C3C8206F,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:25:43.262Z,08D12C89C3C82072,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:25:43.277Z,08D12C89C3C82072,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:25:43.277Z,08D12C89C3C82072,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:25:43.480Z,08D12C89C3C82072,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:28:59.131Z,08D12C89C3C82075,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T02:29:10.628Z,08D12C89C3C82075,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T02:29:31.656Z,08D12C89C3C82075,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:28|NextRetryTime:2014-04-24T02:39:31.656Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:28|NextRetryTime:2014-04-24T02:39:31.656Z]
2014-04-24T02:29:31.656Z,08D12C89C3C82075,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T02:30:03.370Z,08D12C89C3C82076,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:30:15.507Z,08D12C89C3C82076,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:30:15.507Z,08D12C89C3C82076,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:30:15.772Z,08D12C89C3C82076,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 108649 ()
2014-04-24T02:30:43.321Z,08D12C89C3C82078,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:30:43.321Z,08D12C89C3C82078,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:30:43.321Z,08D12C89C3C82078,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:30:43.524Z,08D12C89C3C82078,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:35:55.486Z,08D12C89C3C8207C,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:36:01.273Z,08D12C89C3C8207C,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:36:01.273Z,08D12C89C3C8207C,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:36:01.585Z,08D12C89C3C8207C,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:39:31.650Z,08D12C89C3C8207D,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T02:39:49.028Z,08D12C89C3C8207D,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T02:40:10.057Z,08D12C89C3C8207D,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:29|NextRetryTime:2014-04-24T02:50:10.057Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:29|NextRetryTime:2014-04-24T02:50:10.057Z]
2014-04-24T02:40:10.057Z,08D12C89C3C8207D,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T02:40:43.565Z,08D12C89C3C8207F,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:40:43.580Z,08D12C89C3C8207F,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:40:43.580Z,08D12C89C3C8207F,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:40:43.814Z,08D12C89C3C8207F,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:45:43.765Z,08D12C89C3C82083,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:45:43.780Z,08D12C89C3C82083,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:45:43.796Z,08D12C89C3C82083,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:45:44.030Z,08D12C89C3C82083,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:50:10.051Z,08D12C89C3C82085,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T02:50:28.006Z,08D12C89C3C82085,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T02:50:43.918Z,08D12C89C3C82087,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:50:43.964Z,08D12C89C3C82087,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:50:43.964Z,08D12C89C3C82087,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:50:44.167Z,08D12C89C3C82087,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:50:49.019Z,08D12C89C3C82085,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:30|NextRetryTime:2014-04-24T03:00:49.019Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:30|NextRetryTime:2014-04-24T03:00:49.019Z]
2014-04-24T02:50:49.019Z,08D12C89C3C82085,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T02:55:43.883Z,08D12C89C3C8208A,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:55:43.899Z,08D12C89C3C8208A,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:55:43.899Z,08D12C89C3C8208A,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:55:44.133Z,08D12C89C3C8208A,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T02:56:13.648Z,08D12C89C3C8208D,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T02:56:31.993Z,08D12C89C3C8208D,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T02:56:31.993Z,08D12C89C3C8208D,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T02:56:32.258Z,08D12C89C3C8208D,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 36581 ()
2014-04-24T03:00:43.974Z,08D12C89C3C8208F,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T03:00:43.974Z,08D12C89C3C8208F,SMTP,mailbox database 1255358834,>,Xchngsvr
2014-04-24T03:00:43.974Z,08D12C89C3C8208F,SMTP,mailbox database 1255358834,>,Established connection to Xchngsvr
2014-04-24T03:00:44.224Z,08D12C89C3C8208F,SMTP,mailbox database 1255358834,-,Messages: 1 Bytes: 19600 ()
2014-04-24T03:00:49.013Z,08D12C89C3C82091,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T03:00:49.013Z,08D12C89C3C82091,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T03:01:10.041Z,08D12C89C3C82091,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:31|NextRetryTime:2014-04-24T03:11:10.041Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:31|NextRetryTime:2014-04-24T03:11:10.041Z]
2014-04-24T03:01:10.041Z,08D12C89C3C82091,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:05:44.002Z,08D12C89C3C82094,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T03:05:44.065Z,08D12C89C3C82094,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:05:45.079Z,08D12C89C3C82094,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:1|NextRetryTime:2014-04-24T03:06:45.079Z]
2014-04-24T03:05:45.079Z,08D12C89C3C82094,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:05:48.308Z,08D12C89C3C82095,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=1;RN=1;
2014-04-24T03:05:48.308Z,08D12C89C3C82095,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:05:49.353Z,08D12C89C3C82095,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:1|NextRetryTime:2014-04-24T03:06:45.079Z]
2014-04-24T03:05:49.353Z,08D12C89C3C82095,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:10:49.350Z,08D12C89C3C82097,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=3;RN=3;
2014-04-24T03:10:49.381Z,08D12C89C3C82097,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:10:50.411Z,08D12C89C3C82097,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:2|NextRetryTime:2014-04-24T03:11:50.411Z]
2014-04-24T03:10:50.411Z,08D12C89C3C82097,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:11:10.035Z,08D12C89C3C82098,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T03:11:15.963Z,08D12C89C3C82098,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T03:11:36.976Z,08D12C89C3C82098,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:32|NextRetryTime:2014-04-24T03:21:36.976Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:32|NextRetryTime:2014-04-24T03:21:36.976Z]
2014-04-24T03:11:36.976Z,08D12C89C3C82098,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:15:50.408Z,08D12C89C3C8209A,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=4;RN=4;
2014-04-24T03:15:50.408Z,08D12C89C3C8209A,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:15:51.422Z,08D12C89C3C8209A,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:3|NextRetryTime:2014-04-24T03:16:51.422Z]
2014-04-24T03:15:51.422Z,08D12C89C3C8209A,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:20:51.419Z,08D12C89C3C8209D,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=5;RN=5;
2014-04-24T03:20:57.471Z,08D12C89C3C8209D,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:20:58.470Z,08D12C89C3C8209D,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:4|NextRetryTime:2014-04-24T03:21:58.470Z]
2014-04-24T03:20:58.470Z,08D12C89C3C8209D,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:21:36.970Z,08D12C89C3C8209E,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T03:21:54.941Z,08D12C89C3C8209E,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T03:22:15.969Z,08D12C89C3C8209E,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:33|NextRetryTime:2014-04-24T03:32:15.969Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:33|NextRetryTime:2014-04-24T03:32:15.969Z]
2014-04-24T03:22:15.969Z,08D12C89C3C8209E,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:25:58.467Z,08D12C89C3C8209F,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=5;RN=5;
2014-04-24T03:26:04.707Z,08D12C89C3C8209F,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:26:05.721Z,08D12C89C3C8209F,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:5|NextRetryTime:2014-04-24T03:31:05.721Z]
2014-04-24T03:26:05.721Z,08D12C89C3C8209F,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:31:05.718Z,08D12C89C3C820A3,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=7;RN=7;
2014-04-24T03:31:05.733Z,08D12C89C3C820A3,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:31:06.763Z,08D12C89C3C820A3,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:6|NextRetryTime:2014-04-24T03:36:06.763Z]
2014-04-24T03:31:06.763Z,08D12C89C3C820A3,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:32:15.963Z,08D12C89C3C820A4,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T03:32:28.006Z,08D12C89C3C820A4,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T03:32:49.034Z,08D12C89C3C820A4,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:34|NextRetryTime:2014-04-24T03:42:49.034Z][TargetIPAddress:198.46.135.216:25|MarkedUnhealthy|FailureCount:34|NextRetryTime:2014-04-24T03:42:49.034Z]
2014-04-24T03:32:49.034Z,08D12C89C3C820A4,SMTP,browseviewsingle.us,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:36:06.760Z,08D12C89C3C820A6,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=8;RN=8;
2014-04-24T03:36:19.193Z,08D12C89C3C820A6,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:36:20.222Z,08D12C89C3C820A6,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:7|NextRetryTime:2014-04-24T03:41:20.222Z]
2014-04-24T03:36:20.222Z,08D12C89C3C820A6,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:41:20.219Z,08D12C89C3C820A9,SMTP,mailbox database 1255358834,+,SmtpDeliveryToMailbox e3aa8b34-f225-43c6-9563-a87898a284c6;QueueLength=TQ=9;RN=9;
2014-04-24T03:41:26.428Z,08D12C89C3C820A9,SMTP,mailbox database 1255358834,>,Xchngsvr[173.221.30.34]
2014-04-24T03:41:27.442Z,08D12C89C3C820A9,SMTP,mailbox database 1255358834,>,Failed connection to 173.221.30.34:475 (ConnectionRefused:0000274D)[TargetHost:Xchngsvr:475|NotMarkedUnhealthy|ActiveConnectionCount:2][TargetIPAddress:173.221.30.34:475|MarkedUnhealthy|FailureCount:8|NextRetryTime:2014-04-24T03:46:27.442Z]
2014-04-24T03:41:27.442Z,08D12C89C3C820A9,SMTP,mailbox database 1255358834,-,Messages: 0 Bytes: 0 (Retry : Unable to connect)
2014-04-24T03:42:49.028Z,08D12C89C3C820AA,SMTP,browseviewsingle.us,+,DnsConnectorDelivery 807c71be-93cd-407f-bd57-eb0baf9809b3;QueueLength=TQ=1;RN=1;
2014-04-24T03:43:06.934Z,08D12C89C3C820AA,SMTP,browseviewsingle.us,>,browseviewsingle.us[198.46.135.216]
2014-04-24T03:43:27.963Z,08D12C89C3C820AA,SMTP,browseviewsingle.us,>,Failed connection to 198.46.135.216:25 (TimedOut:0000274C)[TargetHost:browseviewsingle.us:25|MarkedUnhealthy|FailureCount:35|NextRetryTime:2014-04-24T03:53:27.963Z

Reseed one Exchange 2013 server databases housing 15 mailbox databases (mailboxes) - NO DAG

I have one exchange server with fourteen server databases. One these server databases is housing 15 mailbox databases (user mailboxes databases) of these fifteen mailbox DB's all have the same search problem in both the inbox and
sent items. They all have the problem in outlook 2010 on their desktop and in Outlook Web APP - Everything I read refers to suggests a reseed of the database, since its effecting all 15 mailboxes in one server database I'm thinking I have to reseed
the one server database a DAG copy - again everything I read refers to a copy /DAG - I don't have a DAG.
I need to reseed this Exchange server database:
This one shows me how I can reseed mailbox database
https://technet.microsoft.com/en-us/library/ee633475(v=exchg.150).aspx
WHILE
http://exchangeserverpro.com/how-to-reseed-a-failed-database-copy-in-exchange-server-2013/
Shows me how to reseed a Copy of Exchange server database using EAC
I have never done either before - so I'm hoping someone can point me in the right direction
Thanks
rjm3rd

Hi,
If you don't have DAG, you need to follow the steps below to rebuild content index.
1. Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.
2. Delete, move, or rename the folder that contains the Exchange content index catalog.
3. Restart the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.
Best regards,
Belinda Ma
TechNet Community Support

New mailbox move request Exchange 2010 : queued

I have deployed new Exchange 2010 server in Exchange 2003 Organization. It is simple setup one Exchange 2003 and New Exchange 2010.
I was trying to move mailbox from Exchange 2003 to 2010 and it has status of QUEUE “indefinetly”.. I have tried several mailboxes and result is the same.
Then I decided to create new database on Exchange 2010 sever. I have crate new mailbox on Exchange 2010 sever, send and receive some emails. And then try to move mailbox to new database. Same results.
I run test MSR replication and is ok.
I have increase msr LOGGING TO Maximum, no errors. I have rebooted server several times, no differences…

Hi,
Based on the description, status of mailbox move request from Exchange 2003 to Exchange 2010 is "indefinitely".
Please make sure mailbox databases in Exchange 2010 and Exchange 2003 are mounted.
Have you moved mailbox using the New-MoveRequest with the BadItemLimit and the AcceptLargeDataLoss parameters? If not, it's worth to do it again. Before you create a new move request, please check if there is any previous move request. If there is, please
clear the previous move request and then move the mailbox.
If the issue persists, please try to move mailbox to another database in Exchange 2003 and then move to Exchange 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange Hub Queue database renamed

Similar Messages

Maybe you are looking for