CSCtw45592 - CLI "NTP Server dns name " - does not get synced to standby

15.1(3)T4

Hi David,
This bug is not shown as resolved in 15.1(3)T4;
http://www.cisco.com/en/US/docs/ios/15_1/release/notes/151-3TCAVS.html#wp54837
Known Affected Versions:                          (65)
15.2(1)S,15.1(3)T3,15.1(3)T2,15.1(3)T1,15.1(3)T
15.1(2)T4,15.1(2)T3,15.1(2)T2a,15.1(2)T2,15.1(2)1
15.1(2)T0a,15.1(2)T,15.1(2)GC1,15.1(2)GC
15.1(1)XB3,15.1(1)XB2,15.1(1)XB1,15.1(1)XB
15.1(1)T4,15.1(1)T3,15.1(1)T2,15.1(1)T1,15.1(1)T
15.0(1)XA5,15.0(1)XA4,15.0(1)XA3,15.0(1)XA2
15.0(1)XA1,15.0(1)SY,12.2(50)SY1,12.2(50)SY
12.2(33)SXJ2,12.2(33)SXJ1,12.2(33)SXJ
12.2(33)SXI8a,12.2(33)SXI8,12.2(33)SXI7
12.2(33)SXI6,12.2(33)SXI5a,12.2(33)SXI5
12.2(33)SXI4a,12.2(33)SXI4,12.2(33)SXI3z
12.2(33)SXI3a,12.2(33)SXI3,12.2(33)SXI2a
12.2(33)SXI2,12.2(33)SXI1,12.2(33)SXI
12.2(33)SXH8b,12.2(33)SXH8a,12.2(33)SXH8
12.2(33)SXH7w,12.2(33)SXH7v,12.2(33)SXH7
12.2(33)SXH6,12.2(33)SXH5,12.2(33)SXH4
12.2(33)SXH3a,12.2(33)SXH3,12.2(33)SXH2a
12.2(33)SXH2,12.2(33)SXH1,12.2(33)SXH0a
12.2(33)SXH
Less
Fixed in:                          (17)
15.2(3.30)PIP,15.2(2.9.6)PIH18,15.2(2.14)PI19d
15.2(2.14)PI19,15.2(2.10)S,15.2(2)T0.12,15.2(2)S
15.2(2)GC,15.2(1.18)S0.8,15.2(1)T2.12,15.2(1)S2
15.2(1)S1.3,15.1(4)XB8,15.1(4)M3.8,15.1(2)SIV11.10
15.1(1.23)SID,12.2(33)SXJ3.36
Cheers!
Rob
"Always movin' ahead and never lookin' back" - Springsteen

Similar Messages

  • Error: Missing SRV record at DNS server - [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
    only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
    a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
                        Error:
                        Missing SRV record at DNS server 192.168.200.5:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
    the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
                  TEST: Dynamic update (Dyn)
                     Test record dcdiag-test-record added successfully in zone cmedia.local
                     Test record dcdiag-test-record deleted successfully in zone cmedia.local
                  TEST: Records registration (RReg)
                     Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
                        Matching CNAME record found at DNS server 192.168.200.5:
                        a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.5:
                        CM-DC1-HV-NYC01.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.cmedia.local
                        Error:
                        Missing SRV record at DNS server 192.168.200.5:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._udp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kpasswd._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.gc._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.5:
                        gc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                        Matching CNAME record found at DNS server 192.168.200.6:
                        a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.6:
                        CM-DC1-HV-NYC01.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.cmedia.local
                        Error:
                        Missing SRV record at DNS server 192.168.200.6:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._udp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kpasswd._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.gc._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.6:
                        gc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                  Warning: Record Registrations not found in some network adapters

    Hi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
    was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
    the latest run of that...
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
                   Starting test: DNS
                      See DNS test in enterprise tests section for results
                      ......................... CM-DC-NY01 passed test DNS
             See DNS test in enterprise tests section for results
             ......................... CM-DC1-NY01 passed test DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : cmedia
          Starting test: CheckSDRefDom
             ......................... cmedia passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... cmedia passed test CrossRefValidation
       Running enterprise tests on : cmedia.local
          Starting test: DNS
             Test results for domain controllers:
                DC: cm-dc-NY01.cmedia.local
                Domain: cmedia.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
                         MAC address is 00:00:00:00:00:00
                         IP Address is static
                         IP address: 192.168.200.6
                         DNS servers:
                            192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
                            192.168.200.5 (CM-DC1-NY01) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: cmedia.local.
                         Delegated domain name: _msdcs.cmedia.local.
                            DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone cmedia.local
                      Test record dcdiag-test-record deleted successfully in zone cmedia.local
                   TEST: Records registration (RReg)
                      Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
                         Matching CNAME record found at DNS server 192.168.200.6:
                         406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         cm-dc-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.6:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.pdc._msdcs.cmedia.local
                         Matching CNAME record found at DNS server 192.168.200.5:
                         406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         cm-dc-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.5:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.pdc._msdcs.cmedia.local
                   Warning: Record Registrations not found in some network adapters
                DC: CM-DC1-NY01.cmedia.local
                Domain: cmedia.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000010] Microsoft Hyper-V Network Adapter:
                         MAC address is 00:00:00:00:00:00
                         IP Address is static
                         IP address: 192.168.200.5, 0000::0000:0000:0000:0000
                         DNS servers:
                            192.168.200.5 (CM-DC1-NY01) [Valid]
                            192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: cmedia.local.
                         Delegated domain name: _msdcs.cmedia.local.
                            DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone cmedia.local
                      Test record dcdiag-test-record deleted successfully in zone cmedia.local
                   TEST: Records registration (RReg)
                      Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
                         Matching CNAME record found at DNS server 192.168.200.5:
                         a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         CM-DC1-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.5:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching CNAME record found at DNS server 192.168.200.6:
                         a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         CM-DC1-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.6:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                   Warning: Record Registrations not found in some network adapters
             Summary of test results for DNS servers used by the above domain controllers:
                DNS server: 198.32.64.12 (l.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12               [Err
    or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:1::803f:235               [Error details: 1460 (Type: Win32 - Description: This operation ret
    urned because the timeout period expired.)]
                DNS server: 2001:500:2::c (c.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2::c               [Error details: 1460 (Type: Win32 - Description: This operation returned b
    ecause the timeout period expired.)]
                DNS server: 2001:500:2d::d (d.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2d::d               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:500:84::b (b.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:84::b               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:503:ba3e::2:30               [Error details: 1460 (Type: Win32 - Description: This operation retu
    rned because the timeout period expired.)]
                DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:503:c27::2:30               [Error details: 1460 (Type: Win32 - Description: This operation retur
    ned because the timeout period expired.)]
                DNS server: 2001:7fd::1 (k.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:7fd::1               [Error details: 1460 (Type: Win32 - Description: This operation returned bec
    ause the timeout period expired.)]
                DNS server: 128.8.10.90 (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90               [Erro
    r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 128.9.0.107 (b.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107               [Erro
    r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2f::f (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2f::f               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:500:3::42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:3::42               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:7fe::53 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:7fe::53               [Error details: 1460 (Type: Win32 - Description: This operation returned be
    cause the timeout period expired.)]
                DNS server: 2001:dc3::35 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:dc3::35               [Error details: 1460 (Type: Win32 - Description: This operation returned be
    cause the timeout period expired.)]
                DNS server: 128.63.2.53 (h.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.168.200.5 (CM-DC1-NY01)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                   DNS delegation for the domain  _msdcs.cmedia.local. is operational on IP 192.168.200.6
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.228.79.201 (b.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.83.42 (l.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.91.13 (d.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   All tests passed on this DNS server
             Summary of DNS test results:
                                                Auth Basc Forw Del  Dyn  RReg Ext
                Domain: cmedia.local
                   cm-dc-NY01                  PASS PASS PASS PASS PASS WARN n/a
                   CM-DC1-NY01                 PASS PASS PASS PASS PASS WARN n/a
             ......................... cmedia.local passed test DNS
          Starting test: LocatorCheck
             GC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             PDC Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             KDC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             ......................... cmedia.local passed test LocatorCheck
          Starting test: FsmoCheck
             GC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             PDC Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             KDC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             ......................... cmedia.local passed test FsmoCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
             provided.
             ......................... cmedia.local passed test Intersite

  • When I add an event to my ipad it does not get synced with any other calendars on my other devices.

    My calendar on my ipad will sync with any information added on my android phone or on my PC but if I add information directly on my ipad it does not get added to my PC or phone.

    Do you have iCloud?
    As it states hereyou need it tp sync.
    Allan

  • DNS cache " Name Does not Exist"

    Hey Guys,
    So we've been experiencing a really weird issue related to the DNS for past couple of months. Here are the details:
    1) Our domain machines are Windows 7 Enterprise and their DNS points to Windows DNS Servers
    2) For companyxyz.net internal sites, the Windows DNS resolves those from its
    companyxyz.net zone.
    3) For public *.companyxyz.com records, the Windows DNS has conditional forwarders to point these requests to our Linux Bind Servers. And than the authoritative name servers respond to these queries accordingly
    4) Our internal employees use the public records such as testing.companyxyz.com 
    Problems:
    1) Employees on the internal network would randomly experience page not found on their browsers while trying to hit
    testing.companyxyz.com. When we try to ping this URL, ping would fail too. However, NSLOOKUP would work perfectly fine and return the correct results. ipconfig /flushdns fixes the issue right away
    2) During the time when this problem is occurring, if I look into the local cache ( ipconfig /displaydns), I find an entry saying:
        testing.companyxyz.com
        Name does not exist. 
    ipconfig /flushdns obviously clears out this record along with the other local cached records and fixes the issue.
    3) Point the local computers directly to the Linux Bind servers as DNS never create this issue. It's only when they are pointing to the Windows DNS and going to this public record. The problem also seems to occur a lot more frequently if there are considerably
    high number of hits to this URL.
    Have you guys experienced this issue before? I am looking for a fix for this issue and not having the end-users to flush their dns constantly. Also note this problem occurs sometimes once a day, or 2 -3 times a week. It's very random.
    Thanks.
    Bilal
     

    Hi,
    It seems that the issue is related to your Windows 7 client. Considering whether there is DNS attack or virus on this computer.
    Please try to do the safety scan first.
    Please monitor the DNS server performance referring these article:
    Monitoring DNS server performance
    http://technet.microsoft.com/en-us/library/cc778608(WS.10).aspx
    Monitoring and Troubleshooting DNS
    http://www.tech-faq.com/monitoring-and-troubleshooting-dns.html
    For further step, we need to capture the traffic by using Network monitor when the issue happened and we continuously ping
    testing.companyxyz.com.
    Microsoft Network Monitor 3.4
    http://www.microsoft.com/en-us/download/details.aspx?id=4865
    Let’s see whether there is DNS request happened and the DNS request is handled.
    You can post back the save traffic log here for our further research.
    Kate Li
    TechNet Community Support

  • ]The server name server_migration_2 specified with -Dweblogic.Name does not

    Hi!
    I followed the following steps to configure a clustered environment with two machines:
    - installation of Oracle WebLogic Server 11g (10.3.3) in machine A and B
    - creation of a domain using configuration wizard (in machine A)
    - distributed domain using pack (machine A) and unpack (machine B)
    - startup of node manager in both machines (both reachable)
    - creation of a Managed Server 1 in machine A
    - creation of a Managed Server 2 in machine B
    - startup of the Managed Server 1 in machine A (it works fine)
    - startup of the Managed Server 2 in machine B , it fails with the following error:
    <Nov 30, 2010 12:39:28 PM WET> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141223]The server name server_migration_2 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
    at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:803)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:493)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
    at weblogic.Server.main(Server.java:67)
    >
    <Nov 30, 2010 12:39:28 PM WET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    The config.xml file located at ../user_projects/domains/mydomain/config/ in Machine 1 has the full environment setup, however the same file on machine 2 only has admin server configuration.
    Why it happens? These two files must be synchronized? The config.xml in the Machine 2 is used by who? Admin server uses this file?
    Thanks a lot
    A.

    If your newly created managed server is on a 3rd machine you will still need to 'pack/unpack', to transport the configuration files to the new machine.
    If your 3rd managed server share domain_home with an already existing managed server you wont need to do this. In this case when a new managed server is created in the admin console, the admin server will propogate the change to the existing managed server which will update its configuration files in its local domain_home. The new server when starting will pick up this updated details from the shared location and will be able to start.
    You were doing the pack after creating admin server alone. So the config files transported to remote machine has only details of Admin Server and using that you were trying to start the managed server, where i it clearly failed saying that it can't find that managed server name in its configuration.
    If you have adavance knowledge of how many managed servers you need to create , at the time of domain creation, the right way is to configure all the man servers in the domain configuration wizard and then use pack/unpack to distribute the configuration files to each of the remote machine where the managed servers run.
    Hope it makes sense.

  • Sending an email from my Ipad I get "receipient was rejected by server because it does not allow relaying". What does this mean and how do I correct it?

    When sending an email from my Ipad. I get "receipient was rejected by server because it does not allow relaying". What does this mean and how do I correct it?

    On the email account's settings (Settings > Mail, Contacts, Calendars and tapping on the account on the right), go into it's outgoing SMTP settings and try putting in your email name and password (they might currently show as 'optional')

  • RDS Gateway + Smart Card Error [ The specified user name does not exist.]

    I have the following Windows Server 2008 R2 servers:
    addsdc.contoso.com, AD DS Domain Controller for contoso.com
    adcsca.contoso.com, AD CS Enterprise CA, CDPs/AIAs published externally.
    fileserver.contoso.com, RDS Session Host for Administration enabled
    rdsgateway.contoso.com, RDS Gateway enabled
    tmgserver.contoso.com, 'Publishing' rdsgateway.contoso.com but with pass-through authentication
    And the following Windows 7 PCs:
    internalclient.contoso.com
    externalclient.fabrikam.com
    There's no trust between the domains, the external client is completely separate on the internet but the CA certificate for contoso.com has been installed in the trusted Root CA store. All servers have certificates for secure RDP.
    I enrolled for a custom 'Smart Card Authentication' certificate with Client Authentication and Smart Card Logon EKUs from the CA, stored on my new Gemalto smart card using the Microsoft Base Smart Card CSP.
    From internalclient.contoso.com, I can RDP to fileserver.contoso.com
    using the smart card just fine with no certificate errors.
    From externalclient.fabrikam.com, I can RDP to fileserver.contoso.com
    via rdsgateway.contoso.com using a username and password just fine with no certificate errors.
    From externalclient.fabrikam.com, I can RDP to fileserver.contoso.com
    via rdsgateway.contoso.com using the smart card to authenticate to the gateway, and a username and password to authenticate to the end server, just fine.
    BUT from when using a smart card to authenticate to the end server via the gateway, it fails with:
         The specified user name does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. 
    When I move the client into the internal network and try the connection again (still via the RDS Gateway), it works fine - the only thing I can think of is being outside the network and not being able to contact the AD DS DC for Kerberos is causing the issue
    - but I'm pretty sure this is a supported scenario?
    The smart card works fine internally, the subject of the certificate is the user's common name (John Smith) and the only SAN is
    [email protected] which matches the UPN of the user account as it was auto-enrolled.
    Does anyone have any ideas?

    I had a similar issue where I am using a smart card through a Remote Desktop Gateway. I had to disable Network Level Authentication (NLA) on the destination Remote Desktop Server. If anyone has another way around this, I'd appreciate hearing it. I'd prefer
    to use NLA.

  • Error: The specified mailbox database [Mailbox Database Name] does not exist, when you try to export mailbox in Exchange 2007

    [Symptom]
    ======================
    In Exchange 2007, when you want to export mailbox to a .pst file, you should run the
    Export-Mailbox cmdlet from a 32-bit computer that has the following installed:
    The 32-bit version of the Exchange management tools
    Microsoft Office Outlook 2003 SP2 or later versions
    If not, you may encounter the following error message:
    You check that you have these required installed, but you get the error below when you run Export-Mailbox in EMS.
    “The specified mailbox database [Mailbox Database Name] does not exist.”
    [Cause Analysis]
    =======================================
    This is because that the account you use to run Export-Mailbox cmdlet don’t have the Exchange Server Administrator role assigned.
    You can check if this account has been delegated the Exchange Server Administrator role through the following path.
    EMC -> Organization Configuration-> Check permissions in the result pane.
    To delegate this Exchange Server Administrator role, right click on the
    Organization Configuration node and choose Add Exchange Administrator,
    you will see the Add Exchange Administrator window.
    [More Information]
    ==============================
    Export-Mailbox
    http://technet.microsoft.com/en-gb/library/aa998579(v=exchg.80).aspx
    How to Export and Import mailboxes to PST files in Exchange 2007 SP1
    http://blogs.technet.com/b/exchange/archive/2007/04/13/3401913.aspx
    Exchange 2007 cannot export pst files via its powershell
    http://social.technet.microsoft.com/Forums/forefront/en-US/b3bc0dce-35f3-4a69-9a33-4f2a855b9f94/exchange-2007-cannot-export-pst-files-via-its-powershell?forum=exchangesvrgenerallegacy
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi,
    Based on my test, if you make the user the owner of the database (rather than a user with the db_owner role), when you create a query, it creates it under the dbo schema rather than DOMAIN\username.
    Steps to do so (in Management Studio):
    Right click database, select Properties 
    Click File 
    Change Owner in the textbox 
    OK to confirm 
    Downside - other users under db_owner role will still have their username appended. So schemas have to be created for these users.
    Jaynet Zhang
    TechNet Community Support

  • I keep getting the following message when trying to send email, email rejected by server because it does not allow relaying

    when trying to send emails on my Iphone i get the message
    email rejected by server because it does not allow relaying
    can anyone help me with this problem

    Go into Settings>Mail, Contacts, Calendars>your account>Outgoing mail ServerSMTP>Primary Server then turn Server ON and fill in both User Name +Passwordunder Outgoing Mail Server.

  • File name does not showing the InDesign icon?

    I have got few files from my client and they said it is an InDesign CS2 version file. but the file name does not showing the InDesign icon on the file name, though I have CS2 and I have tried other version too.
    Also I could not open the file in any version.
    Can somebody help me?

    there is no screen shot...
    You must either post a link to it on another server or embed it into a post using the camera icon on the web page like this:

  • Groupwise 7 Rule Name does not display Windows 2008 R2

    Under tools and rules on a windows 2008 R2 server the rule name does not display. Any ideas on how to resolve this would be greatly appreciated.

    kdavisb wrote:
    > 2008 R2 server
    I'm pretty sure that the GW7 client is not supported on Windows 2008 R2.
    Danita
    Novell Knowledge Partner
    Upgrading to GroupWise 2012? http://www.caledonia.net/blog/?p=514
    http://www.caledonia.net/gw12upg.html

  • The table with Name of 'Table Name' does not exist.An error occurred when loading the Model.

    The table with Name of 'Table Name' does not exist.An error occurred when loading the Model.
    We get this error when we try to check the properties of an analysis server using SQL Server Management studio(right click the instance name
    and check properties). We have resolved this issue twice by Stopping the SQL Server analysis service,removing db folders from Analysis Server Data folder and starting the services back on. The db folder that we removed was advised by the BI team.
    The SQL Server Analysis Server is 2012 SP1

    Hi RB_ORIPW,
    The table with name of 'XXX' doesn't exist.
    An error occurred when loading the model(Micorsoft.AnalysisServices)
    If I understanding correctly, you encounter the error randomly, now what you want it that avoid this issue completely, other than stop the services, detele the db filder and restart the services, right?
    The error might be caused by that the data file is corrupted. However, we cannot give you the exact reason that cause this issue. You can troubleshoot this issue by using the Windows Event logs and msmdsrv.log.
    You can access Windows Event logs via "Administrative Tools" --> "Event Viewer".  SSAS error messages will appear in the application log.
    The msmdsrv.log file for the SSAS instance that can be found in \log folder of the instance. (C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log)
    Here is a blog about data collection for troubleshooting Analysis Services issues, please see:
    Data collection for troubleshooting Analysis Services issues
    Besides, here is fix that describe the similar issue, and it was fixed in Cumulative Update 7 for SQL Server 2012 SP1, please refer to the link below to see the details.
    http://support.microsoft.com/kb/2897263/en-us
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • TS2621 i'm getting the following message "The recipient was rejected by the server because it does not allow relaying."

    I cant send email.  I get the following message "The recipient was rejected by the server because it does not allow relaying."

    Try going into Settings > Mail, Contacts, Calendars > select the account > account name , tap on SMTP (under the 'Outgoing Mail Server' heading) and then tap on your Primary Server and try entering your email account and password and see if it then works

  • When I send email i get the recipient was rejected by the server because it does not allow relaying whats this mean??

    When i send an email i get this response " the recipient was rejected by the server because it does not allow relaying" whats this mean and how do i fix it??

    Go into Settings>Mail, Contacts, Calendars>your account>Outgoing mail Server SMTP>Primary Server then turn Server ON and fill in both User Name + Password under Outgoing Mail Server.

  • HT1430 I receive emails but when I try to send emails, I get a box that says that the "recipient was rejected by the server because it does not allow relaying"

    I can receive emails over AOL but cannot send them. When I do, I get a box that says "recipient was rejected by the server because it does not allow relaying"

    That's because you did not enter your screen name and password for the outgoing (SMTP) mail server on the phone. Or if you did they got erased. Go to Settings for the account and enter them.

Maybe you are looking for

  • Error while deploying to BPEL 11.1.1.3

    Hi I encountering a problem while deploying my bpel process. I am able to deploy the same process in the environment with Enterprise manager version 11.1.1.4 whereas when i try to deploy the same jar file in another environment with enterprise manage

  • How can I add image files to a executable jar file ?

    Could you tell me how can I add image files to executable jar file ? package structure: ../com/Main.class ../images/..

  • Need DVI splitter.

    Want to have 2 monitors on my mini. Where can I find a DVI splitter?

  • Trial Balance : monthwise

    Hi expers, My users wants to get F.01 monthwise.In F.01,if run period 2,i will get gl balances from Apr10 to May10.User wants only trial balance for Apr10,May10 like.Is there any standard functionality report. Please advise. Regards, Samaar

  • To static or not to static

    Hello, i have a little discussion with a colleage of mine about the use of statics. say we have a class (sqlManager) which is used to do all the sql work including the db connection. would it be wise to make this class static. in my opinion no. perha