Richard H
asked on
MS Exchange Server 2010 Transport Server Service Will Not Start on SBS2011
After a reboot the Transport Server service will not start. I used ESEUTIL to check the integrity, recover and to repair the pasettings.edb with no success. All the Events and ESEUTIL results are listed.
eseutil /g
Integrity check successful.
eseutil /r /a trn
Operation terminated with error -1216 (JET_errAttachedDatabaseMi smatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after 0.203 seconds.
eseutil /p
Integrity check successful.
Source: ESE
Event ID: 494
Description:
edgetransport (12524) Sender Reputation Database: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\ data\Sende rReputatio n\pasettin gs.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.
Source: ESE
Event ID: 454
Description:
edgetransport (12524) Sender Reputation Database: Database recovery/restore failed with unexpected error -1216.
Source: MSExchangeTransport
Event ID: 17007
Description:
Sender Reputation Database: The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport service is shutting down. The exception is Microsoft.Exchange.Isam.Is amAttached DatabaseMi smatchExce ption: An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info (-1216)
at Microsoft.Exchange.Isam.Je tInterop.M JetInit(MJ ET_INSTANC E instance)
at Microsoft.Exchange.Isam.In terop.MJet Init(MJET_ INSTANCE instance)
at Microsoft.Exchange.Transpo rt.Storage .DataSourc e.InitInst ance().
I used ESEUTIL to try and fix the database with no success:
************************** ********** ********** ********** ********** ********
[PS] C:\>eseutil /g "C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\ data\Sende rReputatio n\pasettin gs.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating INTEGRITY mode...
Database: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\ data\Sende rReputatio n\pasettin gs.edb
Temp. Database: TEMPINTEG12576.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----| ----|----| ----|----| ----|
.......................... .......... .......... .....
Integrity check successful.
Operation completed successfully in 0.140 seconds.
************************** ********** ********** ********** ********** ********
[PS] C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\ data\Sende rReputatio n>eseutil /r /a trn
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: trn
Log files: <current directory>
System files: <current directory>
Performing soft recovery...
Restore Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----| ----|----| ----|----| ----|
.........X
Operation terminated with error -1216 (JET_errAttachedDatabaseMi smatch, An outstanding database attachment has been dete
cted at the start or end of recovery, but database is missing or does not match attachment info) after 0.203 seconds.
************************** ********** ********** ********** ********** ********
[PS] C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\ data\Sende rReputatio n>eseutil /p pasettings.edb
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating REPAIR mode...
Database: pasettings.edb
Temp. Database: TEMPREPAIR13960.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----| ----|----| ----|----| ----|
.......................... .......... .......... .....
Integrity check successful.
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully in 3.214 seconds.
eseutil /g
Integrity check successful.
eseutil /r /a trn
Operation terminated with error -1216 (JET_errAttachedDatabaseMi
eseutil /p
Integrity check successful.
Source: ESE
Event ID: 494
Description:
edgetransport (12524) Sender Reputation Database: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Source: ESE
Event ID: 454
Description:
edgetransport (12524) Sender Reputation Database: Database recovery/restore failed with unexpected error -1216.
Source: MSExchangeTransport
Event ID: 17007
Description:
Sender Reputation Database: The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport service is shutting down. The exception is Microsoft.Exchange.Isam.Is
at Microsoft.Exchange.Isam.Je
at Microsoft.Exchange.Isam.In
at Microsoft.Exchange.Transpo
I used ESEUTIL to try and fix the database with no success:
**************************
[PS] C:\>eseutil /g "C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating INTEGRITY mode...
Database: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Temp. Database: TEMPINTEG12576.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Integrity check successful.
Operation completed successfully in 0.140 seconds.
**************************
[PS] C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: trn
Log files: <current directory>
System files: <current directory>
Performing soft recovery...
Restore Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
.........X
Operation terminated with error -1216 (JET_errAttachedDatabaseMi
cted at the start or end of recovery, but database is missing or does not match attachment info) after 0.203 seconds.
**************************
[PS] C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating REPAIR mode...
Database: pasettings.edb
Temp. Database: TEMPREPAIR13960.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Integrity check successful.
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully in 3.214 seconds.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found an article that shows how to run eseutil with different switches to try and repair or rebuild the pasettings.edb. At the end of all the steps the author explains that if nothing fixes the issue delete everthing in the SenderReputation folder and restart the Transport Service.
http://exchangeserverpro.com/event-id-454-and-17003-a-corrupt-sender-reputation-database-causes-exchange-server-2007-transport-service-to-stop/
Though this may report success, and further integrity checks show the database to be healthy, you may still find the Microsoft Exchange Transport service will not start. In these cases you can delete the files in C:\Program Files\Microsoft\Exchange Server\TransportRoles\data \SenderRep utation. When the Microsoft Exchange Transport service is next started it will build a new Sender Reputation database
Sembee2 was correct: delete the file and restart the service
http://exchangeserverpro.com/event-id-454-and-17003-a-corrupt-sender-reputation-database-causes-exchange-server-2007-transport-service-to-stop/
Though this may report success, and further integrity checks show the database to be healthy, you may still find the Microsoft Exchange Transport service will not start. In these cases you can delete the files in C:\Program Files\Microsoft\Exchange Server\TransportRoles\data
Sembee2 was correct: delete the file and restart the service
ASKER
I've requested that this question be closed as follows:
Accepted answer: 480 points for Sembee2's comment #a39046058
Assisted answer: 20 points for gkousikan's comment #a39046394
Assisted answer: 0 points for TechAK's comment #a39049908
for the following reason:
I gave all the point to Sembee2 because he was correct, but I did find an answer that explains why in more detail.
Accepted answer: 480 points for Sembee2's comment #a39046058
Assisted answer: 20 points for gkousikan's comment #a39046394
Assisted answer: 0 points for TechAK's comment #a39049908
for the following reason:
I gave all the point to Sembee2 because he was correct, but I did find an answer that explains why in more detail.
“Path of the log files” /d “Path of the database
2.Once the command completes successfully, mount the stores.
You might get this error:
“Operation terminated with error -1216 (JET_errAttachedDatabaseMi
3.To resolve this, run soft recovery with the “/i ” switch at the end and it will override the EDB-STM mismatch.