What is the difference between a TFS installation with Sharepoint Services and one with Sharepoint Server? What are the limitations of the former?
Thanks
This refers to licensing. If you have a SharePoint server license you would like to use for your TFS web portal, or would you like to install a new instance of SharePoint Services(which is free).
Related
actually i tried to migrate lists and document libraries from one site to another site in sharepoint 2013 and migrate sites also from 2010 to sharepoint 2013. But,I want to migrate web application from sharepoint 2013 to sharepoint online.
We are limited to creating Site collections only in SharePoint online. You cannot create/migrate the complete web application to SharePoint online in one go. You would have to migrate either a complete site collection or site level.
I have experience migrating with SharePoint migration tool from Microsoft (which is free software) and it worked well.
However, i would suggest to migrate individual site level as it would be easy to manage. I have tried migrating a site collection which failed after 40% and it was difficult to debug where the error was. I later figured it was the nintex form on a document library that was a culprit.
Good luck with your project!
You may use below methods to create apps
Using SharePoint Apps ( https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins )
Use the latest SPFx framework (https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview) to create apps.
I have to develop a document repository on SharePoint from Azure. As I have new to Azure, I do not know about the requirements to set up the entire SharePoint and make it run like the SharePoint online, 2013, etc.
As much as I have read, it says we need a VM, a SQL server and Sharepoint. I am unsure if this all what we need and what is the role of the VM and SQL server in this.
Can anyone please share the suggestions or the experiences for this?
If you are going to host document repository, you need to check
Office 365's OneDrive or SharePoint components. This is the PAAS
model.
If you want to have a dedicated portal using full SharePoint features, you need to setup a virtual machine, on which you setup the entire installation of SharePoint just like you do on a actual server. This will be the IAAS model, where Azure just offers you hosting service for the VM. SQL server is required for hosting the backend database for SharePoint (documents, users, roles etc)
Problem summary:
I have just built a new TFS 2013 environment for my organization. On my first attempt\test creating a new team project using Visual Studio 2013, I receive the following error at the final stage (Finish button):
"TF218017: A SharePoint site could not be created for use as the team project portal. The following error ocured: Server was unable to process request. ---> The user does not exist or is not unique.---> The user does not exist or is not unique."
I have found several other posts with folks encountering this same error but the proposed solution seems to always be to change the authentication mode in SharePoint to classic which is not available in SharePoint 2013.
The error message implies that this is permissions related. However, it is a little baffling due the fact that when I created a new TFS Project collection using the TFS Admin console it created a new site collection in SharePoint with no issues. I don't understand how my permissions would allow me to create a site collection but not place sites under the site collection.
Here are some details about my setup:
TFS 2013 running on Windows Server 2008 R2 Enterprise
SharePoint 2013 Foundation (separate server within same domain as TFS
server)
TFS Service account is a Site collection admin on the SharePoint site
collection
My AD account is a Site Collection admin on the SharePoint site
Collection
TFS Service account is a Farm Admin in SharePoint
My AD account is a Farm Admin in SharePoint
The TFS2013 Server is also a Farm Admin in SharePoint
No problems were encountered during installation of TFS 2013
TFS Server is used solely for TFS - nothing else is hosted here.
TFS Extensions For SharePoint have been installed on all servers in
the SharePoint 2013 Farm
TFS Server fully updated as of 1/17/2014
workstation fully updated as of 1/17/2014
Details on what I have attempted/researched so far:
Confirmed with my networking staff that there are no firewall\blocked ports
issues between TFS Server and SharePoint Servers
For the time period in which I was trying to create the new team
project there are no errors\warnings in the event viewer on my local
machine, SharePoint servers, or the TFS Server
When running Fiddler on the TFS server while trying to create the new
Team Project - I am seeing no traffic at all between the TFS server
and the SharePoint server.
my workstation has no open connections to any of the servers in question when trying to create the Team project
Cleared cache on my workstation at: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\4.0\Cache and C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\5.0\Cache
Verified nothing in cache on TFS Server at: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v12.0
Performed IIS reset on TFS Server
Re-start on TFS Server
Team Foundation Server Best Practices Analyzer (it says "SharePoint products is not installed", I'm suspecting this is because SharePoint is installed on another server)
Installed Visual Studio 2013 Update 1.
I apologize if this is in bad form but I have also posted this on the msdn forum: http://social.msdn.microsoft.com/Forums/vstudio/en-US/0758f52d-bf03-44e4-96aa-b60468395914/tf218017-cannot-create-sharepoint-2013-site-from-tfs-2013?forum=tfsgeneral
I am reaching the bounds of my skill set on this one. Any help\ideas would be greatly appreciated. Thanks!
Update:
Well, unfortunately I had to break down and call tech support from an un-named large tech company for assistance on this. Some changes were made to our SharePoint environment in the process which coincided with the SharePoint farm "going down". I am not sure if the problem on the farm was a coincidence or related to my changes but the end result is that my SharePoint people are now skeptical of my TFS integration etc... so I was forced to do a default install of SharePoint on the TFS box. I will leave this post up for others with similar issues to discuss unless that is in bad form. Thanks to all who tried to help with this.
Here are some additional items I would check:
Make sure you start VS 2013 elevated (Right-click when opening and choose 'Run As Administrator') when creating a team project.
If possible, see what happens if you try from a different computer or the server itself using Team Explorer.
Ensure that the user that you are attempting to create the team project with has enough permissions in SharePoint (you can make the account a site collection admin on the site collection in question).
The user should be a TFS Server Administrator or Team Project Collection Administrator.
Make sure that user account has Content Manager rights in the related Reporting Services folder as well, just in case.
Go to the your SharePoint site collection and attempt to create a site in it manually as the account that you are trying to create the Team Project with; when you perform this, make sure you create it with one of the team site templates that TFS installed (like the Agile or CMMI); If you encounter errors this way it may help you narrow down the problem.
Don't forget to review the event logs on the machines involved.
Okay, I finally go to take another crack at this against my SharePoint enterprise environment and got it to work: The key was to simply remove Anonymous Authentication from the SharePoint web application and it worked!
Access the SharePoint web site collection (for example server/site/DefaultCollection) and add your user or group on Site Collection Administrator.
I have a farm solution wsp which I want to add and deploy on a client's SharePoint farm.
Now I don't have remote access to this SharePoint machine but do have full admin rights to its central admin and related site collection, and can open the central admin and all sites through my machine.
Now as per my knowledge a farm solution is added to the SharePoint farm and not to the site collection, but I could not find any screen in central admin from which I can add my solution.
This is the case with both SharePoint 2010 and SharePoint 2013 servers.
What are the possibilities?
Basically, it sounds like you need to add and deploy a farm solution only using central admin? I don't think that is possible. If you look step one from MSDN
Adding: A solution package is added by a farm administrator to the farm's solution store, which is in the farm's configuration database. This is done either with the SharePoint Management Shell (or with the object model). It cannot be done in Central Administration.
You can't do this through web interface.
If you have full admin rights - you can use Remote PowerShell. But this require some setup on server. You can read this article about this: http://blog.incworx.com/blog/nik-brendlers-blog/administer-your-sharepoint-farm-remotely-with-powershell
If I use MOSS 2007 or Sharepoint Services 3.0 with TFS do I need a license or is there an implicit license with TFS, like there is for SQL Server.
You need a license for MOSS, but Sharepoint Services 3.0 are part of Windows and don't require a separate license to use. TFS only requires WSS to run. The stack looks like this:
WSS
/ \
MOSS TFS
WSS 3.0 comes free with Windows Server 2005/2008, MOSS always requires a separate license. TFS doesn't grant you any kind of SharePoint licensing afaik.
Ray - as others have said you need a license for MOSS beyond your Windows Server and TFS licenses, but not WSS 3.0 for TFS 2008. TFS 2010 does not require WSS or MOSS at all if you have another site or portal solution (i.e. FlexWiki, Zen, Pivotal Tracker, etc).