Dataguard Log Transport Services Warning

Please, explain me. What mind Warning on Primary Server
SELECT a.facility, a.severity, a.ERROR_CODE, a.MESSAGE
FROM v_$dataguard_status a
where a.facility = 'Log Transport Services'
and a.severity = 'Warning';
result
FACILITY SEVERITY ERROR_CODE
MESSAGE
Log Transport Services Warning 0
LNS: Standby redo logfile selected for thread 1 sequence 136 for destination LOG_ARCHIVE_DEST_2
Log Transport Services Warning 0
ARC0: Standby redo logfile selected for thread 1 sequence 135 for destination LOG_ARCHIVE_DEST_2

In alertlog on Primary only message like :
Fri Jun 20 16:08:11 2008
LNS: Standby redo logfile selected for thread 1 sequence 146 for destination LOG_ARCHIVE_DEST_2
Fri Jun 20 16:08:12 2008
Thread 1 advanced to log sequence 147 (LGWR switch)
Current log# 3 seq# 147 mem# 0: /ora/oradata/testmain/redo31.log
Current log# 3 seq# 147 mem# 1: /ora/oradata/testmain/redo32.log
Fri Jun 20 16:08:12 2008
LNS: Standby redo logfile selected for thread 1 sequence 147 for destination LOG_ARCHIVE_DEST_2
Fri Jun 20 16:08:13 2008
Thread 1 advanced to log sequence 148 (LGWR switch)
Current log# 1 seq# 148 mem# 0: /ora/oradata/testmain/redo11.log
Current log# 1 seq# 148 mem# 1: /ora/oradata/testmain/redo12.log
and alert log Standby like:
Fri Jun 20 16:06:29 2008
Recovery of Online Redo Log: Thread 1 Group 5 Seq 145 Reading mem 0
Mem# 0: /ora/oradata/maintest/redo51std.log
Mem# 1: /ora/oradata/maintest/redo52std.log
Fri Jun 20 16:08:11 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[1]: Successfully opened standby log 4: '/ora/oradata/maintest/redo41std.log'
Fri Jun 20 16:08:11 2008
Media Recovery Waiting for thread 1 sequence 146 (in transit)
Fri Jun 20 16:08:11 2008
Recovery of Online Redo Log: Thread 1 Group 4 Seq 146 Reading mem 0
Mem# 0: /ora/oradata/maintest/redo41std.log
Mem# 1: /ora/oradata/maintest/redo42std.log
I think that all work property. But I do not understand why message Warning?

