Hi, I have a report which I want to deploy in report manager but it's not getting deployed there. Let me give you guys a bit more detail. I have a report where I have used an OLE provider in the connectionstring to connect to a cube. The properties of the connection string are Type - OLE, Provider - Microsoft OLE DB provider for Analysis Services 9.0. Connection string is, Provider=MSOLAP.3;Data Source=ServerName;Initial Catalog="Cube_Name". I tried to use the Analysis services (as type) but in that case I was not able to connect itself. I have 2 servers, say A and B. I have BIDS installed in server "A", where I have created my report. In server "B" I have the Analysis Manager (AS 2000). So while creating the report in BIDS, I had to choose the OLE provider to connect to the cube. I tried initially with the Analysis services but in that case I was not able to see the list of cubes in the wizard for creating my DataSource. Now my problem is that while the report runs perfectly fine in BIDS, as soon as I deploy it in the report manager (which is in the same server as where I have created my report in BIDS, in our case server A), i get an error, An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'OLEDataSource'. (rsErrorOpeningConnection) The following system error occurred: No connection could be made because the target machine actively refused it. I am perplexed as the report runs fine from BIDS which is in the same server as my report manager. Any clues to solve this ? Am I missing something here ? Thanks in advance, Suman

Hi Guys, Any pointers please on the above issue. I did some google and found that for AS 2000 cubes, we need to add the users in the cube roles. I have added the users (that have been used in the datasource connectionstring) in the cube roles but still its not working. Do I need to process the cubes once more? Thanks in advance, Suman

Does the user that the ReportServer service runs under have access to the cube? This issue is usually caused by the fact that the user you are connecting to the cube is not the one you expected. Check which user you have authenticated with and the report server service. It is entirely possible that when you use BIDS, you are using a different login which has more access than when you are hitting the cube.Regards, Steve If this post answers your question, please mark it as an Answer.

Hi Steve, I think your suggestion is worth exploring. Unfortunately I do not have the access rights to check the cube or the Reporting services configuration. I will ask the Tech support guys to have a look and then if necessary add the Reporting Services user in the cube. Thanks for the suggestion, Suman