Hey guys,
I have three servers, assume ServerA,ServerB, and ServerC. ServerA is where the database(datasource) is located. ServerB is used as a report server and Server C is my local machine where I design reports. So obviously I deployed the reports from my local machine(server C) to the remote report server(server B). Deployement was successful but I got the following error when I run the report from the report server. You might think that the report is not pointing to the right data source, I checked that several times and it is pointing to the right data source.
However, I also observed that when I deployed the same reports on the local machine report server(server C), it run with out any problem. So it seems that the problem is related with the remote server(server B) not the data source.
Does anybody has a solution for this.
Thx
Normally it is one of two things when I encounter this message:
1) The report is not connected to the datasource on ServerB (as you mentioned).
2) The DataSource Connection String on ServerB has a misspelling somewhere. (If ServerA is Case Sensitive Collation, check upper/lower case).
If not those, make sure ServerB can connect to the database on ServerA through some other means (ODBC, etc). Good luck.
|||Well, the quick and easy solution is to change the configuration for the connection already deployed to ServerB. Since it's working from your local PC/ServerC, so just use your ID and password to config the connection on ServerB. But if ServerB is really a production server, it's better to create a separate logon, either a Windows account or a SQL account with the access to ServerA. Make sure to set the password to never expire. Then use this account to config the connection on ServerB. HTH.
|||I don't think I need to config the connection on ServerB, because, there are other several reports deployed and run with out any problem. FYI the existing reports was actually deployed by some body else. This problem happened for the new reports that I developed. It is very weired situation.|||The problem has to be with the connection from ServerB to the data source, otherwise you wouldn't be able to run it from your local machine.
Are you using a shared data source?
Go to the properties of the report in Report Manager, and select 'Data Sources' from the left. Select 'A custom data source' and verify Microsoft SQL Server is listed in your 'Connection type'. The 'Connection string' should look like this: Data Source=ServerA;Initial Catalog=DB_Name. Select 'Credentials stored securely in the report server' and type your username (domain\user) and your password. Then check the box 'Use as Windows credentials when connecting to the data source' and hit Apply at the bottom.
If you do this from ServerB (RS Server), then you should get an informative error message if/when you get the error. Do you have access to log directly into ServerB?
Jarret
|||Hey Jarret,
First, I really appreciate your follow up to assist me in solving this issue.
Actually, I am using a shared data source to generate the reports. As a matter of fact, the existing reports also uses a shared data source and run with out any problem. I also tried what you said up here, however, I got the same error message. Anyhow, I just wanna cross check one thing with you. If I select A custom data source, which server's username and password do I have to apply, ServerA(datasource), ServerB(report server), or ServerC(Local machine)?
Thx.
|||I really don't mind. Actually, I'm sorry that I haven't been able to get you a solution yet.
If you select 'A custom data source', then the connection string will have to point to your database server (ServerA) and you'll have to supply either a SQL account or a windows account (domain\user) that has permission to read the data.
If this still doesn't work, I would start a new report without using the shared data source and just store the connection information into the report itself.
Jarret
|||The problem maybe because the shared datasource you are using may be in a different folder on your report manager whereas you would have specified a different targetdatasourcefolder (Report project properties) for your report. So, it is trying to create that data source at runtime and not able to do it because you dont have enough permissions.
Shyam
|||I'm very disappointed with this annoying error message. I experienced the same kind of problem in some other project and I was able to solve it with no time. One thing which makes me angry is that the existing shared data sources are working fine, however the data source that I created doesn't work. I wasted a lot of time on this. I don't know what to do next. May be go for a vacation LOL.
Anyhow I will let you know if I am able to find something new. Please keep on posting me if you have any idea.
Thx.
|||Have you read my post and any progress?
Shyam
|||Hi Shyam,
I checked that too. On my project properties, the TargetDataSourceFolder is 'Data Sources'. On the report manager, the data sources are created in the same folder name, i.e. 'Data Sources'. I couldn't see any problem.
I even created a new data source (which is not a shared data source) on the report server level and pointed it to my report, but still getting the same error message
Maybe the following links will be of some help to you:
http://msdn2.microsoft.com/en-us/library/ms365166.aspx
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=288600&SiteID=17
Shyam
No comments:
Post a Comment