Showing posts with label SharePoint 2013. Show all posts
Showing posts with label SharePoint 2013. Show all posts

Friday, September 4, 2015

SharePoint 2010 Management Shell does not load with Windows Power Shell 3.0



SharePoint 2010 Management Shell does not load with Windows Power Shell 3.0

Issue: After you install Microsoft SharePoint Server 2010 and Windows Power Shell 3.0 on a server, you receive one or both of the following error messages when you start SharePoint 2010 Management Shell:

Error message 1:The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

Error message 2:Microsoft SharePoint is not supported with version 4.0.30319.17929 of the Microsoft .Net Runtime.

Workaround: please follow the work around mentioned below.
To work around this issue, change the Target field value for SharePoint 2010 Management Shell. To do this, follow these steps:
1.   Click Start, and then right-click SharePoint 2010 Management Shell.
2.   Click Properties.
3.   Click the Shortcut tab in the SharePoint 2010 Management Shell Properties window.
4.   Input the following value in the Target field:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Version 2.0 -NoExit " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "

 


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, September 3, 2015

Task synchronization between SharePoint and Exchange



Task synchronization between SharePoint and Exchange

I am getting the queries about the synchronization between SharePoint and exchange from users, hence writing this article to explain the same.

Details: have configure task synchronization between SharePoint Server 2013 and Exchange. Some users see the tasks in OWA (or Outlook) synced from SharePoint but after they change this tasks in OWA - changes do not appear in SharePoint. If you then change the task again in SharePoint task data in OWA will be replaced.

Why the synchronization is not happened in vice versa?

Answer: It is by design that the tasks created in Outlook will not be synced to SharePoint task list and the tasks will be synced to Personal Tasks in users’ My Site. This is how the new feature “Sync to Outlook” works in SharePoint 2013.

If you want to display the task in the task list, then you can edit the task to make it public and choose the task list where to store it.

I hope the above clarifies the answer, If you still have any concerns, please make a comment.
 


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, September 2, 2015

SharePoint 2013 licensing

SharePoint 2013 licensing

SharePoint supports intranet, extranet, and Internet applications from a single, integrated platform. The specific licenses you need depend on three factors: what capabilities are used, how SharePoint is deployed, and where the system is hosted. The terms and conditions for how you can use the software are defined in the Product Use Rights (PUR) document and the Product List document.
  • SharePoint Online is licensed on a per-user basis. You can purchase SharePoint Online as a standalone plan or included as part of Office 365 plans. Learn more. Licensing details are available here.
  • For On-Premises, intranet sites are licensed using a Server/CAL (Client Access License) model. SharePoint Server 2013 is required for each running instance of the software, and CALs are required for each person or device accessing a SharePoint Server.
SharePoint Standard CAL: the Standard CAL delivers the core capabilities of SharePoint

·         Sites: a single infrastructure for all your business websites
·         Communities: an integrated collaboration platform
·         Content: enterprise content management (ECM) for the masses
·         Search: people and expertise search, visual previews, visual best bets

SharePoint Enterprise CAL: the Enterprise CAL delivers the full capabilities of SharePoint

·         Sites: a single infrastructure for all your business websites
·         Communities: an integrated collaboration platform
·         Content: ECM for the masses
·         Search: standard search features plus entity extraction, video search, item recommendations
·         Business solutions (includes Access Services and InfoPath Services)
·         Business Intelligence for everyone (includes Power View, Performance Point Services, Excel Services, and Visio Services



 Find the atricle from MS:

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, August 6, 2015

Support for SQL 2014 with SharePoint 2013



Support for SQL 2014 with SharePoint 2013

This is a common question arises in every administrators mind. is the SQL 2014 supported by SharePoint 2013?on what extent? Please find the answer as below.

Yes, SharePoint Server 2013 will support SQL Server 2014 with the April Cumulative Update. Find the reference links from MS.
 

 http://www.microsoft.com/en-us/server-cloud/products/sql-server/

http://msdn.microsoft.com/en-us/library/bb500435(v=sql.120).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.

Tuesday, August 4, 2015

Difference between create a new farm and join an existing farm



Difference between create a new farm and join an existing farm

I am writing this topic because, many of the administrators who entered into the SharePoint recently will get this query, what makes difference between them? We see this option after the installation of SharePoint and while running the Products and Technologies wizard.

create a new farm: This option is used to create a new SharePoint installation .(This can be a standalone installation having all the roles (Web front end(WFE), Application server and database server on the same machine). This is where the new configuration DB will be created in SQL

join an existing farm: This option is used to add a new role to an existing SharePoint installation(In farm scenario, we can add an application server or WFE by joining the machine to an existing farm). This is where the server will be connected to already created configuration DB.


 


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, July 2, 2015

Keep on saying that “A system restart from a previous installation or update is pending” at the pre-requisites installation for SharePoint 2013



Keep on saying that “A system restart from a previous installation or update is pending” at the pre-requisites installation for SharePoint 2013.

                                   


Issue: Keep on saying that “A system restart from a previous installation or update is pending” after the pre-requisites installation for SharePoint 2013. After I run a prerequisiteinstaller.exe successfully and download all pre requests During a SharePoint 2013 install. I got the error "A system restart from a previous installation or update is pending".  even if I already rebooted.

Solution: Please follow the steps below to resolve the issue.

1.    Open the Registry editor (run > regedit)
2.    Navigate to this path “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager“
3.    Rename the “PendingFileRenameOperations” value to “OldPendingFileRenameOperations“
4.    Reboot the server

Solution 2: If you see the issue still, Then Delete the key as below and check again.

1.    Open the Registry editor (run > regedit)
2.    Navigate to this path “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager“
3.    Rename the “PendingFileRenameOperations” value to “OldPendingFileRenameOperations“
4.    Reboot the server
  


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.

ShareThis

X