Hot answers tagged

35

This question has come up before. Take a look in the Related column on the right where you will find 4-6 similar questions: Getting started with SharePoint 2010 for SharePoint 2007 Developers Recommendations for SharePoint 2010 training? What resources would you recommend to someone who would like to learn and possibly become a SharePoint Developer? What ...


19

Free for all: IT Pro: http://technet.microsoft.com/en-us/sharepoint/ee518660 Developer: http://msdn.microsoft.com/en-us/sharepoint/ee513147 For MS Partner: IT Pro: Ignite Training Developer: Ignite Training


13

The Lynda SharePoint Essentials Training is an excellent starter video series for understanding the general components and concepts behind SharePoint. Getting Started Developing on SharePoint 2010 from MSDN is an authoritative guide for fresh developers. For an understanding more towards the business side of things, start with the Total Economic Impact of ...


11

Check out this article on nothingbutsharepoint.com on how to find the versions in SP2010. And Todd Klindt has a nice break down too. Taken from Todd's article, To see which build your farm is, go to Central Administration > System Settings > Manage servers in your farm (/_admin/FarmServers.aspx) Or using Windows PowerShell: ...


10

This is a nightmare situation to be in! Got it escalated in Microsoft who indeed know and have already fixed the source (so terminated backups don't trigger this) in the April CU http://blogs.technet.com/b/stefan_gossner/archive/2013/04/27/april-2013-cu-for-sharepoint-2013-has-been-released.aspx - you have to install March CU first. However, it does not yet ...


9

I got this error when trying to do Restore-SPSite on a SharePoint Farm that did not match the schema version of the backed-up Site Collection. After installing the correct CU to my target environment the Restore-SPSite worked without issues. Found this in the ULS log to pinpoint the issue : Microsoft.SharePoint.SPException: Schema version of backup ...


9

You can purchase a book on the subject or spend some time reading blogs. There are many good ones out there that can help you either better understand the features and components of SharePoint or to tackle specific issues or implementations. Since you are looking at this for an Intranet replacement, I would highly recommend you focus on some Information ...


9

I very recently had the same issue with Nintex Workflow 2010: It wouldn't install properly from my App server because this service was turned off. Other than that, yes it's a good way to turn an application server into a true application server, and prevent it from running and serving the content web applications and IIS sites. Have a look at the ...


8

If you are running this from the server, you will need to make sure you "run as administrator" also, the farm account is the account that is used for the identity for Central Admin. You can grant other accounts privileges to run PowerShell Commands, and you have to do this if you are going to use a non-farm admin account to run PowerShell. You can find that ...


8

Try SharePoint PowerShell: Get-SPDatabase http://njbblog.blogspot.com/2011/03/sharepoint-40-powershell-get-spdatabase.html


8

This is what I follow. The most important thing to note is if you screw up somewhere along the way you have to blow away your service application before trying again. Update Very rarely I have to remove the FIM certificates when things are really broken with the user profile service: Stop the SharePoint Timer Service Stop the User Profile Service if ...


7

The domain that needs to be isolated is only a DNS domain not a new AD domain. This is purely such that you have a separate IIS site where Cross Site Scripting is prevented by the browser. You can add that new domain in DNS (see Configure an environment for apps for SharePoint (SharePoint 2013)) or hosts file. The High trust app still needs the same ...


7

The account will need permissions on the content database. Just executing: Add-SPShellAdmin CONTOSO\User1 Will give you access to the configuration database, but not the content database. Also provide access to the content database by giving access to the content database by using the -database parameter Add-SPShellAdmin -UserName CONTOSO\User1 -database ...


6

Why not simply using Central Admin... :-) (works even if you do NOT have access to either the physical server (console) or databases server. Central Admin -> Upgrade and Migration -> Review Database Status. By pasting /_admin/DatabaseStatus.aspx at your CA url. Rgds, Arjan Vos


6

Check with your IT department. You probably already got an SMTP server that you can use. Then it is just a question of configuring SharePoint for outgoing mail from Central Administration > System Settings > Configure outgoing mail settings The whole setup (including if you do not have an SMTP server) are described pretty well on Technet here. If you ...


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

When trying to administer SharePoint Online (O365) via PowerShell through a proxy server the Connect-SPOService cmdlet connections fail. Perform these commands and retry Connect-SPOService $cred = [System.Net.CredentialCache]::DefaultCredentials [System.Net.WebRequest]::DefaultWebProxy.Credentials = $cred


6

Just look at the code snippet below and try to imagine the scenario of what will happen: using(SPSite site = new SPSite("http://somesite")) { using (SPWeb web = site.OpenWeb(SameGuid)) { return web.Url; } } The above code can raise an exception because two web objects would be returned, there are infinite scenarios where GUID is used to ...


5

Check your web application user policy and see if builtin\administrators have full control.


5

If you want to know databases in your farm instance, use Get-SPDatabase as suggested by another answer. If you want to understand what databases sharepoint creates and what exactly sharepoint stores in them, check Databases That Support SharePoint 2010 Products


5

I was able to accomplish this using the following PowerShell commands: $site = Get-SPWeb https://server.name/site/ $site.Lists["ListName"].RootFolder.MoveTo("ListName") Normally, the MoveTo method would take an argument like "Lists/ListName", but when it's passed just the list name it moves the list to the root of the site. This command can also be used ...


5

The procedure described in these articles should work just fine. I've done this multiple times. You don't need to install the SQL Management or Client Tools on every SharePoint server. Just us the cliconfg.exe program to setup the alias. You can find more information on my blog at: http://thomasvochten.com/archive/2009/03/using-sql-aliases-with-sharepoint/ ...


5

Never disable the Timer and Administration Service. From TechNet: To facilitate this centralized configuration model, Windows SharePoint Services 3.0 relies on two new and enhanced services: the Windows SharePoint Services Administration service and the Windows SharePoint Services Timer service. The Windows SharePoint Services Timer ...


5

If you are a Farm Administrator or have access to a Farm admin account, you can then add yourself as a Site Collection Admin on any Site Collection for any Web application in that Farm. You mention that several sites are not showing up in CA. Are you sure these are Site Collections and not sub sites? If so, could they possible be in a different Web ...


5

The Local parameter can be used, and exists, for two reasons as you and Anders describes. 1) Execute the deployment immediatley withouth the timer service - on single server farms. Most common approach. 2) Deploy the solution on one server at a time to maintain uptime for the farm while updating/deploying. It's not as easy as it sounds. First of all you ...


4

If you want to completely stop a SharePoint farm there is a useful list of services within the Move all databases (SharePoint Foundation 2010) article. Obviously (as you have requested) this will mean that ALL SharePoint activity will cease: "To stop the farm On the server that is running the Central Administration Web site, in the Services snap-in, stop ...


4

Not entirely sure why you add "except CA". Sure you can automate security using PowerShell. But this gives you only real value if you have multiple farm environments that you want to stay as much "the same" as possible. The important thing here is to harden security for your farm, not really how you do it. As a primer you should read Plan security hardening ...


4

Leave it on, as it provides flexibility. You should already be directing traffic to your WFEs with DNS or a load balancer, so other servers won't have traffic hitting them. But leave it on. Down the road you'll need to perform some sort of troubleshooting, and this will come in handy. "Well, then turn it on when you need to!" I hear you say. The problem ...


4

There is a strong possibility that the application pool for central admin timed out before the application was created on the second node. To fix this: Delete the web application that did not provision on all WFE's On the server hosting Central Admin, open IIS manager. In the tree view, expand the server name and click on Application Pools. Locate the ...



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