SharePointSupport

* Recently we had issues with our distributed cache system that was set up on are farm quite some time ago when I built it with SPAuto-Installer.  This could have been from rolling out cumulative updates or what have you.  There is very little documentation on the web for this. *  In our case we had 4 servers (2 web front-ends and 2 application servers)  all with the distributed cache enabled.  Only one server was running the distributed cache. *  The correct topology for distributed cache is for it to exist on the web front-ends.  So we made some changes to the farm.  Clean up all 4 Servers using the following commands: #Stopping the service on local host Stop-SPDistributedCacheServiceInstance -Graceful #Removing the service from SharePoint on local host. Remove-SPDistributedCacheServiceInstance #Cleanup left over pieces from SharePoint $instanceName = ”SPDistributedCacheService Name=AppFabricCachingService” $serviceInstance = Get-SPServiceInst

Why Performance Testing ? If you work on a team responsible for the delivery of SharePoint into your organization there's usually a mountain of tasks to complete before making it live. One of the most vital tasks is to make sure that SharePoint is "fast" enough to meet the requirements of your users. If you get performance problems after going live this can easily ruin all of your hard work and - even worse - your users will think SharePoint sucks! So, by the time you "go live" you should be confident of the following : You know the maximum load your service can take. You know your service can run for a pro-longed period of time. You know the point at which you may need to add more servers, so you can plan. When you do get to maximum load you need to know where the bottle necks in your service are, (e.g. SQL, Network, SP servers). If you don't know these metrics up front, then you are going to have to react as problems occur. If you have t

I have created a new site. When I open the site uing the URL the browser gives this. HTTP/1.1 404 Connection: close Date: Tue, 01 Feb 2011 15:44:05 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12.0.0.4518 Solution : * The most probably reason is you haven’t create the Top-Level site collection . * SPS will not create the Top-Level site collection for you by default. To create the Top-Level site collection, goto Central Administration > Application Management > Create Site Collection.

The problem i am having is that i installed SharePoint 2010 and SharePoint designer 2010 If i try to open a site with the SharePoint designer it tries to open the site but gives a error. in the event log is the following: WebHost failed to process a request. Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/11404313 Exception: System.ServiceModel.ServiceActivationException: The service '/_vti_bin/client.svc' cannot be activated due to an exception during compilation. The exception message is: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. Parameter name: item. ---> System.ArgumentException: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. Parameter name: item at System.ServiceModel.UriSchemeKeyedCollection.InsertItem(Int32 index, Uri item) at System.Collections.Generic.Syn

Error I have created a site collection and then create two team sites on sharepoint server. Sites are working fine from central Admin but they are not appearing in IIS manager. Also when I try to edit a sharepoint site on sharepoint designer 2010 follwing error comes. Unable to open website following causes: 1) the web server may not have sharepoint installed 2)The web server may be temporarily out of service 3)if you are connecting through a proxy server the proxy settings may be incorrect 4) An error may be occured in the web server The IIS manager only showing the follwing sites Sharepoint 80 and sharepoint central admin When I try to create a site on sharepoint designer following error comes: The web site must be created on a server that is running microsoft sharpoint foundation server please chooose another location. I have installed sharepoint server 2010, sharepoint foundation server 2010 and sharepoint designer on my pc. solution : * In IIS Manager, you'r

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai

I have installed a new server with WSS 3.0.  I can open the SharePoint site from the local computer, but I cannot get to it from another computer.  I installed it as a stand alone server, it is a member of my domain.  I have a development server that was not a member of the domain (it is it's own DC) that I have no problems connecting to.  The IIS settings are the same on both servers. I the only difference is the one the I can't connect to is a member of the domain.  I know this has got to be simple but I am not seeing it. solution : I knew it was simple.  Windows firewall .  I was not the one who configured the new server and assumed that the firewall would be off or configured properly.

I am having this strange problem . All of a sudden all of the new sites created in the SharePoint are not opening locally. And even iis is failing to pick up the ip binding with a site. All my existing sites when browsed from IIS manager are giving certificate error and ultimately showing connection problem error. Only thing that was done was the patching this week. I have no idea why all this is happening. Has any one faced similar problems before. Solution : * try stopping the Foundation Web service on the affected farm member and re-starting it . * If you were adding SSL certs to the IIS sites, it may be a case of attempting to use the same IP with different SSL certificates across IIS web sites.  IIS 7.5 and below do not support SNI, so you have to have a unique IP:SSL Cert combination, or get a Wildcard or SAN certificate instead.

Protocol Port Usage Comment TCP 80 http Client to SharePoint web server traffic (SharePoint – Office Web Apps communication) TCP 443 https/ssl Encrypted client to SharePoint web server traffic (Encrypted SharePoint – Office Web Apps communication) TCP 1433 SQL Server default communication port. May be configured to use custom port for increased security UDP 1434 SQL Server default port used to establish connection May be configured to use custom port for increased security TCP 445 SQL Server using named pipes When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP port 445 TCP 25 SMTP for e-mail integration Cannot be confi