Showing posts with label Service Applications. Show all posts
Showing posts with label Service Applications. Show all posts

Tuesday, July 25, 2017

Service Applications in SharePoint 2013

Service Applications in SharePoint 2013:


The below are the service applications which are Exist in SharePoint server 2013 Version. Each service application will be used for different functions and the steps to Enable the service is different. Please find the below list of service Applications.
  1. Access Service
  2. Access Service 2010
  3. App Management Service
  4. Business Data Connectivity Service
  5. Excel Services Application
  6. Machine Translation Service
  7. PerformancePoint Service
  8. PowerPoint Automation Service
  9. Managed Metadata Service
  10. Search Service
  11. Secure Store Service
  12. State Service
  13. User and Health Data Collection Service
  14. User Profile Service
  15. Visio Graphics Service
  16. Word Automation Services
  17. Work Management Service
  18. Microsoft SharePoint Foundation Subscription Settings Service


The type of service applications in SharePoint is differ from version to version. In some versions its new application and in other it’s the existing service applications are deprecated.


 I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Wednesday, June 28, 2017

Creation of Secure Store Service in SharePoint

Creation of  Secure Store  Service in SharePoint:


Please follow the steps below to create a Secure store service in SharePoint.
  1. Register a managed account in SharePoint Server 2013 to run the Secure Store application pool.
  2. Start the Secure Store Service on an application server in the farm.
  3. Create a Secure Store Service application.
To run the application pool, you must have a standard domain account. No specific permissions are required for this account. Once the account has been created in Active Directory, follow these steps to register it with SharePoint Server 2013.
To register a managed account :


  1. On the SharePoint Central Administration Web site home page, in the left navigation, click Security.
  2. On the Security page, in the General Security section, click Configure managed accounts.
  3. On the Managed Accounts page, click Register Managed Account.
  4. In the User name box, type the name of the account.
  5. In the Password box, type the password for the account.
  6. If you want SharePoint Server 2013 to handle changing the password for the account, select the Enable automatic password change box and specify the password change parameters that you want to use.
  7. Click OK.
To start the Secure Store Service
 
On the Central Administration home page, in the System Settings section, click Manage services on server.
  1. Above the Service list, click the Server drop-down list, and then click Change Server.
  2. Select the application server where you want to run the Secure Store Service.
  3. In the Service list, click Start next to Secure Store Service.
Once the service is started, you must create a Secure Store Service application. Use the following procedure to create the service application.
To create a Secure Store Service service application


  1. On the Central Administration home page, in the Application Management section, click Manage service applications.
  2. On the Manage Service Applications page, click New, and then click Secure Store Service.
  3. In the Service Application Name box, type a name for the service application (for example, Secure Store Service).
  4. In the Database Server box, type the instance of SQL Server where you want to create the Secure Store database.
  5.     Select the Create new application pool option and type a name for the application pool in the text box.6.    Select the Configurable option, and, from the drop-down list, select the account for which you created the managed account earlier.
  6. 7.    Click OK.
 


The Secure Store Service has now been configured. The next step is to generate an encryption key for encrypting the Secure Store database.
 


Please find the TechNet below for the details of creation of Secure store DB.
 
https://technet.microsoft.com/en-us/library/ee806866.aspx


  

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Thursday, October 15, 2015

Delete a service application in SharePoint 2013

 Delete a service application in SharePoint 2013


service applications can be deleted by using the SharePoint Central Administration website or by using Windows Power Shell 3.0 cmdlets.

Before deleting a service application, verify that its removal will not adversely affect users. As a best practice, you should ensure that no web applications are currently consuming the service application that you are going to delete. 

When you delete a service application, you have the option of also deleting the service application database. Some service applications do not have databases. If you plan to create the service application again in the future, do not delete the service application database. If the service application is temporary, you will most likely want to delete the database during this operation.

How to delete by the CA: Please follow the steps below to delete the Service Application by the GUI in CA.

