Tag Archive | SharePoint

SharePoint 2010 Error with Performance Point Dashboard: The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.

Note: SharePoint 2010 Beta 2

While using Performance Point’s Dashboard Designer, I received the following error.

The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.

I went into the event log, and saw this:

Here is the text:

An exception occurred while running a report. The following details may help you to diagnose the problem:
Error Message: The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.

Contact the administrator for more details.
Dashboard Name:
Dashboard Item name:
Report Location: {fc25930f-590e-26ac-7da4-f60f076f7b32}
Request Duration: 119.02 ms
User: SPS\david.frette

Exception Message: The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.
Inner Exception Message:
Stack Trace: at Microsoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation analyticReportViewLocation, BIDataContainer biDataContainer)
at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.ExtractReportViewData()
at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.CreateRenderedView(StringBuilder sd)
at Microsoft.PerformancePoint.Scorecards.ServerRendering.NavigableControl.RenderControl(HtmlTextWriter writer)

PerformancePoint Services error code 20604.

I solved this issue by adding my user account to the visitors group of the site. Crazy!


SharePoint 2010 Developer Exams Announced

Microsoft released some exam information on SharePoint 2010, but only for developers. ITPros, I guess you’re going to have to wait.

Check out the Training Page – at the bottom you’ll see an exam list.

Exam 70-573 TS: Microsoft SharePoint 2010, Application Development

Exam 70-576 PRO: Designing and Developing Microsoft SharePoint 2010 Applications

For IT Pros, Exams Exam 70-667, 70-668 don’t have pages.

Overall Exam List

SharePoint 2010 Release Date Announced for May 12

Get ready for SharePoint 2010. The news is official now.

RTM is April 2010.
Available for businesses on May 12, 2010.
Available for everyone else in June 2010.

Here’s the launch page:

Changing the SharePoint Site in a Visual Studio 2010 / SharePoint 2010 project

I created a new Visual Studio project and entered in the url of a site that simply didn’t exist. Whoops! I didn’t want to create a new site for just this project, so I wanted to change the URL that Visual Studio 2010 uses to deploy this SharePoint solution.

It’s not located in the project file itself. It’s located in the user config file of the project.

Here is the file:

Once this file is open, you can change the url, save the file, and close it out.

Old setting:

New setting:

After editing this file, you’ll have to reload your project.

It’s not completely obvious where this setting is, but once you’ve done it, you’ll remember that the key is the user configuration file.

Turn on the Developer Dashboard via PowerShell

I found some outdated information for the SharePoint snap-in for PowerShell.  The cmdlet to enable and disable the developer dashboard has been deprecated. To use powershell, we ultimately need to use the Object Model.

To view the answer, just scroll to the bottom!

In particular, we’ll use this Library::Object     
ContentService.DeveloperDashboardSettings;  The original documentation said to use this:     

PS C:\Users\svc_sp_admin> Set-SPFarm -DeveloperDashboardEnabled      

The term 'Set-SPFarm' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling
of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:11
+ Set-SPFarm <<<<  -DeveloperDashboardEnabled
    + CategoryInfo          : ObjectNotFound: (Set-SPFarm:String) [], CommandN
    + FullyQualifiedErrorId : CommandNotFoundException


So I tried this:       

PS C:\Users\svc_sp_admin> Set-SPFarmConfig -DeveloperDashboardEnabled
Set-SPFarmConfig : A parameter cannot be found that matches parameter name 'DeveloperDashboardEnabled'.
At line:1 char:44
+ Set-SPFarmConfig -DeveloperDashboardEnabled <<<<    + CategoryInfo : InvalidArgument: (:)
[Set-SPFarmConfig], ParameterBindingException + FullyQualifiedErrorId :


Finally, I was told by a certain ADMIN to use the OBJECT MODEL. LOL. He was right, though. 🙂 He’s a good admin and developer wannabe.       

PS C:\Users\svc_sp_admin>

DisplayLevel                 : Off
TraceEnabled                 : False
RequiredPermissions          : AddAndCustomizePages
MaximumSQLQueriesToTrack     : 50
MaximumCriticalEventsToTrack : 50
AdditionalEventsToTrack      : {}
Name                         :
TypeName                     : Microsoft.SharePoint.Administration.SPDeveloperD
DisplayName                  :
Id                           : d72a704a-81a1-429f-8c4d-5372e5524b42
Status                       : Online
Parent                       : SPWebService
Version                      : -1
Properties                   : {}
Farm                         : SPFarm
UpgradedPersistedProperties  :


   And while I appreciate the blogs out there that teach Admins how to code, let’s face it, even developers don’t instanciate objects when they don’t need them. So, here’s the long way that some suggest:     


