1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

(Resolved) Exchange Server 5.5 -- MSExchangeMTA

Discussion in 'All Other Software' started by kathleenb, Nov 5, 2002.

Thread Status:
Not open for further replies.
Advertisement
  1. kathleenb

    kathleenb Thread Starter

    Joined:
    Feb 28, 2001
    Messages:
    9
    I receive Error message 2140 (An internal Windows NT error
    occurred) when attempting to start the MSExchangeMTA
    service. In looking in the Event Viewer, it gives me the
    following error:
    Event ID: 9400
    Category: Field Engineering
    A fatal MTA error has occurred. The file SCT.INP could
    not be opened. [BASE MAIN BASE 1] (16)

    I replaced the sct.inp with the original file from CD...
    no luck. I re-ran SP4... no luck. I ran mtacheck.exe....
    no luck.

    As such... no incoming/outgoing mail!
     
  2. Rockn

    Rockn

    Joined:
    Jul 29, 2001
    Messages:
    21,334
    Sounds like a corrupt file in the \Exchsrvr\Mtadata directory. Replace all the files in this directory from the CD, but once you do remove the read only attribute from them.
     
  3. kathleenb

    kathleenb Thread Starter

    Joined:
    Feb 28, 2001
    Messages:
    9
    I did replace all files within the MTA folder, except the .dat files... removed the "read-only" attribute and re-ran the Exchange SP4. It still didn't work... I still get the message that it cannot open sct.inp.
     
  4. Rockn

    Rockn

    Joined:
    Jul 29, 2001
    Messages:
    21,334
    It's also possible that one of the dat files is corrupt. I used to have this problem on an almost weekly basis before a SP update.
     
  5. kathleenb

    kathleenb Thread Starter

    Joined:
    Feb 28, 2001
    Messages:
    9
    Seems to me I read somewhere within the MS Knowledgebase that removing dat files (which are associated with edb) can create havoc. I'm thinking I may need to completely remove and reinstall Exchange.
     
  6. Rockn

    Rockn

    Joined:
    Jul 29, 2001
    Messages:
    21,334
    Sorry I am not more help. Have you checked all of the Exchange services to see if they are all started?
     
  7. kathleenb

    kathleenb Thread Starter

    Joined:
    Feb 28, 2001
    Messages:
    9
    After much research... too much actually... I ended up uninstalling Exchange, installing a clean version and restoring the database. It works fine now. One idea that was presented to me (after I uninstalled the program) was that the problem could have been caused by either a corrupt or over-sized message in the in/out queues... should I run into this problem again in the future... I will definitely check out the queues first!
     
  8. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/102732

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice