I have SharePoint farm 2010 with two wfe's, in which one wfe is down. Can I deploy a wsp solution now? What are the consequences?
You can but why would you want to put your WFE Servers out of sync. Consequence is whenever the server is up and if you have load balancing enabled, than the request can go to other server where you didn't do deployment.
Excerpt from Installation and Deployment of a Farm Solution in SharePoint 2010
It is possible to deploy a solution on only one server even in a multi-server farm, using the DeployLocal property. This should be done only temporarily as a troubleshooting step. At all other times, the front-end web servers should be identically configured.
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 tried to configure alternate access mappings in my SharePoint 2010 which is installed in WorkGroup Windows Server 2008 R2 server but could not make it work.
Here are my steps.
Go to Central Administration-> Manage Web Application.
Select a web application and extend it.
Provide the my12server.com in the host header and leave other default values as it is. I changed the zone to Extranet.
Click Ok.
After sometime, it creates Web Application in SharePoint and Web Site in IIS.
I have changed my hosts file by adding entry
192.168.1.11 my12server.com
Browse the new extended. It asks for credential. Supplied the correct credential but nothing got display. Just a blank page.
Note: I have however successfully extended web application when the SharePoint 2010 is in domain machine.
Please advice me.
Thanks
Prakash
SharePoint is designed to work in domain environments only. In other words, you cannot expect to run it on an underlying Windows Server which joined into a workgroup and expect full functionality. Although there are blog posts around describing installation in a workgroup environment (or, better to say, using local accounts), I wouldn't recommend wasting time with such a mode of operation.
Furthermore, it doesn't make sense to extend a web application just for the sake of providing another hostname. Extending web applications multiple times is mostly useful when you need different authentication providers for each of them. In your simple case you can just configure multiple Alternate Access Mapping records for a single web application.
I am trying to install sharepoint 2010 foundation. I want to have farm content database on a different machine which is not on a domain, but in a workgroup.
When I do a server farm installation, on 'specify database settings' screen, it asks for a domain account. The problem is that my db machine is not on a domain. Is there any way to install sharepoint with this requirement.
The short answer is no, I don't believe you can. You can get away with installing SharePoint 2010 as a single-server standalone configuration in a workgroup, using local accounts for services. To add other servers to form a multiple-server farm, you need a domain environment.
The most straight forward way to do this is have a second server acting as a domain controller and have both servers in their own network. You could try having SHarePoint, SQL and DC all running on the same server, but this might be too much for one server to handle.
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 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