Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool named “User Profile Service Appl” already exists under the parent Microsoft.SharePoint.Administration. Rename your object or delete the existing object…
A way should be using another Application Pool, but at my new client they are “governance” geek and the Application Pool, Web Application, Managed Accounts and many other should be the same or at least follow the governance decided by the web architects.
So I couldn’t use the easy way and had to find another way to proceed: How to delete the older Application pools? They don’t show up in IIS Manager. There is then only 1 way to delete the application pools and that’s by using PowerShell!
User Profile Synchronization Service in DMZ with One Way Trust zone
You can find more information about the remove-spserviceapplicationpool on the official TechNet KB http://technet.microsoft.com/en-us/library/ff607921.aspx
If you have the same issue with deleting a Web Application you can try this solution:
Reference: http://wblo.gs/aeK
Now I could create my User Profile Service Application. I hoped not to receive any “starting” errors on my farm. I did not got it, but you can receive it and your service can be on STOPPED.
Probably, and the most of time, your User Profile will crash. You will see, you’re service will hang on User Profile Synchronization Service This is the most common issue, to resolve this: Be sure that Service Pack1 and cumulative updates are installed.
Mare sure that once you’ve updated hotfix for SharePoint 2010, you must use the command “psconfig -cmd upgrade -inplace b2b -wait” and then check product and patch installation status (Central Administration >Upgrade and Migration > Check product and patch installation status) For User Service Profile service account perspective, you must configure the following for this service account:
You will then need to use the following command to stop User Profile Service Application due to “Starting” forever.
Delete the existing User Profile service application and then re-provision one. After completely configuring properly permission for User Service Profile service account as well as re-provisioning a new User Profile service application, you start new User Profile service application and need to check FIM service. Make sure that two FIM services are started automatically. Don’t force it to start because let User profile service automatically does.
So I wanted to start the User Profile Synchronization Service from Spence Harbar’s blog where we can read that this is: A “SharePoint Service” in Services on Server. This is a wrapper responsible for the provisioning of the Forefront Identity Manager (FIM) bits. You select a UPS SA to associate with, and need to specify the credentials under which the FIM Services will run. This should run on the machine in the farm you wish to use to host the User Profiles “Role”. When it’s running that machine is known as the Service Machine Instance.
You can also read the TechNet Article about configuring the User Profile Synchronization on SharePoint 2010: http://technet.microsoft.com/en-us/library/ee721049(v=office.14).aspx
Following his steps my User Profile Service Application was set up perfectly but I couldn’t import data from Corporate Local into Corporate Extranet (DMZ). The User Profile Synchronization Service Proxy wasn’t operational.
User Profile Synchronization Service in DMZ with One Way Trust zone 3
In describing trust relationships, arrows illustrate the direction of trust between domains as follows:
Why couldn’t I getting any data? I surfed on TechNet and here the answer:
In Microsoft SharePoint Server 2010, some service applications can be shared across server farms.
By publishing a service application, you can optimize resources, avoid redundancy, and provide enterprise-wide services without installing a dedicated enterprise services farm. You can publish the following service applications in a SharePoint Server 2010 farm:
Clearly I have 2 domains (DMZ and LOCAL) with only “one way trust” and not a Full Trust, Multi Trust, Bidirectional Trust or whatever.
You can read the article on TechNet: http://technet.microsoft.com/en-us/library/ff621100(v=office.14).aspx
On SharePoint 2013 it’s the same and without A Multi Trust we can’t have working USPA Proxy: http://technet.microsoft.com/en-us/library/ff621100(v=office.15).aspx
If my company decides to implement a multi –or Full trust on the infrastructure then we could be able to get data from our publishing farm.
The farm that contains the service application and publishes the service application so that other farms can consume the service application is known as the publishing farm. The farm that connects to a remote location to use a service application that the remote location is hosting is known as the consuming farm.
You can check Proxy Configuration issues with User Profile Syncronization in SharePoint 2010/2013: http://blogs.msdn.com/b/spses/archive/2012/12/17/proxy-configuration-issues-with-upa-in-sharepoint-2010-2013.aspx
There isn’t a proper solution yet but a backup restore of the User profile Databases are more than enough to get data in the User Profile. We are doing this one time a week but for the second line, it’s a bit enoying and I can understand. I will post the solution when I will find it!
The temporary solution:
2. Restore the Profile DB and Social DB from backup on the SQL Server
3. Start the User Profile Service and User Profile Synchronization Service in Central Admin.
Happy SharePointing!
Gokan
Ed Price - MSFT edited Revision 6. Comment: Title casing
Ed Price - MSFT edited Revision 5. Comment: TOC, tags
Gokan Ozcifci edited Revision 1. Comment: style
Gokan Ozcifci edited Original. Comment: style