| Why you shouldn’t stop / start Analysis Services from SCM when running in SharePoint Integration Mode |
| Written by Lee Graber |
| Tuesday, 19 January 2010 02:41 |
|
Hopefully this will be my first of many posts as I have been meaning to try and start doing memory dumps to this blog. Hopefully some of those memory dumps also made it into our docs … I tried. So most people who are used to using Windows based services are used to using Service Control Manager (SCM) (started via services.msc) to start and stop the service. Some also use “net <stop | start>” to control the service. And in normal situations … this works great. When services are integrated and managed by SharePoint, however, this is not recommended and doing so might leave you a bit confused. This is why: As of SharePoint 2010, they have exposed their “Services” infrastructure which was previously used only by teams like Excel Services, Access Services, … This is some of the infrastructure that PowerPivot for SharePoint hooks into. As such, if you go to System Settings in Central Admin
|
Author articles
- PowerPivot for SharePoint:Set of videos by Lee Graber
- Testing the Claims To Windows Token Service for different identities
- Cannot add the specified assembly to the global assembly cache
- The data connection uses Windows Authentication and user credentials could not be delegated
- Dashboard Bubble Chart Shows a Red X (fails to load)
Most Popular
- Step by step guide on installing PowerPivot for SharePoint on a single machine
- List of suggested datasets to test PowerPivot
- List of PowerPivot DAX functions with description
- How to install PowerPivot for Excel and list of know issues
- Microsoft Virtual Lab: PowerPivot for Excel 2010 Introduction
- List of PowerPivot DAX functions (short)
- Learning PowerPivot and DAX
- PowerPivot's impact on BI pros?
