SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Tuesday, October 27, 2015

The Trust Relationship Between This Workstation And The Primary Domain Failed

So every now and then, I've come across the error when trying to login to a server:

The Trust Relationship Between This Workstation And The Primary Domain Failed

There are a number of reasons this can happen - basically it means that the Domain Controller and the Server are not communicating. For example, if a domain controller goes down and the server brought up, it cannot communicate to authenticate the server in the domain. This can also happen when system recoveries are necessary or when restoring a Virtual Machine.

One method (though not the best) is to simple login to the server as an Administrator, go to the System Properties, leave the domain by specifying a temporary workgroup name (you'll need the AD Administrator account & password), reboot then join the domain again.

However, there are two better ways to do this by simply resetting the Server Password in Active Directory from the Server you are having issues with. Login as the Server Administrator then via a Command Line (using Run as Administrator), enter the following:

netdom.exe resetpwd /s:<AD server name> /ud:<user name> /pd:*

Where 'AD server name' is the name of the Active Directory server and 'user name' is an account (in format of domain\name) that has permssions in AD.

Note that when you enter this command, it will prompt for a password to the account you specified.

Alternately, you can use PowerShell:

Reset-ComputerMachinePassword [-Credential <PSCredential>] [-Server <String>]

Where 'PSCredential' is the login name and 'String' is the name of the domain controller. For more info on the PowerShell command, see here:

Once either of these methods are used, I suggest rebooting the server - when it comes back up, login with a domain account.

Tuesday, October 6, 2015

Some interesting changes for SharePoint 2016

Overall, SharePoint 2016 is simply an upgrade to 2013. One significant change is that Server Roles must be assigned when installing (i.e. web front end, etc.) and the Distributed Cache role is also new (as a setting that is – 2013’s streamlined model accounted for this role though most folks didn't use it). It is clear that it will require a few more servers in your average farm.

There are some cosmetic changes to the site templates (they changed the header a little bit – site settings now in a new black bar at the top of the page):

Overall, the installation process and adding servers is pretty much the same. All of the service applications are the same – and surprisingly, PerformancePoint is still available (Microsoft hinted at dropping that two years ago). They did add a new service for Project Server (see below). Site deployment remains the same and templates are the same as 2013.

As for features, annoyingly, the Access App feature is automatically enabled meaning you have to turn it off it you don't want your users using that (the security issues around Access still remain). This time though, they did expand on the explanation of what it’s for (in 2013, it just said Access web app).

They have added some new ones (not sure if this represents a merge of Project Server but sure looks like it; since this is preview, they might not include these in the final):

  • Announcement Tiles - Enables Announcement Tiles feature and adds the webpart to the site.
  • Project Proposal Workflow - Provides a review workflow for managing project proposals.
  • Project Web App Connectivity - Provides the lists required within a Project Site for integration with Project Web App including issues, risks, and deliverables.
  • Project Server Approval Content Type - This content type is used by the Project Server Approval workflow
  • Project Web App Permission for Excel Web App Refresh - When this feature is active, users can refresh reports containing Project Web App data within Excel Web App.
  • Project Web App Ribbon - Contains the ribbon controls for Project Web App pages.
  • Project Web App Settings - Project Web App PMO Settings
  • Sample Proposal - Sample workflow for Project Server

The Services on Server has changed a bit too, in addition to the Roles, they’ve added a new Restart option and an indicator if the Service is in Compliance (not 100% on the last one, but would appear to be based on the Role of the server):

Probably the biggest changes is the new 2016 Hybrid Feature – this allows connection to Office 365 and OneDrive:
“With hybrid features, you can take a best-of-both-worlds approach by providing access to Office 365 productivity services and offerings directly within SharePoint Server 2016. To learn more about SharePoint hybrid solutions, visit the 'SharePoint Hybrid Solutions Center' (”

So – there you have it! As the preview, Microsoft is usually around 3 months to customer release – I expect we’ll see the final in December!

Troubles installing SharePoint 2016

If you are working with the pre-release SharePoint 2016 preview, you may get an error when trying to install. The error in the System Event Application log - Event ID 5586 shows the error as:

Unknown SQL Exception 53 occurred. Additional error information from SQL Server is included below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

There are a variety of reasons this may occur, most notable:

1) Not using a SQL Alias - this has been a problem will all SharePoint versions. If you attempt to use the SQL instance name it will work - sort of. If it is the default instance you might be OK but usually services like the User Profile will not. If you've not setup an alias before, the command is "cliconfg". Be sure to enable TCP/IP and Named Pipes (with TCP/IP as the priority).

2) An actual network problem - some have experienced this in networks where the DNS is flakey; often adding all of the farm servers to the Hosts file (on all servers) will correct.

3) Incorrect settings in SQL Server - if SQL is set to Named Pipes vs. TCP/IP, this will occur.

4) Something else - sometimes, simply re-running the installation will 'fix' the issue. I had this occur on a fresh system; I rebooted and ran again and the install completed.

Hope this helps!