Home > Exchange 2013 > DsGetSiteName failed: Status = 1919 0x77f (Installing Exchange 2013 SP1)

DsGetSiteName failed: Status = 1919 0x77f (Installing Exchange 2013 SP1)

I ran Exchange 2013 SP1 Setup in my LAB from a windows 2012 member server, received the following error message at the Readiness Checks dialog box:

“The Computer does not belong to a valid active Directory site. Check the site and subnet definitions”.

1Readiness Checks Error

Used Nltest.exe utility with the nltest /dsgetsite option, the Nltest.exe utility generated the following output:

DSGetSiteName failed: Status = 1919 0x77f ERROR_NO_SITENAME

2Error

To resolve this issue, I have followed below steps to make sure my windows 2012 Member server is healthy and part of valid site

  1. Check the DNS settings on the member server is pointed to valid internal DNS servers.

To change the DNS settings:

  1. Right-click My Network Places, and then click Properties in the shortcut menu to open the Network and Dial-up Connections dialog box.
  2. Right-click Local Area Connection, and then click Properties in the shortcut menu.
  3. Click Internet Protocol (TCP/IP), and then click Properties.
  4. Change the preferred DNS server.

     2. Check the AD replication is working properly between your domain controller. Push a force replication.

How to do force replicate between Domain Controller :  http://technet.microsoft.com/en-us/library/cc816926(v=ws.10).aspx

  1. I ran the “NLTest” command for member server agai and see its working fine now.

3

4.  In few cases if you are not part od AD team and above setting does not help the issue, you can manually change the netlogon settings in member server for site name and fix as a work around.

From regedit, drill down the following:

HKLM\System\CurrentControlSet\Services\Netlogon\Parameters

Once you click Parameters, add a string word called “SiteName

Add the current site name to the entry and exit regedit.

Run command “nltest /Server:punlync2010 /dsgetsite” and verify output

Advertisements
Categories: Exchange 2013
  1. April 20, 2015 at 3:32 pm

    Thanks! I had this error and the registry key fixed it for me.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: