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 Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an ...
7 comments
Read more

Error "403 Forbidden" on Sharepoint Search Settings Page

Ok so I had to struggle with this error for like 48 hours, busy googling for a solution. This error came up at the same time on both our live and test environment after we were hit by the worm Microsoft reported a few days ago. So here is how I went about sorting it out: Using STSADMIN commands 1. I first ran stsadm -o osearch -action stop –f 2. Then stsadm -o osearch -action start -role indexquery 3. And stsadm -o execadmsvcjobs So now I tried to access the search site and it told me that I had to assign an index server, of which I did, then I again from the index server had to run stsadm -o execadmsvcjobs. At this point, I had to provide access to c:\windows\tasks, from the command line, on our index server for the local group WSS_WPG as follows 1. By running attrib -s c:\windows\tasks on the index server so as to be able to change the tasks system folder attributes. 2. Then I added the local group WSS_WPG with read and write access 3. And now take back the attributes of the tasks sy...
4 comments
Read more