Tag Info

New answers tagged

0

As per my little experience with SharePoint and A lot of Discussion with MSFT folks. I come to this Point First, you have to make sure you need CU to Fix a problem in your Farm Dont apply those CU /Fixes from Windows Update.Always Turn off Automatic Update on Server Dowload the CU from MSFT site and apply. You need to plan it, test it, schedule a down ...


1

You need to remove SharePoint Foundation 2013 and than install SharePoint Server 2013.. You cannot install SharePoint Server on the top of SharePoint Foundation.. I have faced this problem.. :) Reference: SharePoint 2013: Migrate from SharePoint Foundation 2013 to SharePoint Server 2013


1

I tried a lot of solutions that I read about online but the only thing that solved my problem was this one. Go to the file C:\windows\System32\ServerManager.exe, copy it and rename the copy to ServerManagerCMD.exe. Run the Preparation tool again and the problem is gone. That simple!


0

The SP 2013 exe installer needs a file named servermanagercmd.exe, which is not present in the windows server 2012 R2 OS. So we need to rename the file servermanager.exe, to servermanagercmd.exe which is located in windows\system32 directory. This is what has solved my problem.


1

​15.0.4641.1001 is for ​August 2014 CU while ​15.0.4667.1000 is for ​November 2014 CU. Check from Here So what i think, you installed the Aug 2014 CU on the Live servers while on staging Server You install the Correct the CU. to fix this, simply download the Nov 2014 CU for SharePoint Server and Install on all servers in farm than Run the Config wizard. ...


1

Looks Like you installed the SharePoint 2013 Standard versions, All the services apps you trying to create are part of Enterprise License. Check this link for standard vs Enterprise Comparison Now you should update your farm with Enterprise license key, You can change it from central admin > Upgrade and Migration > Convert License Type> enter the ...



Top 50 recent answers are included