Welcome to the SharePoint Ocean. This blog help's you to Swim with perfection!! Thank You.
Monday, January 13, 2014
Sunday, January 12, 2014
The Security Token Service is not available. The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state
The Security Token Service is not available.
The Security Token Service is not issuing tokens. The service could be
malfunctioning or in a bad state.
(Or)
An exception occurred when trying to
issue security token: Could not connect to http://localhost:2843/SecurityTokenServiceApplication/securitytoken.svc.TCP error code 10061: No connection could be made because the target machine
actively refused it
(Or)
(Or)
The
Managed Metadata Service '' is inaccessible.
Solution:
Go to InetMgr(IIS manager)
1.
start the "SharePoint Web Services" site
2.
start the "SharePoint Web Services Root"
application pool
3.
Do IIS reset.
Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!
Friday, January 10, 2014
Lost SharePoint Farm Passphrase
Lost SharePoint Farm Passphrase
Sometimes,Unfortunatly we forgot the pass phrase given, there is no way to get
the old pass phrase but we can generate the new pass phrase by using the PowerShell.
Follow the below to get the new one.
Make sure that the account you are logged in as:
1. Farm
admin
2. Local
admin on server
Run the
following commands to get the new one.
·
$passphrase
= ConvertTo-SecureString -asPlainText –Force
·
Set-SPPassPhrase
-PassPhrase $passphrase –Confirm
Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!
Thursday, January 9, 2014
Microsoft Certification details of SharePoint 2013
Microsoft
Certification details of SharePoint 2013
Code Course Title Exam
Code
MS20331
Core Solutions of Microsoft SharePoint Server 2013
70-331
MS20332
Advanced Solutions of Microsoft SharePoint Server 2013 70-332
MS20488 Developing Microsoft SharePoint Server
2013 Core Solutions 70-488
MS20489 Developing Microsoft SharePoint Server
2013 Advanced Solutions 70-489
Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!
How to set the custom error attribute in SharePoint server 2013
How to set
the custom error attribute in SharePoint server 2013
Check the
below mentioned to set the custom error attribute to get the detailed error instead
of “sorry something went wrong”
Every change
you make in that config files have no effect on the web application. You have
to go the web.config file that is generated once the web application is
created.
So edit the
web.config file in C:\inetpub\wwwroot\wss\VirtualDirectories\your port number and modify the parameters you have indicated
in that web.config file
1. custom Errors mode must be
"Off"
2. compilation debug must be
"true"
3. Safe Mode Call Stack must be
"true"
The 'port
number' is the port you assigned when you created the Web Application in the
Central Administration
Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!
The tool was unable to install Application Server Role, Web Server (IIS) Roles as pre-requisites for SharePoint server 2013
The tool was unable to install Application Server
Role, Web Server (IIS) Roles as pre-requisites for SharePoint server 2013.
Issue: While installing SharePoint 2013 in a Windows 2012 Server was getting the following
error right after the prerequisites installation begins:
SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
Update\Reboot Required
Solution: To resolve the issue, we
need to set the Local policy. Follow the process below. Go to the paths in
below.
Go to server->windows start->MMC-> Click File, Add/Remove Snap-in-> Select Group Policy Object Editor and ADD it-> Navigate to Administrative templates / System-> Select and edit “Specify Settings for optional component installation and component repair”
Enable and select “Contract Windows Update
directly to download repair content instead of Windows Server Update Services
(WSUS)”
Re-run the prerequisite installation
Solution 2: run the command below
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regii -enable -i
Please Comment if You need Help!!!I am happy to assist.
Lables::
Installations,
SharePoint 2013
The Products Preparation Tool in SharePoint Server 2013 may not progress past Configuring Application Server Role, Web Server (IIS) Role
The Products
Preparation Tool in SharePoint Server 2013 may not progress past Configuring
Application Server Role, Web Server (IIS) Role
Issue: When you try to install Microsoft SharePoint Server 2013 on some Windows
Server 2012 configurations, the Products Preparation Tool may be unable to
correctly configure and install the required Windows Features for SharePoint.
If this occurs, the tool will continuously try to configure and install the
required features and then restart.
Solution:
We have Workarounds for
this issue. Follow the below steps to overcome the issue. It will work like
charm. Thanks to MS.
Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!
Add a Yammer feed to a SharePoint page
Add a Yammer feed to a SharePoint page
Detailed
article from Microsoft.
Thanks to
MS.
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 !!!!!
Lables::
Publishing,
Service Applications
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
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.
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 !!!!!
Subscribe to:
Posts (Atom)