New answers tagged installation
Realize this is old but in the future if you get a correlation ID you can simply open the management shell (SharePoint) and type the following: merge-splogfile -correlation "your correlationID" -Path "C:\someDirectory\SomeFile.log This will scan the entire farm regardless of server count and write any entries to SomeFile.log where you can open it with ...
If you have .NET 4.6 installed, uninstall it and re-install .NET 4.5. Then try the WAC install again. You can upgrade to .NET 4.6 afterwards.
Not all patches update the farm build number. These are typically security hotfixes or non-security hotfixes that do not patch microsoft.sharepoint.dll. It is expected behavior. Applying CUs is the best bet to update the farm build number and of course, all products. That said, even security patches require testing and you may not want to deploy all of ...
As mentioned by @jubblerbug, this can occur if you already have .NET Framework 4.6 installed before SharePoint 2013 (e.g. if you installed Visual Studio 2015 first). I couldn't use Microsoft's workaround as the option to remove .NET Framework 4.5 was disabled, and the ability to uninstall the .NET 4.6 update wasn't there either. So I used Process Monitor to ...
Update... after installation of SharePoint Server 2016 RC update, it worked perfectly. Download Link
The solution to this problem: In Windows Server2012 R2 ServerManagerCMD.exe does not exist, but the setup needs it. I made a copy of C:\Windows\system32\ServerManagerCmd.exe and renamed it to ServerManagerCMD.exe. After this 'fix' all prerequisites are successfully installed.
You also need .NET Framework 3.5 installed. Check under features that its available. If not, follow the guide How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2
You must configure your Exchange server (or any email server you use to send emails in your organization) to route emails @OurSharePointServerName-OurDomainName to the IP address of the SharePoint server where the SMTP service is enabled. See "Step2: Create Send and Receive Connectors in Exchange 2010" at ...
Only certain lists support incoming email, like discussion boards and calendar. Custom list is not one of them. https://support.office.com/en-us/article/Enable-and-configure-e-mail-support-for-a-list-or-library-DCAF44A0-1D9B-451A-84C7-6C52E7DB908E
What i am thinking, it is permission issue. You service account don't have enough rights to provision this. Make sure Services account should have following rights. log on as batch rights Log on as a service A very good reference about the service account.SharePoint 2013: Group Policy Considerations for a SharePoint Farm
Top 50 recent answers are included