Skip to main content

Report Server in SharePoint Integrated Mode Error: Cannot create a connection to data source 'DatasSource1'

So having made my report using Business Intelligence Development studio, i successfully deployed it to my Sharepoint Reports Library.

When i tried to access the report from SharePoint, BOMB!!!

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DatasSource1'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors

So after 24 hours of hitting my head against the wall, i got it right.

Try this:
1. open your http://sharepointserver/reports/data connections/
2. click to open the data connection
3. On the credentials section, click the "stored credentials" radio button, type in a domain account in the format 'MYDOMAIN\Accountname' and it password. Note that this account can be the service account of your farm, assuming that its also the account that the report server is using when connecting to the report server database (well at least that's how my farm is)
4. Check the two boxes for "Use as windows credentials" and for "Set execution context to account"
5. click ok and you should be good to go
Labels:

Comments

Anonymous said…
Thank you very much.. Its really helpful.
November 4, 2011 at 4:08 AM
Post a Comment

Popular posts from this blog

SharePoint: How to create a custom action to open Word Documents using "Edit in Microsoft Word".

Imagine you have a SharePoint custom search webpart, and on your search results, you return word documents, you will obviously want to at times be able to open them in your MS Word client program for editing. So basically, depending on your office client installed on your local machine, there are 2 different approaches that can be made for Office 2003 and Office 2007/10, using the same function " editDocumentWithProgID2 ". For Office 2003: - If your document libraries versioning settings have got "Require Check out" ticked, then you will first want to check out the document using: onclick ="CheckoutviaXmlhttp(‘{SiteURL}’, ‘{DocumentDownloadURL}’)" - Then to open the document, you use: onclick =" return editDocumentWithProgID2(‘ {DocumentDownloadURL} ’, ”, ‘SharePoint.OpenDocuments’, ’1′,’ {SiteURL} ’, ’0′);" href ="#" - and now combining the above 2 actions into one clickable action: onclick ="CheckoutviaXmlhttp(‘ {SiteURL} ’, ‘ {...
2 comments
Read more

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.
8 comments
Read more

How to Scope your SharePoint Projects

The "SharePoint project scope" is all of the things that must be produced to complete a SharePoint project. These 'things' are called deliverables and you need to describe them in depth as early in the SharePoint project as possible, so everyone knows what needs to be produced. Take these 5 Steps to scope your SharePoint projects: Step 1: Set the Direction Start off by setting the direction for the SharePoint project. Do you have an agreed SharePoint project Vision, Objectives and Timeframes? Are they specified in depth and has your customer agreed to them? Does everyone in the SharePoint project team truly understand them and why they are important? Only by fixing the SharePoint project direction can you truly fix the SharePoint project scope. Step 2: Scope Workshops The best way to get buy-in to your SharePoint project scope is to get all of the relevant stakeholders to help you define it. So get your SharePoint project sponsor, customer and other stakeholders in a ...
1 comment
Read more