Document conversion load balancer unavailable

Issue: Document conversion load balancer unavailable

Summary:   The Document Conversions Load Balancer Service manages the availability of document converters. Stopping the service stops the document conversion process and turns off the Document Conversions Launcher Service. To resume the document conversion process, you must restart the Document Conversions Load Balancer Service, and then start the Document Conversions Launcher Service.

Symptoms:   One or more of the following symptoms might appear:

1.     Documents are not being converted.

2.     Only one server seems to be converting documents.

3.     The Document Conversions Load Balancer Service is not running.

Cause:   The Document Conversions Load Balancer Service is no longer running. This can occur when an administrator unintentionally stops the service or the server runs out of RAM.

Resolution:   Restart the Document Conversions Load Balancer Service

1.    On the SharePoint Central Administration Home page, in the System Settings section, click Manage services on server.

2.    On the Services on Server page, click Document Conversions Load Balancer Service.

3.    In the Select Server section, verify that the server that you want is selected. If it is not selected, on the Server menu, click Change Server.

4.    On the Select Server page, click the name of the server on which you want to run the Document Conversions Load Balancer Service.

5.    In the Communication Scheme section, select the scheme that you want the load balancer to use for communication. The default is http.

6.    In the Port Number section, type the port number that you want the load balancer to use for communication. Choose a port number that is not used by other services on the server, but which is open in the firewall on the server.

7.    Click OK.

Resolution:   Restart the Document Conversions Launcher Service

1.    On the SharePoint Central Administration Home page, in the System Settings section, click Manage services on server.

2.    On the Services on Server page, click Document Conversions Launcher Service.

3.    In the Select Server section, verify that the server that you want is selected. If it is not selected, on the Server menu, click Change Server.

4.    On the Select Server page, click the name of the server on which you want to run the Document Conversions Launcher Service.

5.    In the Communication Scheme section, select the scheme that you want the launcher to use for communication. The default is http.

6.    In the Port Number section, type the port number that you want the launcher to use for communication. Choose a port number that is not used by other services on the server, but which is open in the firewall on the server.

7.    Click OK.

Note: You must be a member of the Farm Administrators SharePoint group to perform the following task

 


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.

Authentication between SharePoint 2013 and Exchange Server 2013

Authentication between SharePoint 2013 and Exchange Server 2013

Server-to-server authentication enables you to share resources that live on various servers in a SharePoint farm and access services, such as Exchange Server 2013 and Lync Server 2013, which are distributed among servers. Server-to-server authentication in SharePoint 2013 also supports resource sharing and access with additional services that are compliant with the server-to-server authentication protocol.

The configuration details in this article are about how to configure server-to-server authentication between SharePoint 2013 and Exchange Server 2013

Check the more details on the below link from MS.

 

 https://technet.microsoft.com/en-us/library/jj655399.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.

SharePoint Server 2016 update

 SharePoint Server 2016 update

Please find the link below from MS to know more about SharePoint 2016.

http://blogs.office.com/2015/04/16/sharepoint-server-2016-update/ 

http://blogs.technet.com/b/wbaer/archive/2015/05/12/what-s-new-in-sharepoint-server-2016-installation-and-deployment.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.

Event 6398 in SharePoint

Event 6398 in SharePoint

Event ID:   6398

Summary:   Several features of Microsoft SharePoint Foundation 2010 rely on scheduled background processes called timer jobs. Administrators can configure, schedule, and view the status of timer jobs by using the SharePoint Central Administration Web site.

I found a very good article from MS. Please find below

  https://technet.microsoft.com/en-us/library/ee513069%28v=office.14%29.aspx?f=255&MSPPError=-2147217396


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.

SQL account used for SharePoint

SQL account used for SharePoint

When we plan to build the SharePoint, The first and most important part is the account used for the SQL admin. Please find the details below that provide you more information on the account.

1. SQL Admin Account
SQL Admin account would be use to install SQL Server for your SharePoint and would be created in AD. This account should be a domain user and must be a local administrator on database server. These rights are enough to successfully install SQL Server. Do not use any other domain admin account or never make this as a domain admin account. I have seen people using domain admin account to install SQL and SharePoint which is a mistake and a threat to security. You can name this account as "sql_install" or "sql_admin".

2. SQL Service Account
This is the account that runs the SQL Server instance. This should be a domain user but do not make this as a local administrator for security reasons. You can name this as "sql_user" or "sql_services". While installing SQL Server with SQL Admin account, necessary permission would be granted to this account for running the SQL Server instance. At Server Configurations step during SQL Server installation, mention your SQL Service account as the account for SQL Server Database Engine and SQL Server Browser and automatically necessary rights would be granted to this account to run the SQL Server instance.

3. SharePoint Setup Account
Create an account "sp_install" (a recommendation, you can name it anything) in your AD and put this account in local administrator group on all SharePoint Servers. Make sure you do not put this account in domain administrator account. You should never use a domain admin account to install SharePoint and its services.

 


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.