451 4.4.0 DNS query failed - NonExistentDomain

I am in the process of migrating from Exch 2007 to 2013 for a small company. It is a very simple setup of just a single domain which has
1 server, 1 organization and 1 database. Here is what I have done so far: 
1. Installed a physical server EX13 for Exchange 2013 with SP1. All updates have been applied. 
2. Added a new Receive Connector of EX13 in addition to existing EX07. 
3. Changed SMTP port forwarding on the firewall from EX07 to EX13. 
4. Migrated a few mailboxes to the EX13. 
Accounts on both servers have no issues with exchanging email both ways on the Internet. However, when accounts on the old server email to
migrated users, the new server does not always receive the messages promptly. There is a delay as much as 30 minutes that happens sporadically.
I checked the message header on the delayed messages and found that they had been stuck in EX07 for a long time before forwarding to EX13.
From Ex07 queue viewer, I found the following error: 
451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain; nonexistent domain 
Net Hop Domain: hub version 15 
Delivery type: SMTP Relay in Active Directory 
Message Source Name: FromLocal 
Last Error: 451 4.4.0 DNS query failed. The error was: SMTPSEND.dns.NonExistentDomain;nonexistentdomain 
The status showed "retry" and eventually the message would be delivered. Once it went through, I sent another one again from an EX07
account to EX13 account, the message was received instantly. 
So far I have tried the following: 
1. Added a host entry to point EX13.my_external_domain.com to the internal address of EX13 
2. Added an 'A' record on the internal DNS server with the same entry. 
3. Verified that EX13.my_external_domain.com was accessible from EX07 using this FQDN. 
4. Removed EX07 and leaving only EX13 on the Receive Connector list 
5. Removed EX13 and leaving only EX07 on the Receive Connector list 
6. Put both connectors back 
There is no change of status. Every morning our users are saying that they could not email users on the new server. Then after 30 minutes,
the problem disappeared but it will come back later in the day. On the other hand, users on the new server do not notice any delay when sending messages to the those on the new box. At this point, I don't feel comfortable migrating more users. Can someone
please shed some lights?

As suggested by Cara, I queried the message logs of both servers to track the delayed message.  This time, it took an hour for a message to be delivered.
========================================
Message Log on Sending Server EXCH07
========================================
[PS] C:\Windows\system32>get-messagetrackinglog -messagesubject "exch07-user1 to
 exch13-user1" | fl
Timestamp               : 3/28/14 2:18:00 PM
ClientIp                : fe80::a5d8:d604:af26:37a9
ClientHostname          : EXCH07.contoso.local
ServerIp                : fe80::a5d8:d604:af26:37a9%10
ServerHostname          : EXCH07
SourceContext           :
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : RECEIVE
InternalMessageId       : 4106
MessageId               : <CC47D79927E02645940E84883BD0D909F58F56E607@TO-EXCHAN
                          GE.contoso.local>
Recipients              : {[email protected]}
RecipientStatus         : {}
TotalBytes              : 3897
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
MessageInfo             : 04I:
Timestamp               : 3/28/14 3:12:02 PM
ClientIp                : 2002:960a:116::960a:116
ClientHostname          : EXCH07
ServerIp                : 2002:960a:125::960a:125
ServerHostname          : EXCH13.contoso.local
SourceContext           : 08D1189FA5E0283C
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 4106
MessageId               : <CC47D79927E02645940E84883BD0D909F58F56E607@TO-EXCHAN
                          GE.contoso.local>
Recipients              : {[email protected]}
RecipientStatus         : {250 2.1.5 Recipient OK}
TotalBytes              : 4337
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
MessageInfo             : 3/28/14 2:18:00 PM
Timestamp               : 3/28/14 3:40:22 PM
ClientIp                : fe80::a5d8:d604:af26:37a9
ClientHostname          : EXCH07.contoso.local
ServerIp                : fe80::a5d8:d604:af26:37a9%10
ServerHostname          : EXCH07
SourceContext           :
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : RECEIVE
InternalMessageId       : 4685
MessageId               : <CC47D79927E02645940E84883BD0D909F58F56E608@TO-EXCHAN
                          GE.contoso.local>
Recipients              : {[email protected]}
RecipientStatus         : {}
TotalBytes              : 3905
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1-1
Sender                  : [email protected]
ReturnPath              : [email protected]
MessageInfo             : 04I:
Timestamp               : 3/28/14 4:34:27 PM
ClientIp                : 2002:960a:116::960a:116
ClientHostname          : EXCH07
ServerIp                : 2002:960a:125::960a:125
ServerHostname          : EXCH13.contoso.local
SourceContext           : 08D1189FA5E0295D
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 4685
MessageId               : <CC47D79927E02645940E84883BD0D909F58F56E608@TO-EXCHAN
                          GE.contoso.local>
Recipients              : {[email protected]}
RecipientStatus         : {250 2.1.5 Recipient OK}
TotalBytes              : 4345
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1-1
Sender                  : [email protected]
ReturnPath              : [email protected]
MessageInfo             : 3/28/14 3:40:22 PM
Timestamp               : 3/28/14 2:18:00 PM
ClientIp                : fe80::a5d8:d604:af26:37a9%10
ClientHostname          : EXCH07
ServerIp                :
ServerHostname          : EXCH07
SourceContext           : MDB:caef6319-6c43-4f5e-8b42-34b112a9f6a4, Mailbox:589
                          783a4-b411-45d8-b359-23095d3cd24d, Event:114759020, M
                          essageClass:IPM.Note, CreationTime:2014-03-28T18:17:5
                          9.653Z, ClientType:OWA
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : SUBMIT
InternalMessageId       :
MessageId               : <CC47D79927E02645940E84883BD0D909F58F56E607@TO-EXCHAN
                          GE.contoso.local>
Recipients              : {}
RecipientStatus         : {}
TotalBytes              :
RecipientCount          :
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              :
MessageInfo             :
Timestamp               : 3/28/14 3:40:22 PM
ClientIp                : fe80::a5d8:d604:af26:37a9%10
ClientHostname          : EXCH07
ServerIp                :
ServerHostname          : EXCH07
SourceContext           : MDB:caef6319-6c43-4f5e-8b42-34b112a9f6a4, Mailbox:589
                          783a4-b411-45d8-b359-23095d3cd24d, Event:114778671, M
                          essageClass:IPM.Note, CreationTime:2014-03-28T19:40:2
                          1.777Z, ClientType:OWA
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : SUBMIT
InternalMessageId       :
MessageId               : <CC47D79927E02645940E84883BD0D909F58F56E608@TO-EXCHAN
                          GE.contoso.local>
