Friday, January 3, 2014

Publishing service applications in sharepoint

Publishing service applications in sharepoint
                                                                                                   

          
               
Follow the below steps to publish the service applications between different farms.

Setting Up the Farm Trust

1. On the publishing server, create a folder at c:\PubCerts.

2. From the publishing server, open the SharePoint 2013 Management Shell. To get the certificate, type the following line and press Enter

        $rootCert = (Get-SPCertificateAuthority).RootCertificate

3. To export the certificate, type the following line and press Enter:

$rootCert.Export("Cert") | Set-Content C:\PubCerts\PublishingRoot.cer
-Encoding byte

4. Copy the c:\PubCerts folder from the publishing server to the consuming server.

5. On the consuming server, create a folder at c:\ConsumerCerts.

6. From the publishing server, open the SharePoint 2013 Management Shell.

7. To get the certificate, type the following line and press Enter:

          $rootCert = (Get-SPCertificateAuthority).RootCertificate

8. To export the certificate, type the following line and press Enter:

$rootCert.Export("Cert") | Set-Content C:\ConsumerCerts\ConsumingRoot.cer
-Encoding byte

9. To get the STS certificate, type the following line and press Enter:
$stsCert =(Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate

10. To export the STS certificate, type the following line and press Enter:
$stsCert.Export("Cert") | Set-Content "C:\ConsumerCerts\ConsumingSTS.cer"
-Encoding byte

11. Copy the c:\ConsumerCerts folder to the publishing server.

12. Still on the consuming server, to load the publishing server’s certificate, type the following line and press Enter:

$trustCert = Get-PfxCertificate "C:\PubCerts\PublishingRoot.cer"

13. To set up the trust using the certificate, type the following line and press enter:
New-SPTrustedRootAuthority PublishingFarm -Certificate $trustCert

14. Return to the Management Shell on the publishing server.

15. To load the consuming server’s certifi cate, type the following line and press Enter:
$trustCert = Get-PfxCertificate "c:\ConsumerCerts\ConsumingRoot.cer"

16. To set up the trust using the certificate, type the following line and press Enter:

New-SPTrustedRootAuthority Collaboration -Certificate $trustCert

17. To load the consuming server’s STS certificate, type the following line and press Enter:

$stsCert = Get-PfxCertificate "c:\ConsumerCerts\ConsumingSTS.cer"

18. To add the STS certificate to the trust, type the following line and press Enter:
New-SPTrustedServiceTokenIssuer Collaboration -Certificate $stsCert

19. Return to the Management Shell on the consuming server.

20. Type the following line and press Enter:
Get-SPFarm | Select Id

21. Record that GUID for use later.

22. Return to the Management Shell on the publishing server.

23. To get the security object for the Application Discovery and Load Balancer service
application, type the following line and press Enter:
$security = Get-SPTopologyServiceApplication |
Get-SPServiceApplicationSecurity

24. To get the farm’s claim provider object, type the following line and press Enter:
$claimProvider = (Get-SPClaimProvider System).ClaimProvider

25. To set up the new claim principal for the consuming farm, type the following line and press
Enter:
$principal = New-SPClaimsPrincipal -ClaimType "http://schemas.microsoft.com
/sharepoint/2009/08/claims/farmid"
-ClaimProvider $claimProvider
-ClaimValue <Type the ID from Step 21, don't include the <>>

26. To give that principal permission in your publishing farm to the Application Discovery and
Load Balancer service application, type the following line and press Enter:
 Grant-SPObjectSecurity -Identity $security -Principal $principal
-Rights "Full Control"

27. To set the access just given, type the following line and press Enter:
 Get-SPTopologyServiceApplication | Set-SPServiceApplicationSecurity
-ObjectSecurity $security

That completes the process of establishing a trust between the two farms so that the publishing server can serve up service applications to the consuming farm. If you want to look at the trusts or possibly remove one, you can do that through the GUI by navigating to Central Administration ➪Security ➪ Manage trust.

Publishing a Service Application

For this task, you could dive back into Power Shell or you could use the GUI in Central

For this example, you will publish a Managed Metadata service application:

1. On the publishing server, open Central Administration.

2. Navigate to Application Management ➪ Manage service applications.

3. Click to the right of the service application you want to make available.

4. In the Ribbon, click Publish.

5. On the Publish Service Application page, check the box for “Publish this Service Application to other farms.”

6. For the Publish URL, copy all of the string that begins with “urn:” and ends with “.svc.”
For example, it will be similar to the following:
urn:schemas-microsoft-com:sharepoint:service:ac40e8f87daa43d9bec93f9fa99360c7
#authority=urn:uuid:de389296913c4f00b7970f50ea298fd4&authority=
https://server:32844/Topology/topology.svc

7. Scroll down the page and click OK.

8. Click to the right of the service application.

9. From the Ribbon, click Permissions.

10. Enter the farm ID of the consuming farm (refer to step 21 in the previous section, “Setting
Up the Farm Trust”). Click Add.

11. Highlight the remote farm: <Your Farm ID>.

12. For permissions, check the box to assign the permissions you wish to give to the remotefarm. The permissions available will vary according to the service application being published.

13. Open Central Administration on the consuming farm and navigate to Application
Management ➪ Manage service applications.

14. From the Ribbon, click Connect.

15. Enter the URL for the service application you want to access from step 6 in this section.

Click OK.

16. Click the service application name so that it is highlighted in yellow.

17. You can specify whether this service application should be included in the default service application group. When you are done, click OK.

18. Either accept the default connection name or enter your own. When you are fi nished,

click OK.

19. At the Success screen, click OK.


You can now work with the service application just as if it were part of your farm. 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Service Application Commands

 Service Application Commands
                              


To get most of the cmdlets about service applications, run the following command from the SharePoint Management Shell:

                Get-Command *service application*


We will get all the commands related to service applications.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

HTTP 500 Internal Server Error in SharePoint 2013

 HTTP 500 Internal Server Error in SharePoint 2013

                            


issue with one of web site created.

Issue: Website cannot display the page due to HTTP 500 Internal Server Error.
 I tried to do  open SharePoint Central Administration, to see if I get the same error message. Strangely, I was able to open Central Administration without any errors.

  
I opened IIS Manager to make sure SharePoint – 80 Application Pool was running, and I noticed that SecurityTokenServiceApplicationPoolapplication pool was stopped.
                      


 I started SecurityTokenServiceApplicationPool application pool, refreshed my SharePoint site but that didn’t resolve the issue. I opened IIS manager and noticed
that SecurityTokenServiceApplicationPool was stopped again.

I Check the  IIS events log to check what’s the issuewith SecurityTokenServiceApplicationPool application pool

 The IIS event log showed the warning ID 5021:
The identity of application pool SecurityTokenServiceApplicationPool is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request.  If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
In order to resolve this problem I navigated back to IIS manager 

SecurityTokenServiceApplicationPool application pool-> Advanced Settings.
                     

 Navigated to the Identity option.
                                                


Updated the user’s credentials and clicked on OK.       
         


I performed iisreset.
  
And opened IIS manager again to check if it

worked. SecurityTokenServiceApplicationPool was now started and didn’t stop anymore.
  
My SharePoint 2013 site was working again!
 Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

October CU 2013 detailed Installation Guide

OCT CU 2013 detailed Installation Guide

Pre-requisites :
-       Ensure backup is already done to farm and databases.

      Note:Downtime Required

Step 1: Stop World Wide Web Publishing Service in all SharePoint Servers
                                              
                             

Step 2: Perform CU installation in the following orders if It’s a Multi server Farm.
                1 – Central Admin server
             2 – Application Servers
             3 – Web Front End Servers

   If It’s a standalone server, Just do on one server.

Installation Steps:

Step 1: Download the CU from below MS site.
               http://support.microsoft.com/kb/2825786

Step 2 : Double click on the “ubersrv2010-kb2825786-fullfile-x64-glb” to start the installation.

Step 3 : Check the “Click here to accept the Microsoft Software License Terms” and hit “Continue”
                      


Step 4 : A window will prompt and wait              
                        
  
Extracting in progress, This take some time
                         


Determine the list to be updated:

Step 5 : please wait while the update is installed. 

Please Click on Yes to reboot the server            
                     


Click OK to complete the installation.

Step 6:
NOTE:, you may check in CA >system settings-> Manage Servers in this farm. You will see the status is now under  “Upgrade Block” For Multi server Farm.                           
                         
                                                                               
Installation Required : The server still not yet install with the same CU that already installed in other servers.
Upgrade Blocked : The server is blocked from upgrade. Server is install with latest CU and it will remained blocked until all the SP servers in the farm are installed with the same version.Once all installed with CU,below screen show.
                                       

Note : the below is a Single server Farm, so status is Upgrade Available.
                                       


Step 7 :  Repeat Step 1 to Step 6 in other SP Servers. (App servers then follow by WFE servers)

NOTE: After CU is installed to all servers and rebooted in Multi server farm. The status would change to “Upgrade Available”

                                 

Step 8 : Run the SharePoint 2010 Products Configuration Wizard in CA server.

Step 9 : Click “Next” to the SharePoint Products Configuration Wizard window.
                               

Click “Yes” to continue
            

Click “Next to Continue                   

Configuration in progress                                                         

Upgrade completed, click “Finish” to end.

Step 10 : Repeat Step 8 to Step 9 other SP Servers. (App servers then follow by WFE servers)

Step 10 : Verify on the installation.
a.     Check SP version in central admin:
CA > Under “System Settings” > Select “Manage Servers in this Farms” > Ensure the version has change to “14.0.7108.5000”
                                             

Check SP servers control panel:
Control Panel > Programs and features > at left pane, click on “ View installed Updates” > Ensure “KB2825786” is in the list.
               


Check in SP power shell:
Open the SharePoint 2010 power shell
                                                                                                          

Type the following:
(get-spfarm).buildversion
Ensure it shows something like 14 0 7108 5000
                                                
           
Note: Maybe you'll notice that after installing, the Config DB version is 14.0.7108.5000 instead of 14.0.7110.5000. No worries that it's because of the SEARCH dlls have been released as a version higher 14.0.7110.5000 than the SharePoint dlls 14.0.7108.5000 .

If You get the Error Installation of the package failed see Solution at http://expertsharepoint.blogspot.de/2014/01/installation-of-package-failed-while.html

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!
Related Posts Plugin for WordPress, Blogger...

ShareThis

X