1.    Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
2.    On the SharePoint Central Administration website, click Application Management, and then click Manage service applications.
3.    On the Manage Service Applications page, click the row that contains the service application that you want to delete. The ribbon becomes available.
4.    On the ribbon, click Delete.
5.    In the confirmation dialog box, select the check box next to Delete data associated with the Service Applications if you want to delete the service application database. If you want to retain the database, leave this check box cleared.
6.    Click OK to delete the service application, or click Cancel to stop the operation

How to delete by using the Power Shell: Please follow the steps below to delete by using the power shell commands.
  1. Ensure  that you meet the following minimum requirements:
·         You must have membership in the securityadmin fixed server role on the SQL Server instance
·         You must have membership in the db_owner fixed database role on all databases that are to be updated.
·         You must be a member of the Administrators group on the server on which you are running the Windows Power Shell cmdlet.

2.Start the SharePoint 2013 Management Shell.

2.    To retrieve the service application that you want to delete, type the following command: 

$spapp = Get-SPServiceApplication -Name "<Service application display name>"


3.    To delete the selected service application, run either of the following commands. In both cases, you are prompted to confirm the deletion. 

·         To delete the selected service application without removing the service application database, type the following command:

Remove-SPServiceApplication $spapp
·To delete the selected service application and also delete the service 
application database, type the following command:

Remove-SPServiceApplication $spapp -RemoveData

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, September 1, 2015

Upgrade service applications to SharePoint 2013



Upgrade service applications to SharePoint 2013

Details: Upgrade service applications (Business Connectivity Services, Managed Metadata, Secure Store, User Profiles, Search) to SharePoint 2013.

When you upgrade from SharePoint 2010 Products to SharePoint 2013, you must use a database attach upgrade, which means that you upgrade only the content for your environment and not the configuration settings. After you have configured the SharePoint 2013 environment, and copied the content and service application databases, you can upgrade the service applications to SharePoint 2013. This article contains the steps that you take to upgrade the service applications.

A very useful Article from MS explaining in very detail about the upgrade of the service applications.


 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, December 30, 2014

how to create service application proxy for existing service application (or) Object reference not set to an instance of an object



how to create service application proxy for existing service application (or)
Object reference not set to an instance of an object.

Issue: issue with User Profile service application which was stopped working.

Solution1:Please follow the steps to solve above issue.

1.    you have to delete your service application proxy from central administration -> manage service applications page.

2.    run this on Power shell. this will show you all service applications of your farm

Get-SPServiceApplication

3.    get the name of User Profile Service Application or you can copy name from central admin also.

$upa = Get-SPServiceApplication -Name “User Profile Service Application”

4.    then  need to create new service application proxy.

 New-SPProfileServiceApplicationProxy  -Name “User Profile Service Application Proxy”  -ServiceApplication $upa  -DefaultProxyGroup

Do an IISRESET.

Solution 2:if the above doesn’t fix the issue. Reset the application pool account for Token Service.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, July 8, 2014

The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator



The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator

Issue: While using Performance Point’s Dashboard Designer, I received the following error. The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.

Exception Details: The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.
Inner Exception Message:
Stack Trace: at Zicrosoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation analyticReportViewLocation, BIDataContainer biDataContainer)
at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.ExtractReportViewData()
at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.CreateRenderedView(StringBuilder sd)
at Microsoft.PerformancePoint.Scorecards.ServerRendering.NavigableControl.RenderControl(HtmlTextWriter writer)

Performance Point Services error code 20604.

Cause: The performance point is not working as expected is of many reasons.

Solutions: Ensure to check the below to work the PP service as expected.

1.   Performance Point doesn't support claims-based authentication.

2.   Make sure the account you use to logon the server has proper permissions to the data connection list since when SharePoint open dashboard designer from client side, it use the current account of the server not the current account of the SharePoint site.

3.   Ensure  the web app pool identity have permissions to connect to performance point service application.

4.   Ensure to configure the unattended service account


6.   The service account that runs the IIS app pools had to be added as a reader in the BI Center.
 

 

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