Recipients              : {}
RecipientStatus         : {}
TotalBytes              :
RecipientCount          :
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1-1
Sender                  : [email protected]
ReturnPath              :
MessageInfo             :
========================================
Message Log on Sending Server EXCH07
========================================
[PS] C:\Users\administrator.contoso\Desktop>get-messagetrackinglog -messagesubject "exch07-user1 to exch13-user1" | fl
RunspaceId              : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp               : 3/28/2014 3:12:01 PM
ClientIp                :
ClientHostname          :
ServerIp                :
ServerHostname          : EXCH13
SourceContext           : No suitable shadow servers
ConnectorId             :
Source                  : SMTP
EventId                 : HAREDIRECTFAIL
InternalMessageId       : 1236950581391
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {}
TotalBytes              : 5337
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[DeliveryPriority, Normal]}
RunspaceId              : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp               : 3/28/2014 3:12:02 PM
ClientIp                : 2002:960a:125::960a:125
ClientHostname          : EXCH13.contoso.local
ServerIp                : 2002:960a:125::960a:125
ServerHostname          : EXCH13
SourceContext           : 08D1189F8F482FF4;2014-03-28T19:09:18.823Z;0
ConnectorId             : EXCH13\Default EXCH13
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 1236950581391
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {}
TotalBytes              : 5337
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
Directionality          : Originating
TenantId                :
OriginalClientIp        : 2002:960a:116::960a:116
MessageInfo             : 0cI:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, EXCH13.contoso.local], [ProxiedClientIPAddress, 65.114.181.16],
                          [ProxiedClientHostname, qw01016.businesswatchnetwork.com], [ProxyHop1,
                          EXCH13.contoso.local(2002:960a:125::960a:125)], [DeliveryPriority, Normal]}
RunspaceId              : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp               : 3/28/2014 3:12:02 PM
ClientIp                :
ClientHostname          : EXCH13
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : AGENT
EventId                 : AGENTINFO
InternalMessageId       : 1236950581391
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {}
TotalBytes              : 5337
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
Directionality          : Originating
TenantId                :
OriginalClientIp        : 2002:960a:116::960a:116
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[CompCost, |ETR=0], [DeliveryPriority, Normal]}
RunspaceId              : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp               : 3/28/2014 3:12:38 PM
ClientIp                : 2002:960a:125::960a:125
ClientHostname          : EXCH13
ServerIp                : 2002:960a:125::960a:125
ServerHostname          : EXCH13.contoso.local
SourceContext           : 08D1189F8F482FFC;250 2.0.0 OK;ClientSubmitTime:2014-03-28T18:17:59.590Z
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 1236950581391
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {250 2.1.5 Recipient OK}
TotalBytes              : 6130
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             : 2014-03-28T18:18:00.077Z;LSRV=EXCH13.contoso.local:TOTAL=36|QDM=35
MessageLatency          : 00:54:38.1220000
MessageLatencyType      : LocalServer
EventData               : {[E2ELatency, 3278], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
                          Opportunistic], [DeliveryPriority, Normal]}
RunspaceId              : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp               : 3/28/2014 3:12:38 PM
ClientIp                :
ClientHostname          : EXCH13.contoso.local
ServerIp                :
ServerHostname          : EXCH13
SourceContext           : 08D1189F97D8A52F;2014-03-28T19:12:38.090Z;ClientSubmitTime:2014-03-28T18:17:59.590Z
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : DELIVER
InternalMessageId       : 1236950581391
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {}
TotalBytes              : 6130
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : EXCH07-USER1 to EXCH13-USER1
Sender                  : [email protected]
ReturnPath              : [email protected]
Directionality          : Originating
TenantId                :
OriginalClientIp        : 2002:960a:116::960a:116
MessageInfo             : 2014-03-28T18:18:00.077Z;SRV=EXCH13.contoso.local:TOTAL=0;SRV=EXCH13.contoso.lo
                          cal:TOTAL=35|QDM=35;SRV=EXCH13.contoso.local:TOTAL=0
MessageLatency          : 00:54:38.1220000
MessageLatencyType      : EndToEnd
EventData               : {[MailboxDatabaseName, Mailbox Database 1497118588], [Mailboxes,
                          43a77dd2-c8bb-4b4c-804c-e761b15da654], [E2ELatency, 3278], [DeliveryPriority, Normal]}

