Re: EdgeTransport.exe - Constant High CPU utilisation

Hi

Whilst I appreciate that this may solve the problem, I don't really see why
I should need to do this. The OS was only set up this week, I installed
Exchange EdgeTransport in the standard way, applied the updates, installed
the service pack, installed Forefront which is part of the installation
process. I then set up the routing and have done close on nothing else to
the server. Surely if I go through that whole process again I will only end
up with the same situation?

I have just been adding monitoring to the edgeTransport server and have now
noticed the following though.
- When it starts up the process sits at close on 0%
- After some time (no exact pattern here) the process jumps to 25%, and then
later to 50%. I have stopped it at this point, so possibly it could continue
to 100% which may have previously happened.
- What seems like around the same time (struggling to match up exactly the
alerts with the jumps in CPU and the event logs) I am receiving a warning in
the Event logs.

Event Type: Warning
Event Source: MSExchange Extensibility
Event Category: MExRuntime
Event ID: 1050
Date: 9/26/2007
Time: 5:56:55 PM
User: N/A
Computer: MAILFILTER
Description:
The execution time of agent 'Attachment Filtering Agent' exceeded 300000
(milliseconds) while handling event 'OnEndOfData'. This is an unusual amount
of time for an agent to process a single event. However, Transport will
continue processing this message.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Does this maybe shed some light on what could be the problem?

Regards,

Matthew ORiordan
Lemon Foundation
http://www.lemonfoundation.com/


"Mark Arnold [MVP]" wrote:

On Wed, 26 Sep 2007 05:46:02 -0700, Matthew ORiordan
<MatthewORiordan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Thanks for your feedback, however, can you answer the following.

If I remove SP1 from this Edge Server, will it continue to operate correctly
with the Exchange 2007 server which has SP1, or do I have to roll back both?

Also, is there a way to disable Forefront rather than completely uninstall
it? This is all just time consuming to get everything to this point so
trying to reduce time installing & uninstalling if there is a quicker way.

Since it's a lab I suggested you format the box and start again,
especially since it's just an Edge and isn't tied in horribly to AD.
All you have to do is to terminate the subscription and do another one
when you've installed the box again.
Windows 2003 SP2 and Exchange 2007 RTM. Make sure everything is
working fine with ForeFront and then back the box up before putting
the Exchange 2007 SP1 back on.

.

Relevant Pages

  • Re: Outgoing POP3 email missing/lost/not received
    ... This event was in the SBS Server Event Logs, ... All of my accounts by default had a X.400 account which exchange ... management have internet email addresses through the local ISP as ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Organisation Name ?
    ... How to configure an account to use the ExMerge utility in Exchange 2000 ... Server and in Exchange Server 2003 ... I'm not an expert on LegacyDN, but I e-mailed some of the other SBS MVPs ... The setup that I'm talking about is the standard full installation ...
    (microsoft.public.windows.server.sbs)
  • Re: 452 4.3.1 Out of memory?
    ... It also occurs when SMTP and Exchange was not ... Check the SMTP Server Configuration. ... After the installation the SBS server, ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA wont work after re-installation
    ... The HTTP identity of the Web Site, make sure external requests are directed ... Assigned the new ip to the " Web Mail " virtual server ... from Exchange System Manger and site from IIS." ... WINS, Simple TCP/IP Services, Remote installation services, Terminal ...
    (microsoft.public.exchange2000.connectivity)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... SBS 2008 does include the option during installation, to install fresh or to perform a migration installation, which allows you to introduce it into an existing SBS 2003 organizations. ... Windows Small Business Server 2008 Unleashed ... Since exchange defaults to accepting ... IF, after a week, you are still seeing some connections, try *DISABLING* ...
    (microsoft.public.windows.server.sbs)