Tuesday, August 31, 2010

SharePoint 2010 - Part 2- PerformancePoint, BCS and Branding

Here are few problems I expereinced during my first SharePoint 2010 engagement:

Like I mentioned in my earlier post this project consisted of dashboards, SQL Server reporting, branding etc. The follwing lists the various issues I encountered and their resolutions:

  • While trying to install and configure Reporting services on SQL box I faced some challenges. Error: "SharepointIntegrated mode is set to true but could not find the microsoft.sharepoint.dll". Resolution to it was to not install Reporting Services on the SQL box but instead on the WFE and create new db on the SQL box. That way we do not need to worry about the sharepoint dll.

  • While configuring BCS (business connectivity services) I was faced with an error: "Access denied". Resolution: Add a new application ID in secure service store application in CA. Edit the database connection in external content type to use "windows impersonation" and enter the application ID created earlier. Go to "Business Connectivity Service" in CA --> Application management and set permissions for "All authenticated users" and others.

  • SharePoint 2010 now displays errors in the form of correlation ID. This way it is able to group related errors in one ID. Use this correlation ID from the error page and search for it in the 14 hive logs. (remember its now 14 hive instead of 12 hive)

  • As I had to extensively use PerformancePoint (PP) in this project I was required to generate a new key for PP service application. Without a key you will be shown an error: "The unattended service account cannot be set for the service application. The secure store service key might not have been generate or properly refreshed after the service was provisioned."

  • My client wanted to have a better looking page than the default report viewer page (RSViewerPage.aspx). As this page does not inherit from any master page and contains no placeholders you are better off creating your own masterpage and linking to it.

  • While creating a SSAS KPI from Sharepoint KPI list the conenction timed out with an error :"The connection either timed out or was lost. This data connection does not use encryption for the communication with the SSAS to help prevent unauthorized users from viewing this information". Resolutions was to got to IIS manager, go to IIS authentication for the site and enable ASP.NET impoersonation --> edit --> change settings (identity to impersonate) and give a domain user account there instead of Windows Authentication.

  • Now I am new to reporting services but most of you with exposure to SSRS will find this as a trivial task. While trying to run a query in the query designer I was blown with an error : "the query contains the parameter which is not declared". Resolution: even though the report designer had these parameters defined the query designer expects them to be defined in its interface.

  • I encountered an issue for which I could not find a permanent cause. I was required to create a custom masterpage with some ribbon UI changes. I changed the default home page to one of my custom pages inheriting from the custom masterpage. While trying to do so the ribbon UI failed to load with a javascript error below in the taskbar "undefined is null or not an object" in scriptresource.axd. It worked fine if I set default.aspx as the home page. Never could understand why this problem occurred. The important thing for me at that time was to get this working for the client.

These were some of the issues I remember while working on my first SharePoint 2010 implementation.

To follow more on SharePoint 2010 check out my next post of the two part series.

No comments:

Post a Comment