Similar Messages

  • 451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain

    Hi,
    I have two Exchange 2010 servers running on Windows 2008 Ent R2.
    These mail servers have been running fine for a few years.
    Today I noticed two things.
    1. users were telling me they were having delays receiving emails from outside of our own domain. The mail gets sent out, but it takes about 15-30 mins for users outside our our domain to get their mail. Mail sent from inside our domain gets delivered right
    away.
    2. An error message that I see when I go to Tools->Queue Viewer in EMC. The error is: 451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain. This error  shows up when you click on the "Queues" tab and then look at the
    "hub version 14" under "next hop domain" column. 
    I'm assuming these two things are related. I don't understand why the problem is just showing up now. As I said, mail delivery has been fine for a while and I haven't done any major updates to the server in a few months.
    Thanks for any ideas and suggestions as to what might be causing it and where I can look.
    Mike

    Hi,
    1. I replaced my Cert with the same exact cert from GoDaddy, just an updated expire date.
    2. We have two exchange servers.
    3. The message I am seeing now, is under "Last Error" for every queue (not individual messages).
    That error message is:  451 4.4.0 Primary Target IP address responded with 421 4.2.1 Unable to connect. Attempted failover to alternate host but that did not succeed.
    OR
    451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain. (This is the same error I mentioned earlier.
    I ran some tests on mxmailbox.com for my domain name.I got the following alerts back when running a DNS check.
    SOA Serial Number format is invalid. ns.rackspace.com Serial XXXXXXXX : Suggested serial format year was 1402 which is before 1970
    AND
    SOA Expire value out of recommended range.  ns.rackspace reported Expire 604800. Expire is recommeded to be between 1209600 and 2419200
    I use Rackspace DNS servers for External lookups.
    Does this point my mail delay problem to Rackspace or something local on my own machine?
    Thanks!
    Mike

  • Exchange 2013 - 451 DNS query failed with error ErrorTimeout

    Hi all, I know that there are many similar topics in forum, but  my problem is a bit different.
    My environment : Exchange Server 2013 (Windows Server 2008 R2 Ent) , Domain Controller + DNS (Windows Server 2008 R2 Ent) . EX Server uses DC as preferred DNS Server .
    Sometimes, I cannot send email to customers / people of some domains, I get error in my MS Outlook :
    Delivery is delayed to these recipients or groups:
    [email protected]
    [email protected]
    Subject: *****
    This message hasn't been delivered yet. Delivery will continue to be attempted.
    The server will keep trying to deliver this message for the next 1 days, 22 hours and 52 minutes. You'll be notified if the message can't be delivered by that time.
    Diagnostic information for administrators:
    Generating server: ex.mydomain.com
    [email protected]
    Remote Server returned '400 4.4.7 Message delayed'
    [email protected]
    Remote Server returned '400 4.4.7 Message delayed'
    Original message headers:
    Then I open Exchange Toolbox ==> Queue Viewer, what I see about messages which are sent to customerdomain.com :
    From Exchange Server command promt, I can query dns
    nslookup
    Default Server: mydc.mydomain.com
    Address: 192.168.10.2
    > set type=mx
    > customerdomain.com
    Server: mydc.mydomain.com
    Address: 192.168.10.2
    Non-authoritative answer:
    customerdomain.com MX preference = 0, mail exchanger = aspmx.l.google.com
    customerdomain.com MX preference = 5, mail exchanger = alt1.aspmx.l.google.com
    customerdomain.com MX preference = 5, mail exchanger = alt2.aspmx.l.google.com
    customerdomain.com MX preference = 10, mail exchanger = aspmx2.googleemail.com
    customerdomain.com MX preference = 10, mail exchanger = aspmx3.googleemail.com
    aspmx.l.google.com internet address = 74.125.200.27
    I can telnet to their mx server port 25 (of course they use gmail hosting) and send email to [email protected] normally.
    It just happen sometimes, with some domain (I can send/receive email with customerdomain.com normally before).
    How can I fix it ?

    Hi all,
    I think the problem because "DNS Suffix" ? although I uncheck "Append parent suffix of the primary DNS suffix" under Advanced TCP/IP Setting of network interface. Please see this:
    When I query by using dns client on DNS server:
    C:\Users\Administrator>nslookup
    Default Server: ad.mydomain.com
    Address: 192.168.0.3
    > gmail.com
    Server: ad.mydomain.com
    Address: 192.168.0.3
    Non-authoritative answer:
    Name: gmail.com
    Addresses: 2404:6800:4005:802::1015
    173.194.127.86
    173.194.127.85
    > set type=mx
    > gmail.com
    Server: ad.mydomain.com
    Address: 192.168.0.3
    Non-authoritative answer:
    gmail.com MX preference = 10, mail exchanger = alt1.gmail-smtp-in.l.google
    .com
    gmail.com MX preference = 30, mail exchanger = alt3.gmail-smtp-in.l.google
    .com
    gmail.com MX preference = 20, mail exchanger = alt2.gmail-smtp-in.l.google
    .com
    gmail.com MX preference = 5, mail exchanger = gmail-smtp-in.l.google.com
    gmail.com MX preference = 40, mail exchanger = alt4.gmail-smtp-in.l.google
    .com
    alt1.gmail-smtp-in.l.google.com internet address = 173.194.72.26
    alt2.gmail-smtp-in.l.google.com internet address = 74.125.25.26
    gmail-smtp-in.l.google.com internet address = 74.125.68.27
    alt4.gmail-smtp-in.l.google.com AAAA IPv6 address = 2607:f8b0:4001:c07::1b
    When I query by using command promt on DNS server, but point the dns server to 8.8.8.8:
    C:\Users\Administrator>nslookup
    Default Server: ad.mydomain.com
    Address: 192.168.0.3
    > server 8.8.8.8
    Default Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    > gmail.com
    Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    Non-authoritative answer:
    Name: gmail.com.mydomain.com
    Address: 187.26.231.129
    > set type=mx
    > gmail.com
    Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    itl.com
    primary name server = ns1.netnames.net
    responsible mail addr = hostmaster.netnames.net
    serial = 2011071103
    refresh = 10800 (3 hours)
    retry = 1800 (30 mins)
    expire = 3600000 (41 days 16 hours)
    default TTL = 21600 (6 hours)
    It append mydomain.com into query, I configured my dns server forward to 8.8.8.8

  • Queue Problems - 451 4.4.0 DNS Querry Error

    Our Current set up:
    Server1: Hubtransport, Mailbox Server
    Server2: CAS, Hubtransport server
    Server3: Exchange 2k3 mailbox server
       Our issue is we are unable to send email to a specific domain. It doesn't matter if the person sending the mail is on the 2k7 or 2k3 mailbox server. The queue's last error states: "451 4.4.0 DNS query Failed."
    I can however do a NSlookup from the machine, and telnet to their mailservers on port 25 and get a helo response.
    I have enabled send connector protocol logging and nothing even shows up in the log about trying to contact this domain.
    I am at a loss as to where to look next. How does exchange 2007 handle its DNS resolution. Please help.
    Thanks
    Here is the results of Get-Sendconnectors |FL
    AddressSpaces                : {smtp:*;1}
    AuthenticationCredential     :
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : False
    Enabled                      : True
    ForceHELO                    : False
    Fqdn                         : dls.rutgers.edu
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : Server1
    Identity                     : DLSExch07mail
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    LinkedReceiveConnector       :
    MaxMessageSize               : 10MB
    Name                         : DLSExch07mail
    Port                         : 25
    ProtocolLoggingLevel         : Verbose
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {Server1, Server2}
    UseExternalDNSServersEnabled : False
    From the Logs in:
    C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\Connectivity
    2007-08-23T14:29:03.954Z,08C9B3176617F11F,SMTP,sabert.com,>,DNS server returned ErrorRetry reported by 0.0.0.0
    2007-08-23T14:29:03.954Z,08C9B3176617F11F,SMTP,sabert.com,-,The DNS query for 'DnsConnectorDelivery':'sabert.com':'247c4dcf-5bc9-4621-b64d-aa43ed43bf55' failed with error: ErrorRetry

    >Had one external DNS on the NIC along with our PDC and backup DC. Went ahead and removed it.
    That's not a good thing. Did you also flush the DNS cache with
    "ipconfig /flushdns" and restart the DNS Client service?
    >As for the "get-sendconnector" it believes it is going to {SMTP:*;1}.
    Maybe, but it shouldn't be going to ANY send connector. You have just
    one Exchange server and the e-mail is purportedly addressed to a domain
    in your accepted domains.
    So, is 61027a30-e9a9-4c2d-acb5-c1efc96d5d8b your send connector, or
    one of your send connectors?
    Let's see the output of this:
    get-sendconnector | fl *
    And this:
    get-accepteddomain | fl
    Rich Matheisen
    MCSE+I, Exchange MVP
    --- Rich Matheisen MCSE+I, Exchange MVP
    Flushed and registered DNS and restarted DNS client.
    Removed Send Connector to try mail without it but no luck, still goes to queue with same error.
    I wasn't sure what NextHopConnector 61027a30-e9a9-4c2d-acb5-c1efc96d5d8b was so I ran get-sendconnector <guid> and it came back with:
    The operation couldn't be performed because object '61027a30-e9a9-4c2d-acb5-c1efc96d5d8b' couldn't be found on '<backup domain controller>.local'.
        + CategoryInfo          : NotSpecified: (:) [Get-SendConnector], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : F31958E9,Microsoft.Exchange.Management.SystemConfigurationTasks.GetSendConnector
    So, it appears that the NextHopConnector is not being located in the AD (which I don't even know why it's looking at backup DC instead of primary) like it should.  When I run get-sendconnector | fl * I get:
    get-sendconnector | fl *
    PSComputerName               : <Exchange FQDN name>
    RunspaceId                   : 2faaf0ee-9a3d-4542-b69f-9fc9548242fd
    DNSRoutingEnabled            : False
    TlsDomain                    :
    TlsAuthLevel                 :
    ErrorPolicies                : Default
    SmartHosts                   : {<ISP SMTP relay>}
    Port                         : 25
    LinkedReceiveConnector       :
    ConnectionInactivityTimeOut  : 00:10:00
    ForceHELO                    : False
    IgnoreSTARTTLS               : False
    Fqdn                         :
    RequireTLS                   : False
    RequireOorg                  : False
    Enabled                      : True
    ProtocolLoggingLevel         : None
    SmartHostAuthMechanism       : None
    AuthenticationCredential     :
    UseExternalDNSServersEnabled : True
    DomainSecureEnabled          : False
    SourceIPAddress              : 0.0.0.0
    SmtpMaxMessagesPerConnection : 20
    SmartHostsString             : <ISP SMTP relay>
    AddressSpaces                : {SMTP:*;1}
    ConnectedDomains             : {}
    IsScopedConnector            : False
    IsSmtpConnector              : True
    Comment                      :
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {<Exchange DNS name>}
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : <Exchange DNS name>
    MaxMessageSize               : 10 MB (10,485,760 bytes)
    AdminDisplayName             :
    ExchangeVersion              : 0.1 (8.0.535.0)
    Name                         : <company>
    DistinguishedName            : CN=<company>,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN
                                   =Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<company>
    Excha
                                   nge Server,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=local
    Identity                     : <company>
    Guid                         : 09833378-b5c5-4581-9622-aa358087caf8
    ObjectCategory               : <domain>/Configuration/Schema/ms-Exch-Routing-SMTP-Connector
    ObjectClass                  : {top, msExchConnector, mailGateway, msExchRoutingSMTPConnector}
    WhenChanged                  : 11/2/2010 9:35:14 AM
    WhenCreated                  : 11/2/2010 9:35:14 AM
    WhenChangedUTC               : 11/2/2010 2:35:14 PM
    WhenCreatedUTC               : 11/2/2010 2:35:14 PM
    OrganizationId               :
    OriginatingServer            : <backup DC>.local
    IsValid                      : True
    get-sendconnector 09833378-b5c5-4581-9622-aa358087caf8
    Identity                               AddressSpaces                     
    Enabled
    <company>                        {SMTP:*;1}                          
    True
    So..is there a way to change this NextHopConnector pointer record so that mail enters the queue with the correct guid?
    Thanks

  • Edge Transport Server Fails DNS Query When Emailing to one Specific Domain

    This issue occurs for the same domain across three different edge transport servers.
    All servers are Windows 2008 STD SP2, Exchange 2007 SP1 U9.  Emails are delivered using DNS connector from edge.  Emails to this one specific domain would sit in the retry queue with DNS query error until NDR was generated.  Connectivity Logging generated the following:
    2009-09-01T19:52:23.539Z,08CBEDE9198E2DC3,SMTP,subdomain.domain.com,>,DNS server returned ErrorRetry reported by 208.241.124.200
    2009-09-01T19:52:23.539Z,08CBEDE9198E2DC3,SMTP,subdomain.domain.com,-,The DNS query for 'DnsConnectorDelivery':'subdomain.domain.com':'cd771f71-77a3-4aca-b002-86f477816910' failed with error: ErrorRetry
    I changed the servers DNS settings to different servers with the same response.  Validated that manual MX lookups worked, and that I could telnet to any of the three MX records and deliver mail via telnet.
    I did a packet capture and received the following:
    12    32.280037    172.28.16.55    208.241.124.200    DNS    Standard query AAAA SMTPSERVER.subdomain.domain.com
    So what is happening is the Edge servers are only performing IP6 lookups, and throughout the log, only for subdomain.domain.com do they NOT perform a regular IP4 A record lookup.  I then went about disabling TCP/IP6 as per this article:
    http://technet.microsoft.com/en-us/network/cc987595.aspx
    this stated to do the following:
    Alternately, from the Windows XP or Windows Server 2003 desktop, click Start , point to Programs , point to Accessories , and then click Command Prompt . At the command prompt, type netsh interface ipv6 uninstall .
    To remove the IPv6 protocol for Windows XP with no service packs installed, do the following:
    Log on to the computer with a user account that has local administrator privileges.
    From the Windows XP desktop, click Start , point to Programs , point to Accessories , and then click Command Prompt .
    At the command prompt, type ipv6 uninstall .
    Unlike Windows XP and Windows Server 2003, IPv6 in Windows Vista and Windows Server 2008 cannot be uninstalled. However, you can disable IPv6 in Windows Vista and Windows Server 2008 by doing one of the following:
    In the Network Connections folder, obtain properties on all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under This connection uses the following items .
    This method disables IPv6 on your LAN interfaces and connections, but does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.
    Add the following registry value (DWORD type) set to 0xFF:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
    This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect.
    I did the above, and still, the Edge Transport servers would only perform AAAA lookups, and messages would sit in the queue.
    As temporary workaround, created new send connector with the three available MX hosts as possible smarthosts for subdomain.domain.com, and this allowed email flow.
    I've tried disabling the TCPIP6, and still doesnt work.  Any suggestions?

    Hi Allen and Paul,
    we experience problems in receiving mails from senders with this Exchage server problem. When we are aware of the problem, we send them the above mentioned link and ask them to make adjustments. Then afterwards usually mail arrives without any problems.
    The problem for us is that it seems as if the problem grows. More and more mail does not arrive on our mailadresses (mine for example is [email protected]) And not all of the senders recieve notifications that mail cannot be delivered. As you can imagine
    this situation is unacceptable and damaging our customer relations.
    Is there anything WE can do? (apart from sending them the information to make adjustements in their Exchange servers...)
    I hope you can help us...
    Thanks in advance
    Leonard
    Hi Leonard,
    as stated below we where experiencing the same problem with one of our customers. Seeing that it's a DNS related problem we suggested to the customer to change or add an additional DNS service through i.e. dyndns.com. After adding the current DNS records
    to the new DNS service mail started coming in from every customer that had problems.
    So for your clients i would suggest a similar solution, it helped over here at least.
    Kind regards,
    Philipp

  • Getting Rest Query failed error.

    Hi,
    I have integrated my app with facebook. I am able to post my reviews and comments on FB but when I click on link in FB post, its redirectign me to the required url but not loading the review.
    Can any body tell me why this happens.
    here are logs:
    2013-05-22 18:29:17,281 [http-bio-8090-exec-10] ERROR com.fatwire.wsdk.rest.WidgetSDKResource - Failed to execute method feed in widget wsdk.reviews
    com.fatwire.cos.ex.CoSServerException: com.fatwire.cos.ex.CoSServerException: REST query failed
         at com.fatwire.cos.core.jpa.query.CoSJpaQuery.getSingleResult(CoSJpaQuery.java:161)
         at com.fatwire.cos.records.RecordManager.countRecords(RecordManager.java:462)
         at com.fatwire.wsdk.cos.records.processors.feed.RecordListReadProcessor.calculatePageNo(RecordListReadProcessor.java:229)
         at com.fatwire.wsdk.cos.records.processors.feed.RecordListReadProcessor.getPageNo(RecordListReadProcessor.java:186)
         at com.fatwire.wsdk.cos.records.processors.feed.RecordListReadProcessor.process(RecordListReadProcessor.java:62)
         at com.fatwire.cos.core.monitor.MonitoredMethodInterceptor.invoke(MonitoredMethodInterceptor.java:68)
         at com.fatwire.wsdk.pipeline.impl.PipelineImpl.execute(PipelineImpl.java:60)
         at com.fatwire.cos.core.monitor.MonitoredMethodInterceptor.invoke(MonitoredMethodInterceptor.java:68)
         at com.fatwire.wsdk.rest.WidgetSDKResource.executeWidgetMethod(WidgetSDKResource.java:183)
         at sun.reflect.GeneratedMethodAccessor255.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
         at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
         at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
         at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
         at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
         at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
         at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
         at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
         at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
         at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
         at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
         at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
         at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
         at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
         at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
         at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)
         at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)
         at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.fatwire.cos.comments.service.filters.RestFilter.doFilter(RestFilter.java:141)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.fatwire.cos.core.i18n.ResourceFilter.doFilter(ResourceFilter.java:45)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.fatwire.cos.core.sso.SSOContextFilter.doFilter(SSOContextFilter.java:64)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:219)
         at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.fatwire.cos.core.sso.GeneralPreparationsFilter.doFilter(GeneralPreparationsFilter.java:68)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.fatwire.cos.core.util.web.StartupGuardFilter.doFilter(StartupGuardFilter.java:42)
         at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
         at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
         at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
         at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
         at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
         at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
         at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: com.fatwire.cos.ex.CoSServerException: REST query failed
         at com.fatwire.cos.core.jpa.cmd.wem.WemCommandManager.execREST(WemCommandManager.java:356)
         at com.fatwire.cos.core.jpa.cmd.wem.WemCommandManager.execGET(WemCommandManager.java:192)
         at com.fatwire.cos.core.jpa.cmd.wem.WemCountQueryCommand.findResult(WemCountQueryCommand.java:79)
         at com.fatwire.cos.core.jpa.cmd.wem.WemCountQueryCommand.executeSingle(WemCountQueryCommand.java:68)
         at com.fatwire.cos.core.monitor.MonitoredMethodInterceptor.invoke(MonitoredMethodInterceptor.java:68)
         at com.fatwire.cos.core.jpa.query.CoSJpaQuery.getSingleResult(CoSJpaQuery.java:156)
         ... 104 more
    Thanks in advance.
    Thanks,
    Nelash jindal

    Hi There,
    Please try the below steps and check if it helps :
    Go to C:/programfiles/Adobe/Adobe Captivate(version)/AdobeCaptivate.ini           
    Open the file with notepad and add the line Use32BitJVMForPublish=1 
    Save it and Try to publish the project .
    Regards,
    Mayank

  • The following query failed: GetUserProfileByName - with the wrong username

    I have 2 users (out of 800), who run into this issue on occasion. Their username is 'fccs\user1' in the profile db, and in every UserInfo table in the system. But when they try to go to certain sites or open an infopath form, this error gets thrown:
    The following query failed: GetUserProfileByName (User: FCCS\[email protected], Form Name: Template, IP: , Connection Target: , Request: http://fccsteams/sites/DataManagement/Tasks/Lists/Tasks/Folders1.aspx?RootFolder=/sites/DataManagement/Tasks/Lists/Tasks/2013/11&, Form ID: urn:schemas-microsoft-com:office:infopath:list:-AutoGen-2013-08-05T23:14:53:458Z Type: DataAdapterException, Exception Message: The remote server returned an error: (500) Internal Server Error.  Operation Failure ---> Access Denied: To create a user profile, you must be an administrator, or create your own profile and have personal features rights.  UnauthorizedAccessAccess Denied: To create a user profile, you must be an administrator, or create your own profile and have personal features rights. The remote server returned an error: (500) Internal Server Error.)
    Notice how the username is now the entire email address and not just the username. I have no idea why it thinks that that is their username. Any ideas?

    Hi,
    According to your post, my understanding is that you got query failed error.
    Melick had written a blog said that the form access the user profile web service (Userprofileservice.asmx) using  UDC
    file.
    You can check whether the UDC connection was still pointing to root site.
    You can change this file to match with the sub site collection. Otherwise there may be a cross domain access issue.
    There are similar threads for your reference.
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/9c2f7f4c-0fa9-43bd-94b1-1d7075e35841/5566-error-with-getuserprofilebyname-and-infopah-browser-forms-using-claims-based-authentication
    http://social.msdn.microsoft.com/Forums/en-US/49753330-40c0-4327-9a9b-2c3304a74e67/sharepoint-infopath-and-populating-forms-with-ad-data?forum=sharepointcustomizationlegacy
    Thanks & Regards,
    Jason 
    Jason Guo
    TechNet Community Support

  • DNS lookup failed. How to fix with Google chrome?

    "The server at _____.com can't be found, because the DNS lookup failed. This error is often caused by having no connection to the internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing google chrome from accessing the network." 

    Is Safari the same?

  • DNS querier

    please help me in creating a DNS query program to display the resource records it returns

    Construct an application to send and receive DNS queries and responses. application must be able to send queries for a given hostname [The application must send the query to a given DNS server, wait for the response and display all the Resource Records returned.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • WSA - Report Query Failed

    Hi all,
    Recently, I'm receiving these two alerts from one WSA S370:
    Report Query Failed
          query_id: wsa_monitor_overview_web_proxy_summary
          data_source: WSASimpleTotalRDS
          error: <type 'type'> ('egg/command_client.py send_message|555', "<class 'Commandment.DaemonUnresponsiveError'>", 'S370B.NAME.net: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
    AND
    Report Query Failed
          query_id: wsa_monitor_overview_clients_by_blocked_transactions
          data_source: WSACommonRDS
          error: <type 'type'> ('egg/command_client.py call|238', "<class 'reporting.query.exceptions.DatabaseQueryFailure'>", '', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|251] [reportdatasource/CounterReportDataSource.py _run_api_query|482] [query/client.py time_merge_query|454] [query/client.py _call|235] [egg/command_client.py call|238]')
    The code I'm using is 7.1.1-038
    I started receiving the alerts only after upgrading to this code. Have you noticed something similar?
    Thanks a lot for your help!!!
    Fernando

    Hello Everyone,
    I am in Australia (Melbourne) and i am using ironport s160 web security appliance version: 7.1.2-80. Reecently i have started receiving the following warning from ironport proxy.
    The Warning message is:
    Report Query Failed
                    query_id: wsa_monitor_overview_malware_categories
                    data_source: WSACommonRDS
                    error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
    Report Query Failed
                    query_id: wsa_monitor_overview_suspect_transactions_detected
                    data_source: CounterReportDataSource
                    error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|272] [reportdatasource/CounterReportDataSource.py _parse_api_results|506] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|525] [query/result.py next|112] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
    Report Query Failed
                    query_id: wsa_monitor_overview_suspect_transactions_summary
                    data_source: WSASimpleTotalRDS
                    error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
    Report Query Failed
                    query_id: wsa_monitor_overview_top_application_types
                    data_source: CounterReportDataSource
                    error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
    Report Query Failed
                    query_id: wsa_monitor_overview_top_url_categories
                    data_source: CounterReportDataSource
                    error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
    Product: IronPort S160 Web Security Appliance
    Model: S160
    Version: 7.1.2-080
    Serial Number: 0025643CFD42-4GQYHL1
    Timestamp: 14 Jun 2012 14:00:21 +1000
    Thank you for your help.
    Lovedeep

  • ERROR: Cannot create authcontext with null org-Naming query failed  code:21

    I use OpenSSO Enterprise 8.0 Update 1 Patch1 Build 6.1(2009-June-9 12:56)
    I try to evaluate the Apache 2.2 web agent.
    It's been installed without errors, and both the OpenSSO and Apache server restarted.
    The agent profile's been created. Also, I use the default (OpenDS) configuration repository
    for OpenSSO, but an external (DSEE) user data directory.
    I think I did all the required steps with regards to both directories, since I don't see any error
    in the LDAP logs, each entry seems to be found as expected, the BIND operations are all
    successfull.
    Also, I use a sub-realm rather than the default top realm, and thus, I've modified the agent configuration
    (in the agent profile) so that the login URL is now ... /UI/Login?realm=myrealm
    When I try to access the Apache homepage, I get an error 500. The most recent OpenSSO server log file
    (...../opensso/debug/Authentication) contains the following message:
    ERROR: Cannot create authcontext with null org
    The most recent agent log file (....../apache22_agent/Agent_001/logs/debug/amAgent) has the following error:
    2009-07-07 17:08:11.992 Error 10513:80149a50 PolicyEngine: am_policy_evaluate: InternalException in Service::update_policy with error message:Naming query failed. and code:21
    I don't know what else I can do to debug this problem and find a solution. Any idea ?

    Thank you Shubba,
    With all available log details enabled, I now have the following messages on the agent side:
    2009-07-09 10:14:51.731MaxDebug 5613:80149a50 all: No value specified for key com.sun.identity.agents.config.profile.attribute.mapping, using default value .
    2009-07-09 10:14:51.731 Debug 5613:80149a50 NamingService: BaseService::doRequest(): Using server: http://portable.antibes.net:8080/opensso/namingservice.
    2009-07-09 10:14:51.731MaxDebug 5613:80149a50 NamingService:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <RequestSet vers="1.0" svcid="com.iplanet.am.naming" reqid="10">
    <Request><![CDATA[                                                                                                                      
      <NamingRequest vers="3.0" reqid="2" sessid=""AQIC5wM2LY4SfcyaGFgc5h9Y7/kpf4f//ml82oVfNlbWxQE=@AAJTSQACMDE=#"">                             <GetNamingProfile>                                                                                                                         </GetNamingProfile>                                                                                                                        </NamingRequest>]]> </Request>
    </RequestSet>
    2009-07-09 10:14:51.712MaxDebug 5613:80149a50 NamingService: BaseService::sendRequest Request line: POST /opensso/namingservice HTTP/1.0
    2009-07-09 10:14:51.712 Debug 5613:80149a50 NamingService: BaseService::sendRequest Cookie and Headers =Host: portable.antibes.net
    2009-07-09 10:14:51.712 Debug 5613:80149a50 NamingService: BaseService::sendRequest Content-Length =Content-Length: 334
    2009-07-09 10:14:51.712 Debug 5613:80149a50 NamingService: BaseService::sendRequest Header Suffix =Accept: text/xml
    Content-Type: text/xml; charset=UTF-8
    2009-07-09 10:14:51.712MaxDebug 5613:80149a50 NamingService: BaseService::sendRequest(): Total chunks: 7.
    2009-07-09 10:14:51.712MaxDebug 5613:80149a50 NamingService: BaseService::sendRequest(): Sent 7 chunks.
    2009-07-09 10:14:51.728 Debug 5613:80149a50 NamingService: HTTP Status = 500 (Internal Server Error)
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Http::Response::readAndParse(): Reading headers.
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Server: Apache-Coyote/1.1
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Content-Type: text/html;charset=utf-8
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Date: Thu, 09 Jul 2009 08:14:51 GMT
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Connection: close
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Http::Response::readAndParse(): Reading body content of length: 13830487939496281954
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 all: Connection::waitForReply(): returns with status success.
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Http::Response::readAndParse(): Completed processing the response with status: success
    2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: AMSetupFilter.doFilter
    com.sun.identity.setup.AMSetupFilter.doFilter(AMSetupFilter.java:117)
    </pre></p><p><b>root cause</b> <pre>java.lang.NullPointerException
    com.iplanet.services.naming.service.NamingService.processRequest(NamingService.java:361)
    com.iplanet.services.naming.service.NamingService.process(NamingService.java:352)
    com.iplanet.services.comm.server.PLLRequestServlet.handleRequest(PLLRequestServlet.java:180)
    com.iplanet.services.comm.server.PLLRequestServlet.doPost(PLLRequestServlet.java:134)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    com.sun.identity.setup.AMSetupFilter.doFilter(AMSetupFilter.java:91)
    </pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html>
    2009-07-09 10:14:51.729 Warning 5613:80149a50 NamingService: BaseService::doHttpPost() failed, HTTP error = 500
    2009-07-09 10:14:51.729 Debug 5613:80149a50 NamingService: NamingService()::getProfile() returning with error code HTTP error.
    2009-07-09 10:14:51.729 Error 5613:80149a50 PolicyEngine: am_policy_evaluate: InternalException in Service::update_policy with error message:Naming query failed. and code:21
    In my Tomcat server (OpenSSO server web container), I have the following errors:
    Jul 9, 2009 10:12:35 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 22746 ms
    [Fatal Error] :2:46: Element type "NamingRequest" must be followed by either attribute specifications, ">" or "/>".
    java.lang.NullPointerException
    at com.iplanet.services.naming.service.NamingService.processRequest(NamingService.java:361)
    at com.iplanet.services.naming.service.NamingService.process(NamingService.java:352)
    at com.iplanet.services.comm.server.PLLRequestServlet.handleRequest(PLLRequestServlet.java:180)
    at ...
    It seems like the problem comes from the couple of closing square brackets in the NamingRequest tag:
    </NamingRequest>]]>
    I don't know where it comes from, so if you've an idea I'd enjoy .
    Cheers,

  • Database Query Failed

    I got this error message instead of weekly report.
    Anybody ever experienced this? How to fix it?
    The Warning message is:
    Report Query Failed
    query_id: mga_overview_incoming_mail_over_time
    data_source: CounterReportDataSource
    error: <type 'type'> ('command_manager/command_client.py call|242', "<class 'reporting.query.exceptions.DatabaseQueryFailure'>", '', '[database/ReportCatalog.py run_report_queries|234] [reportdatasource/CounterReportDataSource.py query|131] [reportdatasource/CounterReportDataSource.py _parse_api_results|216] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|251] [reportdatasource/CounterReportDataSource.py _parse_interval_result|317] [reportdatasource/CounterReportDataSource.py _parse_standard_interval_result|326] [query/result.py next|239] [query/client.py _call|212] [command_manager/command_client.py call|242]')
    Version: 5.5.1-011

    Yes, I did. Instead of a graph, I got this error message:
    Error while receiving data.
    There may have been an intermittent timeout during the database query.
    Have you tried going onto the GUI interface and going to "Monitor > Incoming Mail", switching the Time range to display a Week and then clicking on the Printable button on the right hand corner.
    I got this error message instead of weekly report.
    Anybody ever experienced this? How to fix it?
    The Warning message is:
    Report Query Failed
    query_id: mga_overview_incoming_mail_over_time
    data_source: CounterReportDataSource
    error: ('command_manager/command_client.py call|242', "", '', '[database/ReportCatalog.py run_report_queries|234] [reportdatasource/CounterReportDataSource.py query|131] [reportdatasource/CounterReportDataSource.py _parse_api_results|216] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|251] [reportdatasource/CounterReportDataSource.py _parse_interval_result|317] [reportdatasource/CounterReportDataSource.py _parse_standard_interval_result|326] [query/result.py next|239] [query/client.py _call|212] [command_manager/command_client.py call|242]')
    Version: 5.5.1-011

  • Query Failed: [nQSError: 46036] Internal Assertion ( OBIEE error)

    Hi Friends.
    Did anyone faced this problem. I am using custom filters on reports. The reports work well for 5 filters but start giving error on last filter. As far as I can guess its an internal OBIEE optimizer error. Can anyone faced this problem and help
    A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46036] Internal Assertion: Condition pCond, file server\Query\Optimizer\Request\Src\SQORRqList.cpp, line 2604.Please have your System Administrator look at the log for more details on this error. (HY000)

    We faced same problem. There is no clear definition of error even we increase log trace level to 7.
    Query Status: [nQSError: 46036] Internal Assertion: Condition pCond, file server\Query\Optimizer\Request\Src\SQORRqList.cpp, line 2716. [[
    We will open a ticket to Oracle Support.

  • Constant DNS querying for 127.0.0.1

    Hello,
    I'm quite puzzled... I noticed a constant low bandwidth traffic on the WAN port of the router and tracked it back to the MacOS X (10.5.2) host constantly DNS querying for 127.0.0.1 (about every three seconds). I am using DHCP and the network configuration picks up the external DNS server.
    I thought this localhost information should be picked up directly from /etc/hosts (in my case)
    cat /etc/hosts
    # Host Database
    # localhost is used to configure the loopback interface
    # when the system is booting. Do not change this entry.
    127.0.0.1 localhost
    255.255.255.255 broadcasthost
    ::1 localhost
    fe80::1%lo0 localhost
    and there should be no need to ask for this reverse DNS name resolution to the external DNS server.
    do I really have to use dscl and create an entry for localhost to stop this DNS querying activity?
    andrea

    and tcpdump reports:
    tcpdump -A -n -i en0 port 53
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on en0, link-type EN10MB (Ethernet), capture size 96 bytes
    00:01:51.873347 IP 192.168.21.100.5353 > 192.168.21.1.53: 13522+[|domain]
    E..YO..........d.......5.EnB4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:01:51.889664 IP 62.31.176.39.53 > 192.168.21.100.5353: 13522 NXDomain[|domain]
    E....A@.....>..'...d.5.....S4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:01:54.873113 IP 192.168.21.100.5353 > 192.168.21.1.53: 13523+[|domain]
    E..Yd..........d.......5.EnA4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:01:54.889388 IP 62.31.176.39.53 > 192.168.21.100.5353: 13523 NXDomain[|domain]
    E....B@.....>..'...d.5.....R4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:01:57.872864 IP 192.168.21.100.5353 > 192.168.21.1.53: 13524+[|domain]
    [email protected]
    dnsbugtest.1.0.0.127.in-addr.ar
    00:01:57.888922 IP 62.31.176.39.53 > 192.168.21.100.5353: 13524 NXDomain[|domain]
    E....C@.....>..'...d.5.....Q4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:00.873402 IP 192.168.21.100.5353 > 192.168.21.1.53: 13525+[|domain]
    E..Y)..........d.......5.En?4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:00.889180 IP 62.31.176.39.53 > 192.168.21.100.5353: 13525 NXDomain[|domain]
    E....D@.....>..'...d.5.....P4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:03.872666 IP 192.168.21.100.5353 > 192.168.21.1.53: 13526+[|domain]
    ..........d.......5.En>4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:03.891466 IP 62.31.176.39.53 > 192.168.21.100.5353: 13526 NXDomain[|domain]
    E....E@.....>..'...d.5.....O4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:06.872956 IP 192.168.21.100.5353 > 192.168.21.1.53: 13527+[|domain]
    E..Y.(.........d.......5.En=4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:06.888972 IP 62.31.176.39.53 > 192.168.21.100.5353: 13527 NXDomain[|domain]
    E....F@.....>..'...d.5.....N4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:09.872419 IP 192.168.21.100.5353 > 192.168.21.1.53: 13528+[|domain]
    E..Y!..........d.......5.En<4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    00:02:09.890732 IP 62.31.176.39.53 > 192.168.21.100.5353: 13528 NXDomain[|domain]
    E....G@.....>..'...d.5.....M4............1.0.0.127
    dnsbugtest.1.0.0.127.in-addr.ar
    ^C
    14 packets captured
    60 packets received by filter
    0 packets dropped by kernel
    pretty clear that the 127.0.0.1 entry in /etc/hosts is unfortunately not used.
    localhost and 127.0.0.1 are part of the loopback interface (lo0) and a lookup from /etc/hosts should suffice! no reason at all to query a DNS service unless explicitly specified.

  • Enter Machine Password DNS Update Failed on Mac Pro 10.6.6

    Windows 2008 R2 Active Directory with several PCs and 3 MACs, all three at 10.6.6.
    Only one, the Mac Pro, is slow to access network resources, gets Enter Machine Password: DNS Update Failed on Console, and is much slower to open webpages than the other 2 MACs; they work fine. I know that AD is configured right since I have no network errors on them.
    Can bind and unbind as expected, can access Mac from AD Server as well as other PC/Macs, so this issue is not like most all other posts in that everything works except slow network (opening a network share gets the spinning wait cursor).
    Any Ideas?
    TIA

    On the offending Mac open System Preferences->Network pane and highlight the port that you are connecting to the domain. Then in the right side of the pane click on the word "Advanced". In that drop-down select the DNS tab and make sure it has the same DNS that the domain uses. You can use thew + button to add the correct DNS servers. Also while in the Network pane, Advanced, select the WINS tab and fill it the appropriate settings for the Windows Domain.
    Also on the offending Mac open System Preferences->Date & Time and make sure the Map Location is correct and also you are using the same Time server that the Domain uses (you can type in the Time Server address in the Time Server field.
    Lastly are you using DHCP or Static in your Domain?

Maybe you are looking for

  • Dynamic function call in Forms PL/SQL [SOLVED]

    I have a 10G form, which has a dropdown list of values. Depending on the value selected, I look up a setup table which will tell me the name of the database package/function to call. I then want to call that function with a bind IN parameter and then

  • MISSING_COMPONENT : oracle.j2ee, 10.1.3.4.0 while applying Opatch  6702510

    Hi, We are upgrading our test instance from 12.0.6 to 12.1.3 ,with IAS_ORACLE_HOME now upgraded from 10.1.3 to 10.1.3.4.0 But when we apply additional patch Opatch 6702510 on IAS_ORACLE_HOME we get following error: MISSING_COMPONENT : oracle.j2ee, 10

  • How do i export emails to excel?

    I am trying to categorize and count emails in Mac Mail.  Is it possible to export emails from Mac Mail into Excel so that I can sort and count based on "sent from" and "date"?  Any help would be greatly appreciated.

  • Help in removing iSCSI driver

    I had an earlier version of Cisco iSCSI driver, 2.1.1, installed, and I thought I had removed it. However, the iscsicfg.cpl file remained in the system32 directory and I couldn't delete it. Cisco doc mentioned to run the setup program to de-install t

  • Can't Sync, iPhone Thinks it's new, wants to restore/set up.

    Recently my iPhone would disconnect itself every time I tried to sync, the phone display itself would still say "in progress", however it would have disappeared from the iTunes source list, I hadn't time to rectify this problem before going out of th