Exchange Server 2007 on SBS2008 can not send email either external or internal

I suspect that you have not opened SMTP PORT 25 on the firewall.
Easy way to test it is go to http://www.abuse.net/relay.html and type in your External IP address. If the web page results in a message - Could not connect, test failed.
It would mean that you haven't setup PORT FORWARDING on your router.

As I mentioned before please cofirm if you have setup PORT FORWARDING on the router/firewall correctly-
If it is setup correctly -
1. Open up services.msc and ensure that SMTP SERVICE is started??
2. Use the Windows Small Business Server 2008 Best Practices Analyzer to confirm that nothing is setup incorrectly in the SBS box. http://www.microsoft.com/downloads/details.aspx?familyid=86a1aa32-9814-484e-bd43-3e42aec7f731&displaylang=en

manav
I don't believe exchange 2007 has separate SMTP service as was with 2003; also, senting email out would not be effect by having port 25 open from the outside or port forwarding.

If they are having issues with recieving emails then the port forwarding would be an issue.  Many routers are not setup blocking port 25 going out.

eaglemobiles can you confirm if you are recieving email or just having issues sending?

@PriceD,

1. Ok I have double checked my SBS 2008, you are right about SMTP service.
2. The reason I suggested a FIREWALL is because it seems that the user is having problems SENDING and RECIEVING as well, Although I guess we will wait to see his response as you have already asked now. When you do a SBS install it does take care of SEND CONNECTORS etc. for you so that is why FIREWALL is the first thing that comes to my mind. If he is having problems just sending then it would be a different issue.

Sorry but i dont think that firewall is an issue because the mail just stays in outbox and go no where, even if the users send internal emails.

Restart the exchange services on the hub transport server.send new mail again and try.

Also try sending mail via OWA in exchange https://mail.domain.com/owa and confirm that you can successfully login to OWA and send mails from there.

Windows Small Business Server 2008 Best Practices Analyzer run and all ok

I have restarted exchange and when i use owa it is working fine but emails stays in outbox

It may be a DNS issue.  So the emails stay in the outbox in owa as well?

So emails are stuck in OWA as well. In that case it is most likely your send connector -
Confirm that your send connector is configured properly.
Read this - http://www.petri.co.il/configuring-exchange-2007-send-external-email.htm
Even though this is not required for SBS in general but I think you might need to delete and recreate your SEND CONNECTOR.

@PriceD,

If it was a DNS issue then emails will still hit the exchaneg server not just sit in outbox.

Have you restarted the server totally?  Also, are you recieving emails?

I have restarted the full server yes.

The send connector is now correctly configured but still the same problem.

manav08 incorrect.  Just had the issue with a client couple of days ago.  The DNS updates expired on the DNS server, client would not connect to the exchange server, mail sits in the outbox on client until it can connect to the server.

Did you have to change something on the connector.  If so, with all MS products, when you make a change.  Restart.

I think it looks like a dns issue rather thann exhcange

If you think it is a DNS do the following.  Go the the hosts file, you will fine this on any client.  C:\windows\system32\drivers\etc
You will see an entry that are something like 127.0.0.1    localhost, go under that entry and type in your internal ip address of the exchange server and under localhost type in the FQDN of the exchange server.  save and see if it works.
Normally, if this is the issue you would not beable to recieve either...but try it just to make sure it is not a client hitting the DNS issue.

Oh, do you happen to have a virus scanner on your server.  Like McAfee.

I cannot find any file called 12.0.0.1 all i can find is hosts which has the following entries.


# Copyright (c) 1993-2006 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

127.0.0.1       localhost
::1             localhost

There is  no anti virus

The file is called hosts with no extension.

The screen shot is the file you want to edit.  Just add under the last line the IP address of the exchange server (then tab over once) and type in the FQDN (basically whatever you type in when you setup outlook and the name you enter for the exchange server)

I get the following error in owa as well

Client Information
------------------
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
CPU Class: x86
Platform: Win32
System Language: en-gb
User Language: en-gb
CookieEnabled: true
Mime Types:

Exception Details
-----------------
Date: Sat Sep 12 05:28:11 UTC 2009
Message: 'gtLV' is null or not an object
Url: http://78.86.121.110/owa/8.1.240.5/scripts/premium/clistview.js
Line: 39

Call Stack
----------
onFcsInLV()


Dump Event
----------
 recordset = null
 type = error
 fromElement = null
 toElement = null
 altLeft = false
 keyCode = 0
 repeat = false
 reason = 0
 data =
 behaviorCookie = 0
 source = null
 contentOverflow = false
 behaviorPart = 0
 url =
 dataTransfer = null
 ctrlKey = false
 shiftLeft = false
 dataFld =
 returnValue = undefined
 qualifier =
 wheelDelta = 0
 bookmarks = null
 button = 0
 srcFilter = null
 nextPage =
 cancelBubble = false
 x = 0
 y = 0
 srcElement = null
 screenX = 344
 screenY = 232
 srcUrn =
 origin =
 boundElements = [object]
 clientX = 166
 clientY = 49
 propertyName =
 shiftKey = false
 ctrlLeft = false
 offsetX = 0
 offsetY = 0
 altKey = false
 errorMessage = 'gtLV' is null or not an object
 errorUrl = http://78.86.121.110/owa/8.1.240.5/scripts/premium/clistview.js
 errorLine = 39
 errorCharacter = 22
 errorCode = 0

