Tag Info

Hot answers tagged

4

Paolo Pialorsi has described it well in his book Microsoft® SharePoint® 2010 Developer Reference : Service This is the actual service, with its own engine, data storage, and infrastructure. It can be hosted on a specific server of the farm, or it can be a third-pary service. For example, this could be an external ERP, or it can be a software component ...


3

To toggle developer dashboard $service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $addsetting =$service.DeveloperDashboardSettings #Use On Off or OnDemand $addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off $addsetting.Update()


2

Consolidating your service applications pool into a single one will impact your farm, no doubt about it, but both in positive and negative ways. Let's start with the bad ones... You will not have process isolation. For instance the SSO service should have it's own process for security reasons If one service app dies/crashes, all of your service apps will ...


2

It is extremely important that there be sufficient storage space in place on each and every server to support your environment or you will have stability issues and a general performance impact. There are non-SharePoint things that will be written to the disk, there are system logs, as well virtual memory. As disks fill up, they will slow down further. ...


2

There is a risk of server instability by not having free disk space on C drive. For example memory management and Windows being able to write to system files. You could set the NLB load to 100% for wfe2 while you fix the issue to prevent users experience any issues accessing wfe1. This will also allow you to reboot the server if necessary. Confirm other ...


1

A web part is for displaying content, not to provide a content repository for other components. A few options: Perhaps you don't need a web part at all, just create a list and store the image there. Perhaps you also need a web part. Create a list, store the image there, and reference that image from the web part. Other components could then also reference ...


1

If its just about getting webpart content from an accessible page within same domain, I dont think you will need a webservice for it. You can place your webpart within a div (id=container) and use below Jquery : $('#result').load('sitepages/test.aspx #container'); When this method executes, it retrieves the content of sitepages/test.aspx, and then jQuery ...


1

Developer dashboard should be enabled only when you see some unexpected behavior (delay in loading webpart etc) and want to see what part of page is taking more time. Enabling it will surely affect performance of your SharePoint site since it will have to load the calculations. It is always better to keep it off when everything is well :) Regards, Sudhir ...


1

The most common causes of problems with Office Web Applications are: OWA not installed (obvious, but it happens) Word viewing/PowerPoint/Excel calculation service not started Word viewing/PowerPoint/Excel calculation service application not created OWA service account does not have db_owner rights on the content database I would suggest checking ...


1

Apparently, you was confused between Service Application and Service in SharePoint 2010 Service Application (CA > Application Management > Manage service applications): it's hard to define what Service application is. However, Service application is responsible for separate capabilities on SharePoint 2010, such as Managed Metadata Service ...


1

I just posted a few Powershell commands that might be useful to you. Check Application Pool name IIS 7.5 On SharePoint Server 2010 I would say, don't modify anything directly on IIS. Either use the SharePoint Powershell SnapIn cmdlets, or use the CA. Cheers


1

Please refer to the following TechNet article on 8032 and 8062 events. One or more of the suggested resolutions may help you address you problem or at least point you in the direction of a resolution: http://technet.microsoft.com/en-us/library/ee513044.aspx I had a customer with this issue about a year ago and they ultimately had to add more WFEs, but you ...


1

It's really hard to tell what is going on. Use the resource monitor to check the WFE's for CPU, disk I/O, network, IIS connections/requests per second/queued requests etc. It could be anything from custom code, bad configuration to faulty hardware. The error you see is basically that SharePoint starts throttling to be able to catch up with incoming requests. ...



Only top voted, non community-wiki answers of a minimum length are eligible