Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Easy way to Resolve Exchange Transport Error Event 17003

Paul Ryan | March 28th, 2015 | general

In this blog we are going to discuss Exchange Error 17003 that normally occurs when the Transport layer of Exchange Server does not work properly. The same error may also pop up due to the Corrupted ESE.

error 1

Explanation of the Error code 17003

The error generally occurs due to the corruption in Extensible Storage Engine (ESE) and this prevents the Exchange Transport Service from being started.

In fact, ESE (Extensible Storage Engine) is a Message Queue database or Content filtering database which may exist on the Hub Transport Server or Edge Transport Server.

exchange-recovery-new

You can find the Message queue database and Transitions logs  at the location given below.

error 2

QueueDatabasePath parameter present in the EdgeTransport.exe.config is used to control the location of Message Queue Database.

QueueDatabaseLogginPath parameter present in the EdgeTransport.exe.config is used to control the location of Message Queue Transaction logs.

Possible Resolution on the Error 17003

  • To resolve the error, the simple thing to do is delete the database with its corresponding logs. As you delete the database, a fresh copy will be automatically created by the System.
  • You can also repair the database by using PowerShell Commands.

Conclusion:

So in this blog we have discussed the main possible causes of the “error 17003”. In case if you are facing any difficulty while repairing the error, Please leave a comment, We will solve your query as soon as possible.

The following two tabs change content below.

Paul Ryan

Paul Ryan is a technical blogger and he’s passionate about writing technical blogs and covering all popular issues related to Exchange server / Outlook apps. He is MCSE certified and putting all his knowledge and experience in providing solutions to the Exchange users/administrators.