Similar Messages

  • V$DATAGUARD_STATUS - Log Transport Services Warning

    Hello gurus,
    OS read hat, oracle enterprise edition 11g release 2, dataguard 2 physical standby's
    everything works fine but since 1 day we get following warnings from dataguard on the primary server:
    SELECT * FROM V$DATAGUARD_STATUS;
    FACILITY          SEVERITY     DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAM
    MESSAGE
    Log Transport Services     Warning          0 309911     0 NO 01.11.12
    RTC returned 2, disabling RTC for next 2 I/Os.
    does anybody know this warning message?
    in the alert log it looks like this:
    RTC returned 2, disabling RTC for next 2 I/Os.
    Thu Nov 01 12:09:46 2012
    RTC returned 2, disabling RTC for next 2 I/Os.
    Re-enabling RTC following backoff interval 2.
    Re-enabling RTC following backoff interval 2.
    RTC returned 2, disabling RTC for next 2 I/Os.
    RTC returned 2, disabling RTC for next 2 I/Os.
    Re-enabling RTC following backoff interval 2.
    Re-enabling RTC following backoff interval 2.
    Thu Nov 01 12:11:16 2012
    RTC returned 2, disabling RTC for next 2 I/Os.
    Re-enabling RTC following backoff interval 2.
    thanks in advance

    Hello;
    It might be this :
    Bug 9869401 - Unwanted ".. RTC .." messages in alert log if COMPRESSION enabled on LOG_ARCHIVE_DEST_n [ID 9869401.8]
    Best Regards
    mseberg

  • Dataguard : redo transport service

    Hi,
    I have a question regarding dataguard: I have a primary database (oracle 10.2.0.4 win 2003 x64 R2 SP2) communicating with a standby and everything was working like a charm up to the moment where the primary starts creating a lot of session with the user PUBLIC on the standby.... At the end, the standby exceeded the maximum processes and the redo transport service stopped.
    So I stopped/restart the standby and as soon as the primary sees the standby, there are 7 sessions with user PUBLIC that are created. Then few seconds, after another one was created and another one and it stoppes at 9 this time.
    I would like to know what drives the creation of a new session and what is the purpose of those sessions (I thinks it maintains the synchronisation information....) .... What could be the reason for so many sessions to be created... Could it be network failure...
    Thanks
    Christophe Lizé

    Hi Ogan,
    Thanks for your answer. This is a windows box. SAP is the application that consumes the data.
    In the standby alertlog, we can see the session that is started:
    Setting recovery target incarnation to 2
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=14, OS id=4380
    ARC1 started with pid=15, OS id=5008
    ARC2 started with pid=16, OS id=2276
    ARC3 started with pid=17, OS id=3596
    ARC4 started with pid=18, OS id=5852
    ARC5 started with pid=19, OS id=6044
    ARC6 started with pid=20, OS id=4956
    ARC7 started with pid=21, OS id=6068
    ARC8 started with pid=22, OS id=2380
    Wed Nov 24 15:05:52 2010
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC9 started with pid=23, OS id=5296
    Wed Nov 24 15:05:53 2010
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Wed Nov 24 15:05:53 2010
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC0: Thread not mounted
    Wed Nov 24 15:05:53 2010
    ARC1: Becoming the heartbeat ARCH
    ARC1: Thread not mounted
    Wed Nov 24 15:05:53 2010
    ARC4: Thread not mounted
    Wed Nov 24 15:05:53 2010
    Successful mount of redo thread 1, with mount id 589430539
    Wed Nov 24 15:05:53 2010
    Physical Standby Database mounted.
    Completed: alter database mount standby database
    Wed Nov 24 15:05:53 2010
    alter database recover managed standby database disconnect from session
    MRP0 started with pid=24, OS id=3980
    Wed Nov 24 15:05:54 2010
    ARC7: Thread not mounted
    Wed Nov 24 15:05:55 2010
    ARC9: Thread not mounted
    Wed Nov 24 15:05:56 2010
    ARC5: Thread not mounted
    Wed Nov 24 15:05:57 2010
    ARC3: Thread not mounted
    Wed Nov 24 15:05:58 2010
    ARC2: Thread not mounted
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Wed Nov 24 15:05:58 2010
    Waiting for all non-current ORLs to be archived...
    Wed Nov 24 15:05:59 2010
    ARC6: Thread not mounted
    Wed Nov 24 15:05:59 2010
    Completed: alter database recover managed standby database disconnect from session
    Wed Nov 24 15:05:59 2010
    Media Recovery Waiting for thread 1 sequence 816
    Fetching gap sequence in thread 1, gap sequence 816-821
    Wed Nov 24 15:06:00 2010
    ARC8: Thread not mounted
    Wed Nov 24 15:06:10 2010
    Using STANDBY_ARCHIVE_DEST parameter default value as G:\oracle\PPS\oraarch
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 5408
    RFS[1]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    RFS LogMiner: Client disabled from further notification
    Wed Nov 24 15:06:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2360
    RFS[2]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 5872
    RFS[3]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 2012
    RFS[4]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[5]: Assigned to RFS process 5336
    RFS[5]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[6]: Assigned to RFS process 3888
    RFS[6]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[7]: Assigned to RFS process 3088
    RFS[7]: Identified database type as 'physical standby'
    Wed Nov 24 15:06:10 2010
    RFS[3]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_817_735230249.ARC'
    Wed Nov 24 15:06:10 2010
    RFS[4]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_818_735230249.ARC'
    Wed Nov 24 15:06:10 2010
    RFS[7]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_821_735230249.ARC'
    Wed Nov 24 15:06:11 2010
    RFS[2]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_819_735230249.ARC'
    Wed Nov 24 15:06:11 2010
    RFS[5]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_816_735230249.ARC'
    Wed Nov 24 15:06:11 2010
    RFS[6]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_820_735230249.ARC'
    Wed Nov 24 15:06:29 2010
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_816_735230249.ARC
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_817_735230249.ARC
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_818_735230249.ARC
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_819_735230249.ARC
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_820_735230249.ARC
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_821_735230249.ARC
    Media Recovery Waiting for thread 1 sequence 822
    Fetching gap sequence in thread 1, gap sequence 822-822
    Wed Nov 24 15:07:10 2010
    RFS[6]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_822_735230249.ARC'
    Wed Nov 24 15:07:31 2010
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_822_735230249.ARC
    Media Recovery Waiting for thread 1 sequence 823
    Wed Nov 24 15:08:11 2010
    RFS[7]: Archived Log: 'G:\ORACLE\PPS\ORAARCH\LOG1_823_735230249.ARC'
    Wed Nov 24 15:08:31 2010
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_823_735230249.ARC
    Media Recovery Waiting for thread 1 sequence 824
    Wed Nov 24 15:15:00 2010
    RFS[1]: Successfully opened standby log 5: 'G:\ORACLE\PPS\ORIGLOGA\STBLOG_G5M1.DBF'
    Wed Nov 24 15:15:01 2010
    Media Recovery Log G:\ORACLE\PPS\ORAARCH\LOG1_824_735230249.ARCA lot of RFS process are created and each one is taking a session with the user PUBLIC.
    What drives the creation of RFS process... and why Oracle does not reuse those created....
    on the standby, the following query shows UNKNOW client_process
    SQL> select process,status,client_process,sequence#,block#,active_agents,known_agents
      2  from v$managed_standby;
    PROCESS STATUS       CLIENT_P  SEQUENCE#     BLOCK# ACTIVE_AGENTS KNOWN_AGENTS
    ARCH    CLOSING      ARCH            800          1             0            0
    ARCH    CLOSING      ARCH            801          1             0            0
    ARCH    CLOSING      ARCH            802          1             0            0
    ARCH    CLOSING      ARCH            803       2049             0            0
    ARCH    CLOSING      ARCH            804          1             0            0
    ARCH    CLOSING      ARCH            805          1             0            0
    ARCH    CLOSING      ARCH            795       2049             0            0
    ARCH    CLOSING      ARCH            796          1             0            0
    ARCH    CLOSING      ARCH            797          1             0            0
    ARCH    CLOSING      ARCH            798          1             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    MRP0    WAIT_FOR_LOG N/A             807          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    PROCESS STATUS       CLIENT_P  SEQUENCE#     BLOCK# ACTIVE_AGENTS KNOWN_AGENTS
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    RFS     IDLE         UNKNOWN           0          0             0            0
    57 rows selected.I don't know if you have enough information...
    Thanks
    Christophe

  • Log transport failing to standby host , target using ASM.

    Hi,
    Please help me in the following scenario. I have two nodes ASM1 & ASM2 with RHEL4 U5 OS. On node ASM1 there is database ORCL using ASM diskgroups DATA & RECOVER and archive location is on '+RECOVER/orcl/'. On ASM2 node, I have to configure STDBYORCL (standby) database without ASM (i.e. on FS). I have taken the copy of database ORCL via RMAN, using following command:
    run{
    copy datafile 1 to '/opt/oracle/admin/df1.dbf';
    copy datafile 2 to '/opt/oracle/admin/df2.dbf';
    copy datafile 3 to '/opt/oracle/admin/df3.dbf';
    copy datafile 4 to '/opt/oracle/admin/df4.dbf';
    copy current controlfile for standby to '/opt/oracle/admin/stdbyorcl_control01.ctl'
    Then I have ftp'd all to ASM2 and put them on FS /u01/oradata. Have made all necessary changes in primary and standby database pfile and then mount the standby database and put it in managed recovery mode. Unfortunately, log transport service is not working and archives are not getting shipped to standby host.
    Here are all configuration details.
    Primary database ORCL pfile:
    [oracle@asm dbs]$ more initorcl.ora
    stdbyorcl.__db_cache_size=251658240
    orcl.__db_cache_size=226492416
    stdbyorcl.__java_pool_size=4194304
    orcl.__java_pool_size=4194304
    stdbyorcl.__large_pool_size=4194304
    orcl.__large_pool_size=4194304
    stdbyorcl.__shared_pool_size=100663296
    orcl.__shared_pool_size=125829120
    stdbyorcl.__streams_pool_size=0
    orcl.__streams_pool_size=0
    *.audit_file_dest='/opt/oracle/admin/orcl/adump'
    *.background_dump_dest='/opt/oracle/admin/orcl/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='+DATA/orcl/controlfile/current.270.665007729','+RECOVER/orcl/controlfile/current.262.665007731'
    *.core_dump_dest='/opt/oracle/admin/orcl/cdump'
    *.db_block_size=8192
    *.db_create_file_dest='+DATA'
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_recovery_file_dest='+RECOVER'
    *.db_recovery_file_dest_size=3163553792
    *.db_unique_name='ORCL'
    *.fal_client='ORCL'
    *.fal_server='STDBYORCL'
    *.instance_name='orcl'
    *.job_queue_processes=10
    *.log_archive_config='dg_config=(orcl,stdbyorcl)'
    *.log_archive_dest_1='LOCATION=+RECOVER/orcl/'
    *.log_archive_dest_2='SERVICE=stdbyorcl'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='%t_%s_%r.dbf'
    *.open_cursors=300
    *.pga_aggregate_target=121634816
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=364904448
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS'
    *.user_dump_dest='/opt/oracle/admin/orcl/udump'
    Standby database STDBYORCL pfile:
    [oracle@asm2 dbs]$ more initstdbyorcl.ora
    stdbyorcl.__db_cache_size=251658240
    stdbyorcl.__java_pool_size=4194304
    stdbyorcl.__large_pool_size=4194304
    stdbyorcl.__shared_pool_size=100663296
    stdbyorcl.__streams_pool_size=0
    *.audit_file_dest='/opt/oracle/admin/stdbyorcl/adump'
    *.background_dump_dest='/opt/oracle/admin/stdbyorcl/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='u01/oradata/stdbyorcl_control01.ctl'#Restore Controlfile
    *.core_dump_dest='/opt/oracle/admin/stdbyorcl/cdump'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/oradata'
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_recovery_file_dest='/u01/oradata/backup'
    *.db_recovery_file_dest_size=3163553792
    *.db_unique_name='STDBYORCL'
    *.fal_client='STDBYORCL'
    *.fal_server='ORCL'
    *.instance_name='stdbyorcl'
    *.job_queue_processes=10
    *.log_archive_config='dg_config=(orcl,stdbyorcl)'
    *.log_archive_dest_1='LOCATION=/u01/oradata/archive'
    *.log_archive_dest_2='SERVICE=orcl'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='%t_%s_%r.dbf'
    *.log_archive_start=TRUE
    *.open_cursors=300
    *.pga_aggregate_target=121634816
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=364904448
    *.standby_archive_dest='LOCATION=/u01/oradata/archive'
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS'
    *.user_dump_dest='/opt/oracle/admin/stdbyorcl/udump'
    db_file_name_convert=('+DATA/ORCL/DATAFILE','/u01/oradata','+RECOVER/ORCL/DATAFILE','/u01/oradata')
    log_file_name_convert=('+DATA/ORCL/ONLINELOG','/u01/oradata','+RECOVER/ORCL/ONLINELOG','/u01/oradata')
    Have configured the tns service on both the hosts and its working absolutely fine.
    ASM1
    =====
    [oracle@asm dbs]$ tnsping stdbyorcl
    TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 19-SEP-2008 18:49:00
    Copyright (c) 1997, 2005, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.20)(PORT = 1521))) (CONNECT_DATA = (SID = stdbyorcl) (SERVER = DEDICATED)))
    OK (30 msec)
    ASM2
    =====
    [oracle@asm2 archive]$ tnsping orcl
    TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 19-SEP-2008 18:48:39
    Copyright (c) 1997, 2005, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.10)(PORT = 1521))) (CONNECT_DATA = (SID = orcl) (SERVER = DEDICATED)))
    OK (30 msec)
    Please guide where I am missing. Thanking you in anticipation.
    Regards,
    Ravish Garg
    (Oracle DBA)

    As Anvar said, check your primary db's alert log what error message you get...
    I am wondering you need this in your standby parameter file?..
    *.log_archive_dest_2='SERVICE=orcl'
    *.log_archive_dest_state_2='ENABLE'

  • Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

    Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%). 
    The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
    configured threshold.” 
    There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20). 
    From what I can tell, all of the IP addresses are from Taiwan. 
    The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014). 
    From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening. 
    The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
    Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
    The Error reads:
    The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
    mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
    Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
    Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
    I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
    Recent changes to the system:
    About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
    Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
    I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
    Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

    Hi,
    Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Frontend transport service

    I have an exchange 2013 server that is set for outbound mail only.  Inbound mail is disabled by intention.  I had an issue whereby the transport and frontend transport services would not run simultaneously.  So i shut off frontend transport
    and turned on transport and outbound mail is processing successfully.  My question is was frontend transport being shutdown automatically because inbound mail is turned off?   I've read that frontend transport acts as a proxy for all inbound and
    (optionally) outbound messages.  Does this mean that if you disable inbound messaging then frontend transport shutting off is normal?  

    Hi,
    As Sarvesh suggested, I recommend you check if there is any error or warning in the event log when the Microsoft Exchange Frontend Transport service is stopped. If yes, please take your time to post it for my further research.
    What's more, I recommend you turn on inbound mail temporarily to verify if the Microsoft Exchange Frontend Transport service can be started.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Event ID 7031 followed by 7032 The Microsoft Exchange Transport service terminated unexpectedly.

    Hello
    Have a strange problem that reoccurs every day. The following are recorded in the log.
    7031
    The Microsoft Exchange Transport service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.7032The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Transport service, but this action failed with the following error:
    An instance of the service is already running.Any suggestions are welcome./Deland
    /Andreas

    Here are the result from the level 5 logging. I Havent disabled the TransportAgent yet.
    Log Name:      Application
    Source:        MSExchangeTransport
    Date:          2013-07-19 10:13:25
    Event ID:      12025
    Task Category: TransportService
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      XXXX
    Description:
    Transport service is disconnecting performance counters with process lifetime from their old process.
    Followed by 32 events of 12028
    Log Name:      Application
    Source:        MSExchangeTransport
    Date:          2013-07-19 10:13:25
    Event ID:      12028
    Task Category: TransportService
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      XXXX
    Description:
    The process with process ID 1100 is holding the performance counter configuration cache total requests Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062 from instance transportrules(B1D082BB) RefCount=0 SpinLock=0 Offset=3936
    and category MSExchangeTransport Configuration Cache while running processes are: Processes running are:
    6300 UMWorkerProcess
    5312 Microsoft.Exchange.ServiceHost
    1568 Microsoft.Exchange.Diagnostics.Service
    2212 WMSvc
    776 svchost
    1760 MSExchangeHMHost
    9808 MSExchangeDelivery
    376 explorer
    2252 Microsoft.Exchange.Directory.TopologyService
    9436 rundll32
    1752 nscp
    2932 noderunner
    6076 MSExchangeSubmission
    7056 scanningprocess
    1736 PccNtMon
    1340 fms
    4688 MSExchangeTransport
    1732 Ntrtscan
    2716 MSExchangeMailboxAssistants
    548 winlogon
    9016 TmProxy
    348 svchost
    2904 SMSvcHost
    1524 inetinfo
    8376 TMBMSRV
    5264 MSExchangeThrottling
    12552 powershell
    4080 w3wp
    1124 svchost
    7688 svchost
    12744 w3wp
    332 smss
    1316 svchost
    13188 mmc
    5772 ForefrontActiveDirectoryConnector
    3080 HostedAgent
    11364 conhost
    3268 w3wp
    1060 svchost
    2924 noderunner
    904 dwm
    3856 w3wp
    504 wininit
    7200 Microsoft.Exchange.Store.Worker
    1668 SMSvcHost
    4832 MSExchangeFrontendTransport
    2072 sftracing
    4932 MSExchangeMailboxReplication
    7192 Microsoft.Exchange.Store.Worker
    6992 Microsoft.Exchange.UM.CallRouter
    9640 w3wp
    9204 svchost
    3244 svcGenericHost
    1200 Microsoft.Exchange.Store.Service
    876 svchost
    10724 rundll32
    3040 conhost
    2480 w3wp
    5992 MSExchangeTransportLogSearch
    596 services
    12508 w3wp
    2636 MSExchangeHMWorker
    11892 taskhostex
    4796 Microsoft.Exchange.Search.Service
    3568 WmiPrvSE
    12532 ServerManager
    9564 msdtc
    4352 Microsoft.Exchange.EdgeSyncSvc
    2032 mqsvc
    6560 scanningprocess
    3404 TmListen
    4384 updateservice
    3004 scanningprocess
    6744 umservice
    1424 hostcontrollerservice
    828 svchost
    432 csrss
    696 svchost
    1284 spoolsv
    8152 w3wp
    3576 w3wp
    1264 svchost
    496 csrss
    5928 Microsoft.Exchange.RpcClientAccess.Service
    2972 noderunner
    2380 conhost
    604 lsass
    6884 Microsoft.Exchange.Store.Worker
    10056 WmiPrvSE
    992 svchost
    2764 noderunner
    5324 msexchangerepl
    4 System
    3548 Microsoft.Exchange.AntispamUpdateSvc
    2168 svchost
    0 Idle
    And 28 events on 106
    Log Name:      Application
    Source:        MSExchange Common
    Date:          2013-07-19 10:13:29
    Event ID:      106
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXXX
    Description:
    Performance counter updating error. Counter name is DataRow seeks total, category name is MSExchangeTransport Database. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance '_total' already exists with a lifetime
    of Process.  It cannot be recreated or reused until it has been removed or until the process using it has exited.
       at System.Diagnostics.SharedPerformanceCounter.FindInstance(Int32 instanceNameHashCode, String instanceName, CategoryEntry* categoryPointer, InstanceEntry** returnInstancePointerReference, Boolean activateUnusedInstances, PerformanceCounterInstanceLifetime
    lifetime, Boolean& foundFreeInstance)
       at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)
       at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.get_RawValue()
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
    Last worker process info : System.ArgumentException: Process with an Id of 14868 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Processes running while Performance counter failed to update:
    6300 UMWorkerProcess
    5312 Microsoft.Exchange.ServiceHost
    1568 Microsoft.Exchange.Diagnostics.Service
    2212 WMSvc
    776 svchost
    1760 MSExchangeHMHost
    9808 MSExchangeDelivery
    376 explorer
    2252 Microsoft.Exchange.Directory.TopologyService
    9436 rundll32
    1752 nscp
    2932 noderunner
    10416 EdgeTransport
    6076 MSExchangeSubmission
    7056 scanningprocess
    1736 PccNtMon
    1340 fms
    4688 MSExchangeTransport
    1732 Ntrtscan
    2716 MSExchangeMailboxAssistants
    548 winlogon
    9016 TmProxy
    348 svchost
    2904 SMSvcHost
    1524 inetinfo
    15116 conhost
    8376 TMBMSRV
    5264 MSExchangeThrottling
    12552 powershell
    4080 w3wp
    1124 svchost
    7688 svchost
    12744 w3wp
    332 smss
    1316 svchost
    13188 mmc
    5772 ForefrontActiveDirectoryConnector
    3080 HostedAgent
    11364 conhost
    3268 w3wp
    1060 svchost
    2924 noderunner
    904 dwm
    3856 w3wp
    504 wininit
    7200 Microsoft.Exchange.Store.Worker
    1668 SMSvcHost
    4832 MSExchangeFrontendTransport
    2072 sftracing
    4932 MSExchangeMailboxReplication
    7192 Microsoft.Exchange.Store.Worker
    6992 Microsoft.Exchange.UM.CallRouter
    9640 w3wp
    9204 svchost
    3244 svcGenericHost
    1200 Microsoft.Exchange.Store.Service
    876 svchost
    10724 rundll32
    3040 conhost
    2480 w3wp
    5992 MSExchangeTransportLogSearch
    596 services
    12508 w3wp
    2636 MSExchangeHMWorker
    11892 taskhostex
    4796 Microsoft.Exchange.Search.Service
    3568 WmiPrvSE
    12532 ServerManager
    9564 msdtc
    4352 Microsoft.Exchange.EdgeSyncSvc
    2032 mqsvc
    6560 scanningprocess
    3404 TmListen
    4384 updateservice
    3004 scanningprocess
    6744 umservice
    1424 hostcontrollerservice
    828 svchost
    432 csrss
    696 svchost
    1284 spoolsv
    8152 w3wp
    3576 w3wp
    1264 svchost
    496 csrss
    5928 Microsoft.Exchange.RpcClientAccess.Service
    2972 noderunner
    2380 conhost
    604 lsass
    6884 Microsoft.Exchange.Store.Worker
    10056 WmiPrvSE
    992 svchost
    2764 noderunner
    5324 msexchangerepl
    4 System
    3548 Microsoft.Exchange.AntispamUpdateSvc
    2168 svchost
    0 Idle
    Performance Counters Layout information: A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=59 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : queue(B351294)
    RefCount=0 SpinLock=0 Offset=48552, categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 8(ED0419E7) RefCount=0 SpinLock=0 Offset=44384,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 6(ED0419E9) RefCount=0 SpinLock=0 Offset=40216,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=4 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 3(ED0419EC) RefCount=0 SpinLock=0 Offset=36048,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=3 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 1(ED0419EE) RefCount=0 SpinLock=0 Offset=31880,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=18 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat(B874BB3) RefCount=0 SpinLock=0 Offset=27712,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : inqueue(56145953) RefCount=0 SpinLock=0 Offset=23544,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=17 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : smtpin(81392C98) RefCount=0 SpinLock=0 Offset=19376,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : mail(7C6FB7CC) RefCount=0 SpinLock=0 Offset=15208,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=68 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : other(ADC98A1) RefCount=0 SpinLock=0 Offset=11040,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 4832, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4832 StartupTime: 130183498009738545, currentInstance : _total(CFBEE918) RefCount=1 SpinLock=0 Offset=32,
    categoryName: MSExchangeTransport Database
    Log Name:      Application
    Source:        MSExchange Common
    Date:          2013-07-19 10:13:31
    Event ID:      106
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXXX
    Description:
    Performance counter updating error. Counter name is Transaction Durable Callback Count/sec, category name is MSExchangeTransport Database. Optional code: 1. Exception: The exception thrown is : System.InvalidOperationException: Instance '_total' already exists
    with a lifetime of Process.  It cannot be recreated or reused until it has been removed or until the process using it has exited.
       at System.Diagnostics.SharedPerformanceCounter.FindInstance(Int32 instanceNameHashCode, String instanceName, CategoryEntry* categoryPointer, InstanceEntry** returnInstancePointerReference, Boolean activateUnusedInstances, PerformanceCounterInstanceLifetime
    lifetime, Boolean& foundFreeInstance)
       at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)
       at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.IncrementBy(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.IncrementBy(Int64 incrementValue)
    Last worker process info : System.ArgumentException: Process with an Id of 14868 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Processes running while Performance counter failed to update:
    6300 UMWorkerProcess
    5312 Microsoft.Exchange.ServiceHost
    1568 Microsoft.Exchange.Diagnostics.Service
    2212 WMSvc
    776 svchost
    1760 MSExchangeHMHost
    9808 MSExchangeDelivery
    376 explorer
    2252 Microsoft.Exchange.Directory.TopologyService
    9436 rundll32
    1752 nscp
    2932 noderunner
    10416 EdgeTransport
    6076 MSExchangeSubmission
    7056 scanningprocess
    1736 PccNtMon
    1340 fms
    4688 MSExchangeTransport
    1732 Ntrtscan
    2716 MSExchangeMailboxAssistants
    548 winlogon
    9016 TmProxy
    348 svchost
    2904 SMSvcHost
    1524 inetinfo
    15116 conhost
    8376 TMBMSRV
    5264 MSExchangeThrottling
    12552 powershell
    4080 w3wp
    1124 svchost
    7688 svchost
    12744 w3wp
    332 smss
    1316 svchost
    13188 mmc
    5772 ForefrontActiveDirectoryConnector
    3080 HostedAgent
    11364 conhost
    3268 w3wp
    1060 svchost
    2924 noderunner
    904 dwm
    3856 w3wp
    504 wininit
    7200 Microsoft.Exchange.Store.Worker
    1668 SMSvcHost
    4832 MSExchangeFrontendTransport
    2072 sftracing
    4932 MSExchangeMailboxReplication
    7192 Microsoft.Exchange.Store.Worker
    6992 Microsoft.Exchange.UM.CallRouter
    9640 w3wp
    9204 svchost
    3244 svcGenericHost
    1200 Microsoft.Exchange.Store.Service
    876 svchost
    10724 rundll32
    3040 conhost
    2480 w3wp
    5992 MSExchangeTransportLogSearch
    596 services
    12508 w3wp
    2636 MSExchangeHMWorker
    11892 taskhostex
    4796 Microsoft.Exchange.Search.Service
    3568 WmiPrvSE
    12532 ServerManager
    9564 msdtc
    4352 Microsoft.Exchange.EdgeSyncSvc
    2032 mqsvc
    6560 scanningprocess
    3404 TmListen
    4384 updateservice
    3004 scanningprocess
    6744 umservice
    1424 hostcontrollerservice
    828 svchost
    432 csrss
    696 svchost
    1284 spoolsv
    8152 w3wp
    3576 w3wp
    1264 svchost
    496 csrss
    5928 Microsoft.Exchange.RpcClientAccess.Service
    2972 noderunner
    2380 conhost
    604 lsass
    6884 Microsoft.Exchange.Store.Worker
    10056 WmiPrvSE
    992 svchost
    2764 noderunner
    5324 msexchangerepl
    4 System
    3548 Microsoft.Exchange.AntispamUpdateSvc
    2168 svchost
    0 Idle
    Performance Counters Layout information: A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=59 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : queue(B351294)
    RefCount=0 SpinLock=0 Offset=48552, categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 8(ED0419E7) RefCount=0 SpinLock=0 Offset=44384,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 6(ED0419E9) RefCount=0 SpinLock=0 Offset=40216,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=4 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 3(ED0419EC) RefCount=0 SpinLock=0 Offset=36048,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=3 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 1(ED0419EE) RefCount=0 SpinLock=0 Offset=31880,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=18 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat(B874BB3) RefCount=0 SpinLock=0 Offset=27712,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : inqueue(56145953) RefCount=0 SpinLock=0 Offset=23544,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=17 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : smtpin(81392C98) RefCount=0 SpinLock=0 Offset=19376,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 10416, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 10416 StartupTime: 130186952059962770, currentInstance : mail(7C6FB7CC) RefCount=1 SpinLock=0 Offset=15208,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 10416, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 10416 StartupTime: 130186952059962770, currentInstance : other(ADC98A1) RefCount=1 SpinLock=0 Offset=11040,
    categoryName: MSExchangeTransport Database
    A process is holding onto a transport performance counter. processId : 4832, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4832 StartupTime: 130183498009738545, currentInstance : _total(CFBEE918) RefCount=1 SpinLock=0 Offset=32,
    categoryName: MSExchangeTransport Database
    Then ESE  Recovery starts on the Transport database. 
    /Andreas

  • Transport service does not start automatically after upgrade to exchange 2010 SP2 from Exchange 2010 SP1

    Hi,
    I am trying to upgrade Exchange 2010 SP2 from SP1, but Transport service does not start automatically.
    Tried manually start services, it started successfully but again goes down within few seconds automatically.
    Reboot server. but no luck.
    Any help.
    MD

    Hi,
    I recommend you use event viewer to check if there are any relate event logs. This may help us to find the cause.
    In addition, as Amit mentioned, Exchange 2010 SP2 isn't supported by Microsoft, I think upgrading to SP3 is a much more sensible approach.
    Thanks.
    Niko Cheng
    TechNet Community Support

  • FYI: TrendMicro antivirus prevents Transport Service from starting after installing Echange Server 2013 Service Pack 1

    I installed Exchange Server 2013 SP1 in my test environment. After that mail flow between internal and external mail servers completely stopped. In the end I discovered that Transport Service on both of the mailbox servers refused to start (or, to be more
    exact, stopped shortly after starting).
    The following events appeared in the System event log:
    Event ID 1052 (error)
    Source: MSExchange Extensibility
    Message: Failed to create agent factory for the agent 'ScanMail SMTP Receive Agent' with error 'Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll'
    due to error 'type not found'.'. Please verify the corresponding transport agent assembly and dependencies with correct version are installed.
    Event ID 16023 (error)
    Source: MSExchangeTransport
    Message: Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program
    Files\Trend Micro\Smex\hookE12TransportAgent.dll' due to error 'type not found'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program
    Files\Trend Micro\Smex\hookE12TransportAgent.dll' due to error 'type not found'.
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents, FactoryInitializer factoryInitializer)
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup, FactoryInitializer factoryInitializer)
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath, FactoryInitializer factoryInitializer)
       at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
    Event ID 701 (informational)
    Source: MSExchangeTransport
    Message: The service will be stopped. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'SmtpReceiveAgents' failed. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The agent component
    failed to load. ---> Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll' due to
    error 'type not found'.
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents, FactoryInitializer factoryInitializer)
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup, FactoryInitializer factoryInitializer)
       at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath, FactoryInitializer factoryInitializer)
       at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
       at Microsoft.Exchange.Transport.Components.Activate()
    The reason for that behavior was TrendMicro ScanMail for Exchange 11. Seems that it was unable to work with the new SP properly and prevented the entire Transport Service from starting. Uninstallation of the antivirus eliminated the issue.

    Actually, you can just disable the agents until TrendMicro releases a patch and then enable them again:
    http://community.trendmicro.com/...
    BTW, a similar problem (high CPU utilization and services not starting) is hitting the AVG package:
    http://forums.avg.com/..
    Step by Step Screencasts and Video Tutorials

  • Error in step 8 - transport service

    hi there,
    i need some help here... in the instalation of exchange server 2012 apear this error on mailbox roles: transport service.
    how i renew the certificate? that the program ask...
    thanks.
    Error:
    The following error was generated when "$error.Clear(); 
              Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "System.Security.Cryptography.CryptographicException: The certificate is expired.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi John,
    Based on my experience, this error usually is caused by incorrect system time.
    And as we know first place to check is ExchangeSetup.log, open the log file and press Ctrl+End, you will reach the end of the file the place where our error will be available. Then check the
    validity of certificate(Start time and End time), if the certificate is valid, please make sure your system time is correct.
    And if the certificate is expired, you need to renew the certificate.
    Click the link below for more information:
    Renewing Certification Authorities
    http://technet.microsoft.com/en-us/library/cc962077.aspx
    Hope it can be helpful.
    Best regards,
    Eric

  • Exchange Server crashed while installing Transport service

    Hi!
    Having some massive issues with the initial install of Exchange 2013 SP1 on Windows Server 2012 Standard.
    Basically, it has crashed multiple times and usually at the end of the install, so I end up with a partial installation which then needs to be manually removed as it won't remove it via the Programs and Features option.
    I have finally got the error after doing the install from the powershell.
    Take note, I am part of the Schema Groups and Domain Admins and have fulfilled the Exchange 2013  prerequisites.
    The server came from Dell with Windows 2012 set up already, Ive just downloaded the Exchange 2013 iso from microsoft and mounted it.
    I've tried also running the setup.exe as administrator (I am also logged in as the domain administrator)
    The last command that I ran from power shell is this.
    Setup.exe /mode:Install /role:ClientAccess,Mailbox /DomainController:SERVER /IAcceptExchangeServerLicenseTerms
    Then I get the below error, regardless of the error the server has 16gb of memory with not much else going on, the hard drives have plenty of space so no issues there either.
    Error:
    The following error was generated when "$error.Clear(); 
                Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
                $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
                $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
                Write-ExchangeSetupLog -Info "Loading FipFs snapin";
                Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
                # Copy Microsoft Engine to Engines folder during the install
                $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
                $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
                $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
                $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
                if(! $MicrosoftEngineExists)
                  Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
              " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete
    this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
    Error:
    The following error was generated when "$error.Clear(); 
                Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
                $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
                $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
                Write-ExchangeSetupLog -Info "Loading FipFs snapin";
                Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
                # Copy Microsoft Engine to Engines folder during the install
                $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
                $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
                $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
                $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
                if(! $MicrosoftEngineExists)
                  Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
              " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete
    this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
    The 2 things that I had to fix during install was that the registry was missing the FIPS entry, once I had manually created that entry again the Exchange installation got up installing the Mailbox role: Transport Service and then errored with the above message.
    As this is a fairly new product theres not much information out there.
    Any Help will be appreciated.
    Thanks,
    Cameron

    Hi 
    Since you have mentioned that It has crashed multiple times its not successful its better to try the installation on a different PC or you can try formatting the box and proceed with the exchange  installation since its a new Exchange 2013 installation.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

  • Transport Service Stops once a week & doesn't restart- causing mailflow issue

    Hi All
    I have a customer with Exchange Server 2013 Standard SP1. I have recently migrated them from Exchange 2010.
    Single Server for All roles. VM has Trend Micro office scan agent installed. Server resource is adequate, Separate drive holds logs, exchange database.
    The only Error / warnings I can find from Event logs are below
    1) Event ID - 6002, Ping of Mailbox database timed out after 00.00.00 minutes
    2) Event ID- 6027, MS Filtering failed to contact primary update path
    3) Event ID- 16028, A lot of this event.
    I have done a bit of searching and reading and seems like all the above could be ignored,
    However my main concern is, I have noticed over the last couple of week that once a week Exchange Transport Service stops and fails to restart itself causing mail flow until staff tells me none is receiving email then I manually start the service.
    Has someone ran it to something similar or can offer a solution? Perhaps a script that runs and checks transport service and if service failure detected then wait 1 minute to force restart it?
    Thank you in advance.  
    MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

    I have gone through several troubleshooting as below
    1) Made sure disabled Anti-malware agent in exchange
    2) Made sure frontend connectors only have one 25 port as described in this article -
    http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-server-2013-sp1-transport-service-stops-and-does-not-restart.html
    3) Made sure to exclude folders that hold mailbox database from scanning by trend Micro officescan agent
    4) Made sure the DNS is pointing currently and doesn't have any bindings to 127. address
    5) Do not have any custom receive connector, the only modification I did to the default Hum transport and Default frontendTransport connector is that I have enabled anonymous user for both of this connector.
    I am in the process of creating a powershell script with the help of (powershell boy) which does a service check via task scheduler and if found service not running then waits for 2 minutes and force
    re-starts the transport service. If this work, it will be a band aid solution, however wondering if someone has found a permanent fix yet?
    MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

  • Exchange Installation Error on Mailbox role: Transport Service Step

    The error I receive occurs at 47% of the Mailbox Role: Transport Service installation.  The details of the error are as follows:
        Mailbox role: Transport service                                                                  
    FAILED
         The following error was generated when "$error.Clear();
              if ($server -eq $null)
                set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
            " was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
    Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
            'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
    Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    Also, when opening the setup log I have this:
    [12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
    [12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.
    [12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
    [12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
    [12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [12/26/2012 17:51:25.0825] [0] End of Setup
    [12/26/2012 17:51:25.0825] [0] **********************************************
    I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/
    http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/
    Some additional information:
    This is a clean installation of Exchange 2013 in a forest that has never had exchange.
    The domain and forest preparations run without errors and are at functional level of 2003.
    The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.
    This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.
    I am running the installation as an enterprise, schema, domain admin.
    Thanks for your help in advance.

    Yes.  I cleaned out Exchange with ADSIEdit so I could re-run the Prepare Schema, domain and all domains and then re-ran setup to show the output here.  But the install still failed.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareSchema
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Extending Active Directory schema                                                                
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:AZGT
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
    een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
    aspx
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAllDomains
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Prepare Domain Progress                                                                          
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\>
    PS F:\> .\setup /IAcceptExchangeServerLicenseTerms /mode:install /roles:Mailbox /TargetDir:"C:\Program Files\Microsoft\Exchange Server\V15"
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Languages
    Management tools
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                                                        
    COMPLETED
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Preparing Setup                                                                                  
    COMPLETED
        Stopping Services                                                                                
    COMPLETED
        Copying Exchange Files                                                                           
    COMPLETED
        Language Files                                                                                   
    COMPLETED
        Restoring Services                                                                               
    COMPLETED
        Language Configuration                                                                           
    COMPLETED
        Exchange Management Tools                                                                        
    COMPLETED
        Mailbox role: Transport service                                                                  
    FAILED
         The following error was generated when "$error.Clear();
              if ($server -eq $null)
                set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainCo
    ntroller
            " was run: "Active Directory operation failed on DC1.XXXX.XXXX.com. This error is not retriable. Addi
    tional information: The object cannot be added because the parent is not on the list of possible superiors.
    Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
            'CN=EXCHMBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
    Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=XXXX,DC=com'
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS F:\>

  • Exchange Transport Service not starting

    Hello All:
    I have installed exchange server 2007 in my Windows Server 2008 domain.I have noticed that when I open up the services tab on my server and check the services which are running that the Information Store and Transport services are set to start automatically. However, they are not running. When I tell it to start the Information Store that service will start. When I tell it to start the Microsoft Exchange Transport  service, I get the following message:
    The Microsoft Exchange Transport Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs. I know that this service must be running in order for me to send and receive mail. Can someone tell me how to troubleshoot and correct this problem. Thanks in advance for any and all responses to this question.
    When I look in the event logs I see the following:Log Name:      Application
    Source:        MSExchange TransportService
    Date:          1/31/2009 10:43:05 AM
    Event ID:      1016
    Task Category: ProcessManager
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      AESTONE.stone-and-stone.com
    Description:
    The worker process crashes continuously on startup: C:\Program Files\Microsoft\Exchange Server\Bin\edgetransport.exe. The service will be stopped.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange TransportService" />
        <EventID Qualifiers="49156">1016</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-31T15:43:05.000Z" />
        <EventRecordID>478666</EventRecordID>
        <Channel>Application</Channel>
        <Computer>AESTONE.stone-and-stone.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>C:\Program Files\Microsoft\Exchange Server\Bin\edgetransport.exe</Data>
      </EventData>
    </Event>
    Any suggestions anyone?

     
    Dear customer:
    Did you upgrade a computer that is running Windows Server 2003 to Windows Server 2008?
    If so, please refer to the following article to fix the issue:
    Multiple Exchange Server 2007 services do not start when you upgrade a computer that is also running Windows Server 2003 to Windows Server 2008
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;951402
    Also, check Exchange2007 Setup log file, if the error resemble the following words:
    2/3/2007 1:07:16 AM] [2] [ERROR] Service 'MSExchangeTransport' failed to start.
    Check the event log for possible reasons for the service start failure.
    [2/3/2007 1:07:16 AM] [2] Ending processing.
    [2/3/2007 1:07:16 AM] [1] The following 1 error(s) occurred during task
    execution:
    [2/3/2007 1:07:16 AM] [1] 0. ErrorRecord: Service 'MSExchangeTransport' failed to
    start. Check the event log for possible reasons for the service start failure.
    [2/3/2007 1:07:16 AM] [1] 0. ErrorRecord:
    Microsoft.Exchange.Configuration.Tasks.ServiceFailedToStartException: Service
    'MSExchangeTransport' failed to start. Check the event log for possible reasons for
    the service start failure.
    [2/3/2007 1:07:16 AM] [1] [ERROR] Service 'MSExchangeTransport' failed to start.
    Check the event log for possible reasons for the service start failure.
    [2/3/2007 1:07:16 AM] [1] Setup is halting task execution because of one or more
    errors in a critical task.
    [2/3/2007 1:07:16 AM] [1] Finished executing component tasks.
    [2/3/2007 1:07:16 AM] [1] Ending processing.
    Perform the following steps to fix the issue:
    1.         Open Registry on Exchange 2007 box.
    2.         Navigate to the following registry key:
    HKLM\SYSTEM\ControlSet001\Services\Tcpip\Parameters
    3.         Right click Parameters,choose permissions,add explicitly the machine account Domainname\Exchange$ (Where Exchange is hostname for Exchange 2007 box) to the
    Access control list by giving read access to it.(Exchange must be able to read this key to find the FQDN of the server so that the SPN can be registered).
    4.         Check the effect.
    Rock Wang - MSFT

  • Transport Mail Database issues crashing Transport service

    We are experiencing frequent issues on Hub servers (as often as once a week) where Transport Mail DB issues crash the Transport service.  Had an MS specialist in the other day who could not exactly figure out the root cause.  The pattern usually is as follows:
    1. Event ID 486 - This event refers to a failure to move a log file (associated with Transport Mail DB queues) because it is being used by another process.  What that process could be is unknown.
    2. Event ID 413 - Unable to create a new logfile because the database cannot write to the log drive.
    3. Event ID 492 - The logfile sequence in <dir> has been halted
    4. Event ID 17019 - A database operation has encountered a I/O error. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamLogWriteFailException: Failure writing to log file (-510)
    Also followed by events 7001,1022,1002, and 1003.
    Haven't been able to determine what is causing Event ID 486.  Not aware of any process that would be tying up the access to the log file.  These queue files are stored on a local disk, not a SAN. 
    Any ideas as to what could be causing this?  Running E2K7SP1 Rollup 2 currently on all Exchange systems.

    Hi,
    I suggest that you use the following method to check which process access the log file indicated in the event 486:
    Using Process Explorer
    http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
    Then, we did the following:
    1. Launch Process Explorer
    2. Click Find, Find Handle or DLL
    3. Enter the log name indicated in the event 486 and click Search
    In addition, please also check whether any events such as 150004 occur before the Transport service crashes. If you notice the event, I also suggest that you refer to the following article:
    http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx
    Mike
     

Maybe you are looking for