$val = "On";
$cs = [Microsoft.SharePoint.Administration.SPWebService]::ContentService;
$cs.DeveloperDashboardSettings.DisplayLevel = ([Enum]::Parse([Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel], $val));
Write-Host ("Developer Dashboard Level: " + $cs.DeveloperDashboardSettings.DisplayLevel)

Let’s consolidate that:    


$cs = [Microsoft.SharePoint.Administration.SPWebService]::ContentService;
$cs.DeveloperDashboardSettings.DisplayLevel = ([Enum]::Parse([Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel], “On”));
Write-Host ("Developer Dashboard Level: " + $cs.DeveloperDashboardSettings.DisplayLevel)

OK. One more consolidation. Use this single command to set the developer dashboard.    

ContentService.DeveloperDashboardSettings.DisplayLevel =

It’s very long, so I suggest copy and paste. I had to include RETURN breaks as it scrolled off the page.  

And to view it, use       


Happy SharePointing!

Meeting unique validation requirements for content types in the same list

Meeting unique validation requirements for content types in the same list.
We can create seperate forms for each content type using InfoPath. It’s pretty easy. However, you cannot customize New/Edit/View forms with InfoPath. You can, however, use SPD and ListView WebPart. That will be the topic for another post.

So, first I’ve set up my Tasks list to have an extra content type (ignore the summary task – I will). I have the Task content type, which is out-of-the-box. I also have a Simple Task content type, which has Task as the parent. I’ve added a new field, called Owner. That’s the only difference. See List Settings from within IE and then from within SPD.

(sorry for the poor image, WordPress is giving me a headache with it. SimpleTask has an Owner field, Task does not.)

Now go to your Tasks List and click Design Forms in InfoPath. Select the content type you wish to modify. I’ll demo a custom InfoPath form for my SimpleTask content type.

Here are my changes to the form (I’ve added a blue title and made the Owner field red to bring attention to it):

Using the InfoPath client Backstage area, found under File tab, the form is published to the list.

This message indicates all went well.

Now, in the web browser, selecting a new SimpleTask from the New Item menu will display the newly customized form.

Here is the customized Simple Task content type form.

A customized Task form can also be created.

Here is the customized Task content type form.

Now let’s make the Task more complicated in validation. Let’s create a rule that says the “Due Date” is required when a “Start Date” is provided.

After publishing the Task form and starting to fill out a new task item, the validation error is revealed.

So, in summary, you can have an InfoPath-customized form for each content type. This works well if you need to validate data differently for each content type. Using InfoPath, we can set our own data validation rules. Since each content type can have its own form, each content type can have its own validation rules.

Unable to synchronize the project with the SharePoint tasks list due to a circularly-linked task

If you see this error “Unable to synchronize the project with the SharePoint tasks list due to a circularly-linked task” it is most likely because you linked a task to itself.

Notice in the task list, the Predecessor is the same as the Title.

So, to rid yourself of the error, remove the self-referencing task from the predecessors list, save the item, and go back to Open Schedule to get back into MS Project.

Note: See the task item edit form below. The predecessors list allows the selection of itself. This can’t happen in the create form, but it can when you edit an existing one. It would have been nice if Microsoft would have thought of this and changed the form to lookup GUIDs and refrained from using it’s own GUID. Obviously a seperate form form the create form would be needed, but I don’t think that would have been too much for MS to do. Perhaps in the RTM version it will be enhanced.

Why WPF makes sense using the ClientOM where SilverLight might not

First off, I’m not jumping to conculsions. Sometimes WPF will make more sense that SilverLight.

While WPF can run on the server and use the SharePoint DLLs and full OM, it can also be delivered to the desktop. Desktop WPF apps cannot use the SharePoint DLLs. Thus, bring in the SharePoint Client Object Model. So, you can have Silverlight pretty, but WinForms functionality, all in one.

So here are some advantages of using a WPF client.

  • It’s synchronous programming
  • No cross site scripting (XSS) issues

So how about a quick example?

Here’s the xaml

Here’s the most basic code. Notice how much less code there is in the WPF example than in the Silverlight example!

Here’s the output on my sample site

The referenced assembly “Microsoft.SharePoint.Client.Runtime, …” could not be resolved…

You may see this error when you compile

The referenced assembly “Microsoft.SharePoint.Client.Runtime, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=MSIL” could not be resolved because it has a dependency on “System.Web, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” which is not in the currently targeted framework “.NETFramework,Version=v4.0,Profile=Client”.


Go into the project settings. They are probably set to .NET 4.0 Framework. In order to use the ClientOM, set them the Framework to 3.5. The project will be unloaded and reloaded, so be sure to save your work before going into the properties canvas.

Next time you build an application intending to use the ClientOM, set the .NET Framework to 3.5 when creating the project.