SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Sunday, July 16, 2017

SharePoint web application creation - '' is an unexpected token. Expecting white space. Line 1, position 15478f

So this was interesting - a "lesson learned":

Setup of a new farm, all going well - tried to create a web application. It was created but show the message 'MD2' is an unexpected token. Expecting white space. Line 1, position 15478 and there was no link to create a site.

In my case, the "MD2" was the start of the names of the databases that were being created for the services.

What I thought could this be? Turns out the PowerShell scripts I was using was putting a space in the database name - i.e. "MD2 SessionState" due to an edit error.

The workaround is let it create then assign a site - however, the PROPER fix is to rebuild all services and be sure that there is NO space in the name.


The trust relationship between this workstation and the primary domain failed

Everyone's had this problem - I just wasted a day yesterday trying to fix on a set of VM's. An update to VMWare Workstation caused a bunch of network issues - tracking many of them down was a real pain.

So Kudos to http://implbits.com/active-directory/2012/04/03/dont-rejoin-to-fix.html on how to fix this issue. I recommend using the netdom method - simply login to the box with problem as an administrator, open a command prompt (using Run as administrator) then enter:

netdom resetpwd /s:<domain server name> /ud:<user with permissions, domain\name> /pd:<user password>

If not prompted, reboot anyway.

AS A SIDE EFFECT - your accounts will be a bit whacked, particularly if it is a server running application - be aware that you will have to reset the password for all system related accounts (application pools, etc.).

Some other issues that were encountered in my foray of fun yesterday:

Using NETDOM - the Target Name is Incorrect - the above corrects.

Using Remote Desktop - "The Local Security Authority Cannot Be Contacted" - simply reset the password of the account in Active Directory (Kudos: http://blog.mnewton.com/articles/solution-rdp-the-local-security-authority-cannot-be-contacted/).





Friday, July 14, 2017

So this one is a question! User Profile Service Page is BLANK!

So here's a question for all - working a development system, I suddenly noticed that I was unable to access Site Settings in any collection despite having full access. 

Took a while looking around but then found this:


Notice? There are NO OPTIONS on the page!

I'd love to get an answer if anyone has it - in the meantime, I rebuilt the User Profile Service - same problem!

I will post an answer if I can find it!

Monday, June 19, 2017

SharePoint Event ID 5586 - Target Principal name is incorrect. Cannot generate SSPI context.

Deploying a solution to SharePoint, it seemed to hang for a really long time. I ended up stopping the deployment to see what was up. Immediately thereafter, I could no longer connect to SharePoint at all.

In the Windows Application Event Log, I found multiple Event ID 5586 entries - basically saying "The target principal name is incorrect".

After a few hours of searching, I found one solution here:

http://www.jrjlee.com/2013/01/the-target-principal-name-is-incorrect.html *

* Note that he doesn't indicate that you have to adsiedit.msc to get to the entry (a little headscratching to figure that out).

Some say it worked for them, but it definitely did not work for me.

For one, there were no MSSQLSvc entries. For two, removing the RestrictedKrbHost entries condition went from bad to worse (new error: Unable to login to untrusted domain). I restored the RestrictedKrbHost entries just fine so I tried adding the MSSQLSvc entries and got "Name is not unique".

The final one that worked for me was:

Step 1) Logged on the AD Server and opened adsiedit.msc (Run as administrator)
2) Right clicked on the SQL Server entry and clicked Refresh:



3) Opened AD Users & Computers, right clicked on the account running SQL Services and clicked Unlock Account:


Hat tip to David Murdoch's post *:

http://www.davidmurdoch.com/2014/10/06/the-target-principal-name-is-incorrect-cannot-generate-sspi-context/

Note: his blog incorrectly says "Refresh" from Active Directory Users and Computers - you actually have to use adsiedit.msc.

Sunday, June 18, 2017

Event ID 6398 SharePoint User Profile Synchronization


Having seen this myself a number of times (and sick of having to look for the answer), there is an error that occurs in the User Profile Sync - Event ID 6398 - in the Event Viewer it looks like this:


Notice that the error is every minute! This will certainly fill up the logs!

The issue is quite simple - there are many fixes but turns out the problem in simply the Forefront Identity Manager Service is not running (or could be the Sync). Open Administration > Services (or use Run and type in services.msc) and locate the Forefront Identity Services:


Simply start the service(s) (right click and select Start). I am not sure what causes it to stop periodically but in this state, User Profile sync errors will continue frequently,.

Hat tip to this post:
https://social.technet.microsoft.com/wiki/contents/articles/24496.sharepoint-2013-event-6398-the-execute-method-of-job-definition-microsoft-office-server-userprofiles-userprofileimportjob-threw-an-exception.aspx

Saturday, June 3, 2017

Central Admin - Something Went Wrong - Access Denied

Had a client that was very upset having problems accessing things in Central Administration (often complainer but that's for another post). Reported 'items missing' in CA menus and when trying to retract a solution, kept getting:

Note the key element here: Access denied.

The issue is quite simple - they were not using the "Run as administrator" option when starting CA. There is a way to fix this permanently too (from another one of my posts).

Click Start then right click on the Central Administration icon and select "Open file location":

Right click on the CA link and select Properties:


Click the Advanced... button - click the checkbox next to "Run as administrator" and click OK:


Note that this ONLY applies to the icon - if you add CA to your startup in IE/Chrome/etc., that will still open without the proper permissions.


Tuesday, May 30, 2017

ASP Event ID 1309 SharePoint On-Premise 2016 Error Creating Lookup Field

This event is pretty standard for any 'non-handled' SharePoint Error - this one happens to be related to the inability to create a Lookup field. I had been working with a few apps installing/uninstalling. Suddenly when trying to create a Lookup Field, I get the innocuous ASP Event ID 1309. Looking into the error (you have to read it carefully), I found:

Feature '6b744ecb-82fc-4896-a981-1ad8dc5c47c2' for list template '10000' is not installed in this farm.

I had to check and it only affected one site - not happy about the time I spent on it but it appears that one app had installed a new List using that ID. Deleted the list and emptied the recycle bin. Returned to the site and it Crashed! It actually took a reboot to fix.

You be careful out there!