I tried to upgrade SharePoint Foundation 2010 Fresh web application to SharePoint 2013.
I found out that upgrade will stuck at some point.
I can only see one error in error log.
But i already installed report server in SharePoint 2013 environment.
More info:
SharePoint 2010 Build version
SharePoint 2013 Build version
Even though I installed Report server after run the 'Test-SPContentDatabase' command throws following error.
You should first check if this is an issue in your 2010 environment. In central admin if you go to Review Problems and Solutions you can check to see if there are any "Missing server side dependencies". I tend to try and remove this in a non-production environment first, before moving it to 2013 just to be sure it doesn't cause any issues in prod. MissingFeatures are always a nuisance. This feature admin tool has worked for me in the past.
also look at this releases.
Related
I have a client who has TFS 2010 and I need to setup my own installation on an Azure VM in order to do some testing, and help them migrate off of TFS 2010 to TFS 2015. However, I cant for the life of me seem to locate a setup .exe online for Team Foundation Server 2010. Is this still possible? Do I need a physical DVD?
The instructions here
https://www.microsoft.com/en-us/download/confirmation.aspx?id=24337
ask to use the physical DVD, but I dont have one.
According to this link https://social.msdn.microsoft.com/Forums/vstudio/en-US/56343ed9-6c0c-4c17-89d1-62b4bb3cf645/visual-studio-team-foundation-server-2010-setup-downloadable-link?forum=tfsbuild
Its available for MSDN subscribers, but I dont see any TFS versions below 2015 on MSDN download page.
I have found the service pack 1 install, but not the setup for the full product. can anyone help me locate a setup exe online so that I can get this running? Thank you in advance.
Seems you are installing TFS 2010 to simulate some existing environment and test configuration changes. However, there is not any setup.exe for TFS 2010 in official site for now.
It's unsupported and 8 years old. There have been five major releases since then. We encourage users move to newly version of TFS server. Either back up the TFS2010 database and do the move directly or use some other machine with DVD to install the TFS2010 ISO image for a test.
I'm trying to migrate our existing TFS 2008/SharePoint installation to TFS 2012/SharePoint 2010. If I do it without SharePoint it all works OK, but if I try and include SharePoint it fails.
At the moment I'm starting from scratch and including SharePoint.
I've run the Configure Extensions for SharePoint Products Wizard, restored the TFS 2008 databases, run STSADM from the command line, and now I'm attempting to run the TFS 2012 Upgrade Wizard: it fails at the, Configure the Server Running SharePoint step with the error "TF250004: The SharePoint Products installation is either corrupt or is not valid. Verify that SharePoint Products is a supported version and is functioning properly, and then try again."
Can someone please advise me what I've done wrong?
It seems that your TFS server can't detect you SharePoint .
Where is your Sharepoint server, is it running on the same computer with TFS server or on another machine?
With your upgrade ,did you change your hardware or use the same hardware as before.
Accroding to your description, you didn't mention whether you need to upgrade your SharePoint. You should finish SharePoint upgrade before your TFS server upgrade.And match TFS upgrade requirements https://msdn.microsoft.com/en-us/library/vstudio/dd631912(v=vs.120).aspx
You should also pay attention to your sharepoint permission.I suggest you use a "Full Permission" Account in sharepoint which interact with TFS .For your reference:http://social.msdn.microsoft.com/Forums/sr/tfsadmin/thread/ea2ef379-dd14-4e23-86e6-fbc156e430d8
I eventually unchecked the "Configure SharePoint Products for Use with Team Foundation Server" option to exclude SharePoint during the upgrade and then manually configured SharePoint after the upgrade, overcoming a host of problems along the way.
I am following the Microsoft tutorial for creating my first sharepoint 2013 app.
(http://msdn.microsoft.com/en-us/library/fp142379.aspx )
I have installed on a windows 2008 R2 Server Sharepoint 2013 RTM, done all the farm config stuff RTM, and installed all of Visual Studio 2012 ultimate and update 1 and restarted the server.
I have also followed the instructions for "How to: Set up an on-premises development environment for apps for SharePoint" which is at http://msdn.microsoft.com/en-us/library/fp179923.aspx (I have to do this as our dev environment has no internet access)
I have got to the point where running Visual Studio as an Administrator I have named it and chosen "sharepoint-hosted" and validated the server and clicked finish (Step 5).
Instead of getting the next step where I open the AppManifest.xml file I get a message saying "An error occurred whilst trying to load some required components, Please ensure the following prerequisite components are installed. Microsoft Web Developer Tools and Microsoft Exchange Web Services"
I have checked VS setup and web developer tools is definetely installed (the only option I have would be to remove it)
Any help would be greatly appreciated. I know Im a noob here (this is my first post) but I have googled this and searched stack exchange and found nothing that helps me.
Got it after a few trial and errors
With an offline install you have to download the Exchange Web Services component. I had downloaded "EwsManageApi" and installed that.
As the error message specifically refers to Exchange Web services, I looked at other versions and tried the older 1.1 and the 32 bit version, but they didn't work either, ** until ** I relised in my haste that I installed using the default settings (which is for the current user) and not for all users of the machine.
So installing EwsManagedApi32 for all users on a 64 bit server does the trick (for me)
I tried reinstalling the EWS Managed API for All Users, but that didn't solve it for me. In the end the solution was simple:
Just uninstall BOTH the EWS Managed API and the Microsoft Office Developer Tools for Visual Studio 2012. After that reinstall ONLY the Office Developer Tools. This time the Web Platform Installer will ensure the correct EWS Managed API is also installed.
I also wrote a small blog about this problem:
https://leonzandman.com/2013/02/07/prerequisite-components-error-when-creating-a-visual-studio-2012-sharepoint-2013-app-project/
Answer for the year of 2014:
Install Microsoft Exchange Web Services Managed API 2.1 (the latest version I can find at this time).
I've just tried out TFS 2010 today, along with Project 2010 and VS 2010. Only Later realized that without Sharepoint, TFS is only configured as Basic. This reduces it's functionality as oppose to what I've seen during VS2010 product launch. Sadly I can't find any alternative but to get a trial copy of Sharepoint to see if it serve my purpose. Well, apparently Sharepoint only comes with x64 edition. I'm not formatting any machine to x64 just to give this a try. So, after some reading up, I found that Project Server is actually based on Sharepoint. Now I wonder is whether TFS can be configure to connect to Project Server?
If it's possible, would the setting be much different that Sharepoint's?
And what am I missing from this setup as oppose to Sharepoint's?
Based on Sharepoint != Sharepoint. I think that Project Server is just a subset of Sharepoint functionality. Also, basing Project on Sharepoint allows for some really tight integration into your portal. To answer your question, I don't think you still will get your fully featured TFS without Sharepoint Proper.
FYI - Sharepoint 2007 (or 3.0 or whatever it is) is not x64 only, but will run on x86. TFS 2010 will go full feature on 2007
Sharepoint 2007 Trial
To answer what you are missing:
Reports
Project Portal
TFS Web Access
That's about it. You still get 90% of the features with your current deployment without SharePoint. Tommy is right about MOSS 2007, it comes in 32-bit and will give you all features. Project Server runs on top of SharePoint as a shared service provider. Traditionally MS releases a power toy to integrate TFS with Project Server. They said they would go over this at TechEd, which just happened about a week ago.
Also, I suspect the integration with Project Server 2010 will be better, but then you will have to run SharePoint 2010 :(
In my opinion, TFS has enough to run most projects by itself and you can use the client version of MS Project for critical path anaylsis, etc.
Use Windows Sharepoint Services for Windows 2003 & Windows 2008:
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb400747.aspx
For Windows Server 2008 sp2 and Windows Server R2, use SharePoint Foundation 2010:
http://www.microsoft.com/downloads/details.aspx?FamilyID=49c79a8a-4612-4e7d-a0b4-3bb429b46595&displaylang=en
Both are free.
I'm not formatting any machine to x64
just to give this a try.
Why not use VMWare Server, Hyper-V, Virtual Box or some other virtualization software to run the pre-made demo/trial/lab VHD's - no formatting, no installation, no setup, more hair.
Link
I installed WSS 3.0 and pointed my TFS2005SP1 installation at it. I am planning my TFS 2008 upgrade. Everything I've read mentions migrating to WSS3.0 after the TFS upgrade.
Are there any gotchas I need to be aware of related to the WSS upgrade already having been performed?
I am in this same situation. I have TFS2008 sitting here ready to go. What I am ultimately thinking is that since Microsoft did put out official documentation on how to upgrade TFS2005 to use WSS3.0 (which I followed and worked perfectly), that the upgrade from TFS2005 to TFS2008 should go on without a hitch with WSS3.0 already in place.
I am still a bit nervous about it and your question is the first mention I have even been able to find online about this.
I had issues with the upgrade. It would always silently exit after entering the Reporting Services account information. The next page of the setup wizard is supposed to be SharePoint connection settings. When I upgraded, I did not replace the WSS 2.0 site but installed side-by-side and changed the SharePoint port settings in TFS config. I think this was the cause of the install failure.
I ended up building up a new virtual machine with the exact same specs, computer name, etc. I did not install TFS 2005, but restored the TFS 2005 databases and then ran the TFS 2008 installer. It detected and upgraded the 2005 databases and all is well.