| Tips and Tricks for Troubleshooting a Microsoft SQL Server PowerPivot for SharePoint Installation |
| Written by Dave Wickert |
| Friday, 25 June 2010 21:17 |
|
PowerPivot presents an interesting challenge for debugging and figuring out what is happening when problems occur. There are a lot of moving parts on a running farm. PowerPivot uses a mixture of SharePoint and SQL logging, tracing and debugging. In this chalk talk we review the various logs and trace files that are generated by SharePoint and SQL (and how they map to PowerPivot features). We take some common usage scenarios, inject faults, and show how you identify and rectify the problem. When do you look at IIS logs; when the NT event log; when SQL? And what do you do on a large farm where the various machine logs and traces are not consolidated. A customer’s first impression of a new product is all-important. This chalk talk is designed to help you guide customers, whether you are a TS, MCS, or support person. We give you the knowledge that will help you help your customers. Presenters: Dave Wickert and Rob Collie
|
Author articles
- Video - Deploying and Managing a PowerPivot for SharePoint Infrastructure Using Microsoft SQL Server 2012
- Video - Deploying and Managing Microsoft SQL Server PowerPivot for SharePoint
- General problems with Gallery snapshots not being taken - no items listed in the ULS log
- Importing XML data
- Data feeds: Cannot get schema? But it is there ...
Most Popular
- Step by step guide on installing PowerPivot for SharePoint on a single machine
- List of suggested datasets to test PowerPivot
- How to install PowerPivot for Excel and list of know issues
- List of PowerPivot DAX functions with description
- Microsoft Virtual Lab: PowerPivot for Excel 2010 Introduction
- Learning PowerPivot and DAX
- List of PowerPivot DAX functions (short)
- PowerPivot's impact on BI pros?



