19
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 ...
14
Microsoft released Hotfix for the issue. Please check the below link
https://blogs.technet.microsoft.com/stefan_gossner/2016/09/14/sharepoint-2013-installer-now-supports-net-framework-4-6-and-above/
KB 3087184 link for download https://support.microsoft.com/en-us/kb/3087184
Hope it helps someone
12
I think you are trying to install Stand alone deployment and using the config wizard to create the configuration database using the local account. In this case you have to create the powershell command to create config DB 1st then run the config wizard.
Run this command.
New-SPConfigurationDatabase
Hit Enter and it will ask couple of question i.e Database ...
11
This forum article helped me but I have to substitute for the missing "C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server" - C:\Program Files\Windows SharePoint Services\15.0\Data\Analytics_{some guid}
Hi All,
Recently an issue was reported to me where some of my site admins were
facing an issue in setting up a SharePoint 2013 stand ...
8
Worked for me: server 2k12, SQL 2k12, SharePoint 2k13. This was done on Hyper-V
I did it as a single server installation, joining the server to my existing domain,
used the full installation option (default) as opposed to the stand alone server. Beyond that, I accepted the defaults as it's the first time I've played with this edition.
As for Perms, I ...
8
Sharepoint designer consider as a part of the office family so that its version should match with other installed office products.
In your case you have 64 bit of Windows and 32 bit of office so you need 32 bit of designer.
Now either reinstall the office with 64 bit or install the sharepoint designer with 32 bit
https://ofaolain.com/blog/2015/02/05/get-...
7
SharePoint 2013 can only be installed on 64-bit editions of Windows Server 2008 R2 SP1 or Windows Server 2012.
You can have the interface for a SharePoint App running on any kind of Web server (including Linux) but this is always external to SharePoint.
7
Microsoft has made sure that Sharepoint won't work in WINE.
WINE developers cannot make the BITS service and other services that Sharepoint and other programs need.
I tried the Sharepoint 2013 beta under the current WINE, it complains that it is not Windows 2008 R2 even if you set it for Windows 2008 emulation. Microsoft has a way to get past the WINE ...
7
Not sure if I understand your question entirely, but if you install a language pack, Central Administration should be available in that language too.
For example, If your customer installed the Swedish based version of SharePoint then install the English language pack and you'll be able to run Central Administration in English if you want too. You don't ...
7
I worked with Microsoft Engineers to find the root cause of the error. We discovered a missing registry key at HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer
I wrote a fix script and posted it on our Blog: http://www.devfacto.com/resolved/
For me the value of the string was warmupx (with the x on the end) and the debug value was 7 that worked, at long ...
7
Run this PowerShell script
get-spfarm | select BuildVersion
7
I had this issue in past when configured the workflow manager. In my situation, I ends up doing the following.
I removed the workflow manager service application using this command...Get-SPWorkflowServiceApplicationProxy | Remove-SPServiceApplicationProxy
Now i I run the same register command with -force parameter like this.Register-SPWorkflowService -...
6
Note: This is the database restore process we follow, if you want to recreate the farm just do your SharePoint install and configure as you need then overwrite the databases created with the production versions. It's how we populate new installs when we create local SP vm's for development and test use.
We do this on a monthly basis, and while this is ...
6
I was looking for the same information, and just found the answer here.
Here are the steps:
Launch regedit.exe
For MOSS 2007, navigate to:
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS
For Sharepoint 2010, navigate to:
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS
Check the ServerRole key
Here are the valid ...
6
Features missing in Foundation:
Business Intelligence
Audience Targeting
Improved Governance
Secure Store Service
Web Analytics
Enterprise Wikis
Tag Clouds & Profiles
for a detailed comparison check this helpful link.
6
As almost always with SharePoint the answer is "It depends".
Why should I have a separate Install account?
The main purpose of a separate Install account is to be sure you have an account which is owner of all the installed files and therefore always have the rights to update these. So at least you shouldn't use a personal account for the installation as ...
6
The solution that worked for me:
Open Windows Update
View update history
Find the KB number in "Microsoft .NET Framework 4.6.1 for Windows Server 2012 R2 for x64 (KB3102467)"
Open "Program and Features"
Search for the KB (KB3102467) and uninstall it
Now continue the installation of SharePoint
6
It is not supported to install SharePoint 2013 RTM on Windows Server 2012 R2.
It was supported first with the release of the SharePoint 2013 SP1 slipstream release.
Please see this KB article https://support.microsoft.com/en-us/kb/2891274
5
Separate web applications would get you totally separated sites on the same server.
I don't believe there would be a method to share content easily between the web applications. I don't know enough about content migration/deployment to know if that would be viable. An klunky alternative would be to have another separate "shared" web application where any ...
5
Typically my team doesn't just install the "latest" CU, but the latest one we are comfortable is stable. Currently we are going to August CU. We install all system patches, SP1 and the CU update before configuring the farm.
5
SharePoint is always installed on the boot drive - typically C:
There should be lot of things that you should be considering if you really want to have SharePoint in a different drive
Disk space - The minimum requirement for SharePoint 2010 to be installed in a hard drive is 80 GB, not to think that SharePoint is that big, but SharePoint must have ...
5
You may want to list out the requirements of your applications and then look into the numerous features of the SharePoint 2010 editions here - Foundation/Standard/Enterprise.
The Foundation edition is not "free" - it is added onto a Windows Server or Win7/Vista (all OS are paid for). SharePoint deployment on Win7/Vista is for development purposes only (not ...
5
The best description I've seen is Todd Klindts How to create a SharePoint 2010 farm with no GUIDs using PowerShell
If you've already created your farm you can follow his other post Getting the GUID out of the AdminContent database in SharePoint 2010
5
Solution #1 (preferred)
Right click the SharePoint 2013 Central Administration > Run as administrator
Solution #2 ( I do not think this solution works!!!!)
(Thanks to this blog post)
Copy the Central Administration URL. Ex: h ttp://tfs01:47345/
Go to Internet Options
Select Security tab
Select Local intranet
Select Sites
Paste the URL in step 1 (if ...
5
I also ran into this trouble spot one day when I was installing SharePoint 2013 for a client.
Setup is unable to proceed due to the following error(s): This product requires Microsoft .Net Framework 4.5
So you need to check which version of .NET framework is installed on the server :
• Set-Location 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\...
5
PS C:\> (Get-SPFarm).Products
GUID Product
35466B1A-B17B-4DFB-A703-F74E2A1F5F5E Project Server 2013
BC7BAF08-4D97-462C-8411-341052402E71 Project Server 2013 Preview
C5D855EE-F32B-4A1C-97A8-F0A28CE02F9C SharePoint Server 2013
CBF97833-C73A-4BAF-9ED3-D47B3CFF51BE SharePoint Server 2013 Preview
B7D84C2B-0754-49E4-B7BE-...
5
SharePoint Server 2013 SP1 supports Windows Server 2012 R2. I see no reason why you shouldn't run your SharePoint Server on a 2012 R2 Server. Just make sure you install SP1 correct before adding logic, solutions and content to your farm.
Currently, Microsoft SharePoint Server 2013 is not supported for installation on computers running the Windows Server ...
5
Short answer, no. You don't need it. It's just a super, no bars account that all the rest of the accounts' permissions are designated from. As part of the "best practice" its one of those accounts that Microsoft suggests to set everything up with the least-privileged account security model.
AutoSPInstaller is a great tool I still rely on today, but running ...
5
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
5
As a recommended approach, you should not install the SharePoint Designer on the SharePoint server, reason is same as you mentioned.
SharePoint Designer is client application and you can connect to both farm from you local machine( as long as that machine on network) as long as you have to permission on the site collection.
Only top voted, non community-wiki answers of a minimum length are eligible
