I am installing SharePoint 2010 single farm on my 64bit Win7 Ultimate development machine. After a lot of pain and apparent success of the installation, I am not finding the "Farm Configuration Wizard" on the "Configuration Wizards" page of Central Administration.
Looking for reasons why and things to check to make it show up.
Thanks
Standalone installations of SharePoint do not support farm configuration wizard.
You get this message when trying the address of the farm config wizard directly:
http://server:prt/_admin/adminconfigintro.aspx?scenarioid=adminconfig&welcomestringid=farmconfigurationwizard_welcome
Related
Perhaps this was asked before but I can't find a whole lot on this, so I would appreciate some help.
Our architecture is as follows: Win 7 desktop on a domain with VS 2010. MS Sql server R2 on Win Server 2008 R2 Ent; SharePoint 2007 on Win 2003; SharePoint 2010 on Win 2008 R2 Ent; Visual Sourcesafe on yet another separate Win Server 2008 R2 Ent server. On this server I have just installed TFS and was running Advanced Config Wizard.
As I'm new to TFS all my selected options are based on intuition and perhaps common sense but Reporting Services and SharePoint aren't working. With reporting services after I add my sql server name (and I've tried IP address and dns name) neither the Report Server URL nor Report Manager URL is populated. (Note: What do I need reporting services for anyway?)
So I've opted not to use reporting services, which as I said, I don't know what is the benefit of it.
Next, in the SharePoint configuration, I wanted to use the existing SharePoint farm which is installed on a separate servers. Testing the Site and Administration URLs would throw an error: "The following site could not be accessed. ... Either ... not installed the Team Foundation Server Extensions, or Firewall... "
I suspect it is not the firewall so then the TFS Extensions. Having search that topic as well seems to point back to the TFS's configuration, so I'm a completely at a loss.
Any ideas?
Thanks,
Risho
/posted from a smartphone since employer blocks this site/
Edited: I was looking at this article http://msdn.microsoft.com/library/dd631915.aspx but I don't have the options listed in the step-by-step solution. TFS Admin Console has this: Top tear - server name, below is Application Tear then Proxy Server, build Configuration and Logs. Expanding Application Tear shows Team Project Collections, SharePoint Web Applications, Reporting, and Lab Management.
You have to configure the SharePoint extensions on each SharePoint machine you wish to connect to TFS. Install TFS on whichever SharePoint machine (or both, if you plan to use both). In the configuration wizard, you should have the option to configure SharePoint Extensions. Once done, you should be able to re-run the readiness checks in the Advanced Wizard on your Application Tier machine.
I have a sharepoint Server that I uninstalled. (I just did it through add-remove programs and uninstall)
Then when I tried to re-install Sharepoint foundations 2010 (the same version I uninstalled) it would seem to work correclty, but it would not give me an option for Stand Alone. Only giving me an option for Existing Web Farm or New Web Farm.
I have tried to delete the instances of SQL Server (Sharepoint) but still getting this problem.
I have Windows 2010 Server (same as Windows 2008 R2)
There is no "Stand Alone" option. I just installed a fresh SharePoint 2010 and only had the options for "Existing Server Farm" or "New Server Farm". As explained in the same dialog: Go for "New Server Farm" when you are installing it on a single server (stand alone).
Is there anyway to develop sharepoint projects without having sharepoint server installed locally. I have a sharepoint server running at my work and vs2010 installed locally. I want to be able to test my projects on the server.
You develop them locally but without SharePoint installed you cant test them. Microsoft Offers no free version of SharePoint Server, so you have to be able to use a licensed copy of SharePoint to test on it. I just use a Remote Desktop Connection to connect to my DEV machine that has SP installed on and Visual Studio. I then develop my app then test, and then it gets deployed to our SharePoint Farm.
Yes, it is possible. You just need to build wsp and then deploy it on a SharePoint server. I hope, this links will help you:
Creating a SharePoint Solution Package (.wsp) in 5 steps
WSPBuilder (SharePoint WSP tool)
Installation and Deployment of a Farm Solution in SharePoint 2010
I will need a Sharepoint Server 2010 install for learning purposes.. I already have a Win 7 x64 os installation with vs2010 and I use it for my current development needs.
The question is ... would you recommend to install sharepoint onto an existing win 7 installation, create a separate OS instance (win7 or win 2008 r2?) for sharepoint development purposes or maybe create a VM for that? I have 4GBs of ram and I wont be able to extend it.
What are your experiences with dev environments for sharepoint 2010? I remember that 2007 was a real resource hog - maybe there is a 'magical' switch that allows sharepoint 2010 related services to be turned off?
If you thought SharePoint 2007 is a resource hog, SharePoint 2010 is even worse. The full installation creates lots of Windows services and IIS application pools. Which makes it really hard to stop SharePoint since all those services start automatically.I agree with others that you should use the VM approach but I think you need Windows Server 2008 R2 to be able to create 64-bit VMs.
Here's a link to powershell scripts for stopping/starting SharePoint services: http://blogs.msdn.com/b/emberger/archive/2009/11/16/stop-and-go-with-sharepoint-2010-on-your-workstation.aspx
I personally always run it in a different instance - either a separate machine or a virtual machine. Sharepoint 2010 is massive, and changes your system with a magnitude not seen by any previous sharepoint version, in terms of databases, scheduled tasks, services...
You should install your SharePoint 2010 in Server2008 R2 if you can ,since then you can do a complete install and use domain account.The installation in win7 is a standalone install and only use system account.It does not match what is in production...
Or if you can, virtualize your SharePoint environment.You need to give at least 4gb ram to SharePoint VM otherwise it is running like a dog.
We installed SP1 on our Team Foundation Server 2008 server. Everything seems fine after the install, except there is a red X on the Reports folder in the Team Explorer in Visual Studio. If we attempt to access the Reporting Services web site, we get a message that says that the "report server is unavailable". There were no errors during the installation.
The Reporting Services service started up fine and left no errors in the event log. We looked at the Reporting Services Configuration Tool and everything shows as OK. We tried restarting the RS service and rebooting the machine. Again, no errors but still no report availability.
The SQL Server instance where our data lives is up and running fine and we can query the OLAP cube and the relational side with no problem. All of our developer machines are already at VSTS 2008 SP1. Visual Studio is not installed on the server.
We looked at the logs files in the RS folder and the only errors that show are the ones that we get when we try to access the web site from IE, but that don't seem to contain any more info about the root cause.
Any help would be greatly appreciated. I'll post any updates on other things we try here.
UPDATE: There is a login error showing up the ReportServer(timestamp).log file. The login on the reporting services service is not the login that is showing up in this error, so I'm not yet sure what process is actually trying to make the connection to the db.
We got this resolved. It appears that the TFS 2008 SP1 install process decided to change the identity setting of application pool for the Reporting Services web site. To resolve we needed to:
Open Internet Information Server Manager
Go into Application Pools
Right click on the Reporting Services application pool
Click on the Identity tab
Change the account from NetworkService to our TFS domain account
Edit the rsreportserver.config located in "\Program Files\Microsoft SQL Server\MSSQL.1\Reporting
Change the "NT Authority\NetworkService" to "OurDomain\TFSDomainAccount"
Restart IIS
Hope this saves someone else some time.
Check the IIS application pools. My feeling is that reporting services doesn't play nice with other web applications (usually I've fixed this in the past by setting a seperate pool for the other applications).