Error on manage user properties page–your search encountered an error

Hi all!

A colleague, told me that he was facing an strange error in when he tried to modify some user properties in a SharePoint Server 2013 – he got the following message “Your search encountered an error. If the problem persists, contact the portal site administrator”

Firstly, I checked search but I saw no errors in there – it seems that the error description is not really guiding you in the correct direction. The solution was as simply as starting the ForeFront Identity Manager Service in the services CMD.

Cheers!

User Profile Synchronisation Errors In SharePoint 2013

While setting up the User Profile Synchronization services on SharePoint  I had a couple of warnings and errors that I had to address:

Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’, component ‘{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}’ failed.  The resource ‘C:Program FilesMicrosoft Office Servers14.0ServiceMicrosoft.ResourceManagement.Service.exe’ does not exist.

Followed by event 1001:

Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’ failed during request for component ‘{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}’
These were repeated for another component GUID.

And event 1015:

Failed to connect to server. Error: 0x80070005

These were repeated for another component GUID

The reason is that the WMI calls are made under the credentials of Network Service account and that this account doesn’t have permissions on the folder indicated in the event.

After I gave the Network Service account read and execute permissions on the “C:Program FilesMicrosoft Office Servers15.0” folder the events didn’t reappear.

Also, is it posible to give this permissions by PowerShell:

