Re: MTA RPC EVent ID 9318 Comms Error 9297
From: Neal (neal__at__ap0yar_dot_co_dot_nz)
Date: 08/23/04
- Next message: Mark Arnold [MVP]: "Re: Please add delete action to IMF for information store"
- Previous message: Todd: "Re: Exchange 2003 - Administrator Mailbox"
- In reply to: trmbr: "Re: MTA RPC EVent ID 9318 Comms Error 9297"
- Next in thread: trmbr: "Re: MTA RPC EVent ID 9318 Comms Error 9297"
- Reply: trmbr: "Re: MTA RPC EVent ID 9318 Comms Error 9297"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Aug 2004 19:09:38 +1200
Fantastic! I've read it and done what it said, now just watching the
queues, I'll know in a few minutes.
Now how come that info hasn't made it into a KB article?
Hmmm, it didn't work, but I checked the same setting on the other server,
and it had some 'special access' permissions. I matched those on the first
server and now it's working.
Thanks very much for your input, and to the people that put the info on the
site.
Neal.
"trmbr" <trmbr50@hotmail.com> wrote in message
news:cg3mur$hpn$1@si05.rsvl.unisys.com...
> Neal
> Dont give up mate...I came across this web site which has solved my
> problem,
> which is security related based on the ANONYMOUS account requiring
> permissions set as per the following instructions.
>
> See if they apply in your situation - mine was resolved
>
> Regads
> trmbr
> ============================================================================
> =================================
> http://www.larkware.com/Articles/TheDailyGrind125.html
>
> Search for "9297" which resulted in:
>
> So, about those Exchange servers. Two servers, both Exchange 2003 running
> on
> Windows Server 2003 in native Win2K3 AD mode. Every ten minutes server #1
> drops a message in its event log:
>
> MSExchangeMTA event ID 9297:
> An RPC communications error occurred. Unable to bind over RPC. Locality
> Table (LTAB) index: 8, Windows 2000/MTA error code: 9297. Comms error
> 9297,
> Bind error 9297, Remote Server Name PINETREE [MAIN BASE 1 500 %10] (14)
>
> And at the same time server #2 complains:
>
> MSExchangeMTA event ID 9297:
> Calling client thread does not have permission to use MTA RPCs. Windows
> 2000
> error code: 0X80070005. Client user account: NT AUTHORITY\ANONYMOUS LOGON.
> [BASE IL INCOMING RPC 25 237] (14)
>
> And sure enough, machine #1 does have a batch of stuff piled up in
> Exchange
> MTA queues destined for PINETREE, if it could ever it through. Any ideas
> cheerfully accepted.
>
> Update 12/22/03
>
> Well, I finally have a fix for those event log messages. I'm posting this
> update because I get e-mail from 2 or 3 users every month with this exact
> problem. But let me be quite clear: I don't understand why this worked,
> and
> I don't understand the security implications. If you can enlighten us all,
> please leave a comment. Anyhow, based on a newsgroup posting, here's my
> ad-hoc fix:
>
> 1. Run regedit on the computer where you run Exchange System Manager.
> Locate
> the key HKCU\Software\Microsoft\Exchange\ExAdmin. Add a new DWORD value
> named ShowSecurityPage and set its value to 1.
> 2. Run Exchange System Manager and then expand the appropriate
> administrative group, then the server that's posting the 9297 errors, then
> protocols. Right-click the X.400 protocol and select Properties.
> 3. Select the Security tab. Locate the account that's listed in the 9297
> message. Grant this account "Send As" and "Receive As" permission. Click
> OK.
> 4. Restart the Exchange MTA service.
>
>
>
>
>
- Next message: Mark Arnold [MVP]: "Re: Please add delete action to IMF for information store"
- Previous message: Todd: "Re: Exchange 2003 - Administrator Mailbox"
- In reply to: trmbr: "Re: MTA RPC EVent ID 9318 Comms Error 9297"
- Next in thread: trmbr: "Re: MTA RPC EVent ID 9318 Comms Error 9297"
- Reply: trmbr: "Re: MTA RPC EVent ID 9318 Comms Error 9297"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|