Hot answers tagged

13

This guide on MSDN tells you pretty much everything you need to know on installing SharePoint 2010 on Windows Vista and 7. As an aside, if you're going to be doing SharePoint Development, you'll really be wanting to do it in a virtual machine running Windows Server 2008. You might need a bit more muscle in your host system (at least 6GB), but SharePoint can ...


9

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

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 ...


8

Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008 More on Google.


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 ...


7

Sounds like you have done a stand alone installation when you installed the bits. This changes everything. You should always do a Server Farm install, even if you are putting everything on a single machine. The only way to repair this is to uninstall SharePoint and install it using the Server Farm installation.


7

Run this PowerShell script get-spfarm | select BuildVersion


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 ...


6

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 ...


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


6

the article you reference at the end of your question really answers it: custom web services should be placed in _vti_bin. i usually start by adding them to _LAYOUTS but thats only to be able to define my discovery files etc (as described in the MSDN specification you mention). _vti_bin is a virtual directory mapped to the 12/ISAPI folder, so you can ...


6

This is the official guide from Microsoft: http://msdn.microsoft.com/en-us/library/ee554869.aspx I tried these instructions and they did not work. This could be due to user error though. There is also a PowerShell script that claims to do it: http://gallery.technet.microsoft.com/scriptcenter/a88cad83-f595-4487-940e-f678ce47eb5f I have not tested ...


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

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 ...


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

It turns out that the Prerequisites installer was downloading a 0KB Geneva installation package, because the official Microsoft download URL is down (giving 404 errors). I found a working link to the installer: http://download.microsoft.com/download/8/6/6/866E86E1-2264-4C80-836A-92F3F3A3B1AB/release/MicrosoftGenevaFramework.x64.msi. So the steps were: ...


5

Developing for SharePoint for SharePoint with VS2010 requires running it on a machine with SharePoint installed locally. I would not recommend doing the Windows 7 install of SharePoint as you do not get full functionality of the Server edition with a Windows 7 install. Sounds like you have the RAM to run a virtual machine. I would recommend doing a Windows ...


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

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

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

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 ...


5

I would load up Process Monitor http://live.sysinternals.com/Procmon.exe then attempt your re-install again. You should be able to see what files/registry keys it is looking at, and remove or edit the offending entries from there. If it starts to look like you will be spending more than an hour on it, then I would look to just re-install, it will take ...


5

I would ship a .zip file which contains solution1.wsp solution2.wsp solution3.wsp install.bat readme.txt install.bat performs the deployment of the solutions by making calls into STSADM.EXE


5

You cannot install SharePoint on XP. There is a round about way of installing it on Vista (see http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2008/05/21/how-to-install-windows-sharepoint-services-3-0-sp1-on-vista-x64-x86.aspx) but you should try and install it on Windows Server 2003 or 2008. By doing so you will get Windows SharePoint ...


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

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

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.


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 ...


4

Modifying the installer is not a Microsoft supported solution. The ArpWrite entry actually is used to write the fact that SP was installed into the registry as part of the install. I ran into this issue on a new install for a client, the server did not have these two patches applied to the server, I noticed they were pending and applied them. I don't ...



Only top voted, non community-wiki answers of a minimum length are eligible