$Acl = (Get-Item "E:Microsoft Office Servers15.0").GetAccessControl('Access')
$Ar = New-Object system.security.accesscontrol.filesystemaccessrule("NT AUTHORITYNETWORK SERVICE","Read, ReadAndExecute, ListDirectory", "ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Ar)
Set-Acl "E:Microsoft Office Servers15.0" $Acl

Hope it helps!

Problems to crawl User Profile properties

Hi all, this a note for myself but I wanted to explain to everyone to not to happen again.

The problem was the following: a client has to create a new Test SharePoint farm because the other one that they had, became corrupt, so the simply solution was to recrete, until here, no problem.

We recreate the farm, with the help of AvePoint products we recreated from the Prodeuction scenario, the Managed Metadata Service Application and the content databases from the portal, so every content was updated.

For several reasons, we need to recreate the User Profile Service Application and the Search Service Application by PowerShell (or by the interface, doesn´t matter), and in the User Profile we recreate the same properties as in production, with the same linked attributes from the AD.

So, once this is were done, we started a full crawl in the search to crawl all the new properties. However, when the crawl finished, the properties were not crawled, and the problem begun here…

First of all, we checked the crawl log to confirm if there were problems in thew crawling: No luck 😦

Then we check the checkbox in the Search Service Application to give permission to the Search Account to retrieve User Data profiles:

dc1 dc2

For my surprise it was no checked, so I checked the property and I started again a Full Search crawl…. nothing again, it begins to be annoying and weird

To be sure that the new properties created has values, I enter into the profile of each user to check if they have values, and yes, indeed all users have values in their new properties.

I was sure that something was missing, it was very strange that something it is “easy” becomes such pain. So I decided to start from the beggining: https://technet.microsoft.com/en-us/library/jj219651.aspx

So I check very step to provision correctly the User Profile, and I was shocked when I realized that I forgot to include in Content Source of the Search Service App, the protocol sps3…. Once I added this url I started again a full search crawl and magically the new properties started to appear in the search schema, so it was possible for me to start to create new managed properties to do a Search Directory…

Conclusion: it was a silly thing, but it stuck me several hours of troubleshooting, I expect to not to forget again that simply thing

User Profile Service not starting

Today I faced a weird problem. This time I was preparing a SharePoint farm for one of our developers, but when I was trying to start the User Profile Service App, it doesn’t start. At the begginig I was mad, because I made this process tons of times, and it was the first time that this service was driving me crazy.

When I tried to start the service, I checked the Event Viewer log to see what is happening and saw the following error:

The server encountered an unexpected error and stopped.

“BAIL: MMS(8164): sql.cpp(2325): 0x80230404 (The operation failed because the attribute cannot be found)

ERR: MMS(8164): storeimp.cpp(5790): Failed to get computer id info from db.

BAIL: MMS(8164): storeimp.cpp(5792): 0x80230447 (Service start up has failed. Cannot read computer_id from the FIM Synchronization Service database.)

BAIL: MMS(8164): storeimp.cpp(5869): 0x80230447 (Service start up has failed. Cannot read computer_id from the FIM Synchronization Service database.)

BAIL: MMS(8164): storeimp.cpp(482): 0x80230447 (Service start up has failed. Cannot read computer_id from the FIM Synchronization Service database.)

BAIL: MMS(8164): server.cpp(388): 0x80230447 (Service start up has failed. Cannot read computer_id from the FIM Synchronization Service database.)

BAIL: MMS(8164): server.cpp(3860): 0x80230447 (Service start up has failed. Cannot read computer_id from the FIM Synchronization Service database.)

BAIL: MMS(8164): service.cpp(1539): 0x80230447 (Service start up has failed. Cannot read computer_id from the FIM Synchronization Service database.)

ERR: MMS(8164): service.cpp(988): Error creating com objects. Error code: -2145188793. This is retry number 0.

BAIL: MMS(8164): clrhost.cpp(224): 0x80131022

BAIL: MMS(8164): scriptmanagerimpl.cpp(7670): 0x80131022

BAIL: MMS(8164): server.cpp(251): 0x80131022

BAIL: MMS(8164): server.cpp(3860): 0x80131022

BAIL: MMS(8164): service.cpp(1539): 0x80131022

ERR: MMS(8164): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 1.

BAIL: MMS(8164): clrhost.cpp(224): 0x80131022

BAIL: MMS(8164): scriptmanagerimpl.cpp(7670): 0x80131022

BAIL: MMS(8164): server.cpp(251): 0x80131022

BAIL: MMS(8164): server.cpp(3860): 0x80131022

BAIL: MMS(8164): service.cpp(1539): 0x80131022

ERR: MMS(8164): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 2.

BAIL: MMS(8164): clrhost.cpp(224): 0x80131022

BAIL: MMS(8164): scriptmanagerimpl.cpp(7670): 0x80131022

BAIL: MMS(8164): server.cpp(251): 0x80131022

BAIL: MMS(8164): server.cpp(3860): 0x80131022

BAIL: MMS(8164): service.cpp(1539): 0x80131022

ERR: MMS(8164): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 3.

BAIL: MMS(8164): service.cpp(1002): 0x80131022

Forefront Identity Manager 4.0.2450.47”

I have to say that this machine was a SharePoint 2013 RTM with any CU installed and configured with a SQL Server 2014.

So, after applied CU April 2013, the problem was solved

Hope that helps

Sharepoint 2013: Error User Settings Not Initialized

Today I faced a weird error, one user had the error whereby whenever they loaded SharePoint they were confronted with the error “Error: User Settings Not Initialized”.

1

If the user clicks on return to original page, he/she can successfully Access to the web page, but sometimes it does not do the trick, so what we can do?

In order to mend the error, open the User Profile Service Application from Central Administration. Next, click on Manage User Profiles and search for the affected user. select Edit My Profile.

Scroll right down to the bottom of the profile screen and choose always use my personal settings and choose the acceptable locale. Next, tick Use language and regional settings. Click save and close.

2

The error should now have been resolved.  You can go back into the user profile and reset the two options you just changed.

Hope it helps!

How To Create the UPA from Powershell

Creating the User Profile Service Application (UPA) via Powershell is a fairly straightforward process. We only have to follow these steps:

  1. Set Parameters
  2. Create the Service Application
  3. Create the Service Application Proxy and associate it to the Proxy Group
  1. Set Parameters: First of all we have to set the parameters we will use for the service application.
  • Name for your User Profile Service Application
  • $UPAName = “70331_UserProfile”
  • Application Pool: You can create a specific one or use an existing one. I recommend to use the same Application Pool for all service applications. In my case, I am assigning the existing application pool called “ServiceApplications” to the $appPool variable:
  • $AppPool = Get-SPServiceApplicationPool –Identity “ServiceApplications”
  • Database Names: UPA uses three distinct databases: Profile, Social and Profile. Try to follow the convention rule you have for your farm databases. $SocialDB = “70331_UserProfile_SocialDB”
  • $SyncDB = “70331_UserProfile_SyncDB”
  • $ProfileDB = “70331_UserProfile_ProfileDB”
  • Proxy Name: Type a name for the Proxy/connection of the UPA
  • $UPAProxy = “70331_UPA_Proxy”
  1. Create the Service Application: Use the New-SPProfileServiceApplication cmdlet for this purpose and use the recently created parameters and collect the result in the $UPA variable so as to use it later in the Proxy creation.

$UPA=New-SPProfileServiceApplication -Name $UPAName -ApplicationPool $appPool -ProfileDBName $ProfileDB -SocialDBName $SocialDB -ProfileSyncDBName $SyncDB

  1. Create the Service Application Proxy: Use the New-SPProfileServiceApplicationProxy cmdlet and the parameters configured above. Use the option DefaultProxyGroup if you want to include the proxy into the default group.

New-SPProfileServiceApplicationProxy -Name $UPAProxy -ServiceApplication $UPA –DefaultProxyGroup

  1. If you did not associate the user profile proxy to the default proxy group and you want to associate it to a custom one, do the following:

#Get the list of Proxy Groups and copy the Friendly Name of the Proxy group you need.

Get-SPServiceApplicationProxyGroup

$proxyGroup=Get-SPServiceApplicationProxyGroup -Identity “Intranet Only”

#Get the list of proxies/connections, copy the typename of the UPA proxy and use it for assigning it to the $proxy variable

$proxy=Get-SPServiceApplicationProxy | ? {$_.TypeName -eq “User Profile Service Application Proxy”}

#Use the Add-SPServiceApplicationProxyGroupMember cmdlet to add the UPA proxy to your custom ProxyGroup

Add-SPServiceApplicationProxyGroupMember -Identity $proxygroup -Member $Proxy

That´s all, hope it helps!