RE: Message Delivery Failure on Incoming

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Tks Brandy
1. We are SMTP.
2. Logging enabled as detailed.
3. A few log events are pasted below. I doubt these are relevant. I don't
know how to "reproduce the issue" as the problem is with inbound emails and
we never get to see them. I don't know if any have been bounced in the last
24-hours. I'll keep monitoring events and see if something more relevant
comes up.
System Events:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 03/06/05
Time: 18:02:18
User: IMPEXIS\thor
Computer: SERVER1
Description:
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-BF92-0060081ED811}

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


Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 03/06/05
Time: 18:02:18
User: IMPEXIS\thor
Computer: SERVER1
Description:
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-BF92-0060081ED811}

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

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 03/06/05
Time: 18:03:09
User: IMPEXIS\thor
Computer: SERVER1
Description:
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-BF92-0060081ED811}

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


Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 3019
Date: 03/06/05
Time: 18:04:59
User: N/A
Computer: SERVER1
Description:
The redirector failed to determine the connection type.

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


APPLICATION LOGS:

Event Type: Information
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 6020
Date: 03/06/05
Time: 16:01:24
User: N/A
Computer: SERVER1
Description:
Categorizer is using LDAP server Host: "server1.Impexis.local", Port: 3268,
Base priority: 0, Bind type: 3, Naming Context: "", Account: ""

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

Event Type: Information
Event Source: MSExchangeTransport
Event Category: Routing Engine/Service
Event ID: 969
Date: 03/06/05
Time: 16:03:19
User: N/A
Computer: SERVER1
Description:
This master server received a base level (Routing group) call back. However
no DS change has been detected and no user version increase will occur as a
result. This should not result in reset route or updated routing packets
being sent out to its subordinate servers and neighboring routing groups.

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


THIS ONE IS ODD, AS I DIDN'T DO THIS!
Event Type: Information
Event Source: MSExchangeIS
Event Category: General
Event ID: 9661
Date: 03/06/05
Time: 16:03:19
User: N/A
Computer: SERVER1
Description:
The Unsolicited Commercial Email default filter level has been updated. The
new value is 7.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Information
Event Source: MSExchangeTransport
Event Category: Routing Engine/Service
Event ID: 973
Date: 03/06/05
Time: 16:03:19
User: N/A
Computer: SERVER1
Description:
On Master side, the following connector's linkstate is up. Process Id: 1768
Process location: C:\WINDOWS\system32\inetsrv\inetinfo.exe ConnectorDN:
CN=SmallBusiness SMTP connector,CN=Connections,CN=first routing
group,CN=Routing Groups,CN=first administrative group,CN=Administrative
Groups,CN=IMPEXIS,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=Impexis,DC=local

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

ENOUGH FOR TONIGHT!

Any use?

""Brandy Nee [MSFT]"" wrote:

> Hello MTV,
>
> Thank you for posting back.
>
> Please see my information below:
>
> 1. What is the type of email account you currently use, SMTP, HTTP or
> Exchange account?
>
> 2. Enable the SMTP logging.
>
> a) Go to Server Management\Advanced
> Management\Yourserver(Exchange)\Administrative Groups\First Administrative
> Groups\Servers\Yourserver\Protocols\SMTP.
>
> b) Right click Default SMTP Virtual Server, and go to Properties.
>
> c) Check the box Enable Logging, the default SMTP protocol log format is
> the W3C Extended Log File Format, and Click OK.
>
> 3. Please collect Event Log:
>
> a) On the server, go to the Exchange System Manager.
>
> b) Expand to Yourserver(Exchange)\Servers\Yourserver.
>
> c) Right click Yourserver, go to Properties, and select Diagnostics Logging.
>
> d) In the Services Console, highlight MSExchangeTransport, then click each
> Category which are displaying in the Categories Console, change the Logging
> level from None to Maximum.
>
> e) Reproduce the issue.
>
> f) Run "eventvwr" and paste all the related issue to the Newsgroup.
>
> For more detailed information, please see the following KB article:
>
> 821910 How to troubleshoot for Exchange Server 2003 transport issues
> http://support.microsoft.com/?id=821910
>
> 4. 127.0.0.1 is your localhost IP address. The SmallBusiness SMTP
> Connector's name space which is "*", it does not mean relay. It is the by
> default setting which means all outbound emails are delivered through this
> connector.
>
> Please take your time to collect all the error information and paste the
> full content of the information to the Newsgroup. I am looking forward to
> hearing from you.
>
> Best regards,
>
> Brandy Nee
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.



Relevant Pages

  • Re: Login Errors Seem to indicate we are being hacked?
    ... As an example, my Sonicwall keeps a log that I can read from the regular UI, as well as having the ability to report to a syslog server or e-mail out the log info. ... thing on the box using that authentication package. ... The SMTP or IIS logs should answer everything. ... I'm not familiar with that particular router or its logging capabilities, ...
    (microsoft.public.windows.server.sbs)
  • Re: ASP.Net V 2.0 problems with sending email
    ... Presumably it is trying to deliver it from the web server, ... parties smtp server. ... I suggest you try turn on the network Tracing asMischa has suggested. ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.Net V 2.0 problems with sending email
    ... Presumably it is trying to deliver it from the web server, ... parties smtp server. ... I suggest you try turn on the network Tracing asMischa has suggested. ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Login Errors Seem to indicate we are being hacked?
    ... I have turned on diagnostic logging on SMTP. ... we could turn something off on our own SMTP server to stop the devils from ... Caller User Name: SERVER01$ ...
    (microsoft.public.windows.server.sbs)
  • Re: NDR delivery delayed errors keep coming, any advice?
    ... I have turned on the logging as you requested, and when I get a DNR 4.4.7, I ... The sending server tried to ... Delivery status notifications in Exchange Server and in Small Business ... The SMTP logging files are located in ...
    (microsoft.public.windows.server.sbs)