Is it IE8 you are using?  when does this error appear

yes it is ie8

@PriceD - I disagree with the DNS issue but go ahead wwith the troubleshooting.
@eaglemobiles - I have to step out for a few hours, i hope PriceD should help you resolve the issue until then.

and when do you get this error.  Logging into owa, after trying to send.  And did this error just start.

no i can login to owa check emails etc but when send emails thats what really happend. get the above error message and the message goes into outbox

I think that might be a JAVA issue.  do you have Java, or the lastest version installed?

what about the outlook clients, other then sitting in the outbox; any other errors?   Also, can you recieve messages.  Regarding you ISP, do you have a static external IP address?

@eaglemobiles and @PriceD,

Eaglemobiles you need to confirm if it is only one client experiencing the problem or all clients.
If it is some clients then it can be a DNS issue otherwise not.
Please do an "ipconfig /all" on your server and workstation and post the results here for PriceD to analyse it better.

all users including admin have same problem, also what i want first to make this working intenrally but it is not even workign internally, once it is working internally i wil sort out the rest.
let me make it clear what is the problem:
i can log in via owa from any computer without any problem, but cant send or reciview emails either via outlook and via owa. i dont know what is the problem.

manav08 I have to leave this in your capiable hands....it has just hit 2:36AM here on the east coast and I have to get up at 7 to build a deck for my wife...have to get some zzzzzs

eaglemobiles,

OK I am back. Let me get this straight

1. No problem accessing owa from any machine on the network.
2. Whether outlook 2007 used or OWA messages just get stuck in Outbox.
3. Problem is only when sending emails. Recieving works fine.
4. Client machine can ping server by its name eg. ping Server OR by FQDN i.e. server.domain.local

Please confirm first of all if I am correct in saying this or not. If I am the next set of things I want you to check -

1. Check the event logs on the Server and please post all error messages/warning that are there.
2. Now go to Start -> Control -> Network Connections and the LOCAL AREA CONNECTION. Right-click LAN and confirm to me what the IP ADDRESS, SUBNET MASK, DEFAULT GATEWAY and DNS is. Also confirm that you haven't disabled IPV6 in your LAN properties. THIS IS VERY IMPORTANT.

every thing is except i got the following message in event log


Log Name:      Application
Source:        MSExchangeMailSubmission
Date:          12/09/2009 13:26:00
Event ID:      1009
Task Category: MSExchangeMailSubmission
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      APEXHOUSINGSBS.apexhousing.local
Description:
The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeMailSubmission" />
    <EventID Qualifiers="32772">1009</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-09-12T12:26:00.000Z" />
    <EventRecordID>6381</EventRecordID>
    <Channel>Application</Channel>
    <Computer>APEXHOUSINGSBS.apexhousing.local</Computer>
    <Security />
  </System>
  <EventData>
  </EventData>
</Event>

Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'.
   Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'. ---> System.ArgumentException: Invalid agent assembly path. --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup) at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath) at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load()

First of all have a look at this post and do as suggested. We will go from there - http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=1009&EvtSrc=MSExchangeMailSubmission&LCID=1033

Also I suggest running Microsoft Exchange Best Practice Analyzer.
1. Open up Exchaneg Management Console
2. Click on Toolbox
3. Double-click BEst Practices Analyser
4. Check for updates so that it is updated
5. Run the tool and it will notify you all the problems with the exchange setup.

This is a very powerful tool. Do the fixes as suggested by it. Hopefully this will resolve your problem.

Do all the available scans EXCEPT the ones that say they will take over 2 hours.

This is the main problem

Log Name:      Application
Source:        MSExchangeTransport
Date:          12/09/2009 14:07:09
Event ID:      16023
Task Category: Configuration
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      APEXHOUSINGSBS.apexhousing.local
Description:
Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'. ---> System.ArgumentException: Invalid agent assembly path.
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup)
   at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath)
   at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="49156">16023</EventID>
    <Level>2</Level>
    <Task>16</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-09-12T13:07:09.000Z" />
    <EventRecordID>6403</EventRecordID>
    <Channel>Application</Channel>
    <Computer>APEXHOUSINGSBS.apexhousing.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'.</Data>
    <Data>Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'. ---> System.ArgumentException: Invalid agent assembly path.
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup)
   at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath)
   at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load()</Data>
  </EventData>
</Event>

2 Steps I would try -

1. go to properties of C:\Program Files\Microsoft\Exchange Server\Transport Roles folder and confirm that Network Service account has permissions - Read and Execute, List Folder Contents, Read, Write, Special Permissions and it is set to be inhertited by child objects. Once you have made sure that this is the case restart the "Microsoft Exchange Transport" service and investigate if error comes up again in event viewer. Try the next step only if this doesn't work.

2. Antigen is part of Forefront Security. Did you install Forefront security as part of your SBS. If yes, I would recommend uninstalling it . If for some reason the uninstall doesn't work, try reinstalling at and then uninstalling it.

i have done still errors coming up in the event log and no there is no security installed

eaglemobiles,

Did you get this sorted. Did you try my suggestions in the above post?