I've got a report that works perfectly in development previews. But when I deploy I get the following error:
In the Dev Environment the Error displayed is:
Error 4 The data source 'myDataSource'
cannot be found. c:\reporting services
projects\reports\rest_of_path\my_report.rdl
0 0
On the reporting services side the error it shows is:
The data source connection information
has been deleted.
(rsInvalidDataSourceReference)
By itself the datasource deploys just fine and it's present on the server so it doesn't make sense that it "can't find" it. What is going on?
P.s. I found a way to make it work on the server by manually assigning the datasource link that's lost in deployment. But I'd rather not have to do this every time I deploy a new report.
go to Report Manager(http:///reports/pages/Folder.aspx)
Click on the Folder in which u have reports
U will be directed into contents tab where u will find Show Details at the right top corner
Click on Show Details
Check in the particular report and click the edit button corresponding to it
Go to the properties tab and click on it
U will find a menu on left hand side, click on Data Sources link
There u will find radio button selected for A share data source(by default) and a browse button.
Click on the browse button u will find the tree structure of the datasource and the reports folder.
select the datasource in the datasource folder and select OK.
(From a post on http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/622dc981-4378-4331-b2fc-e377660464df/)
Did you upgrade the report files? the RDL spec changed between 2005 and 2008, you need to ensure that you are working with 2008 compatible tools if you are targeting 2008.
I got this to work with 2005, and to make it work I had to change the data source to use OLE DB and Sql Server Native Client 10.0. Another strange quirk was that the data source had to not have spaces in the name. I then had to reassign the report to use the new data source without spaces and then the 2005 rdl worked on the 2008 server.
Related
I'm wanting to publish a workbook to Tableau public, by following these steps which say to click on the "server" drop-down menu then sign into Tableau public etc. But I have no "Server" menu. I Thought maybe I should try updating to the latest version, so I downloaded the newest version from their website but the same thing happened. Anyone know what's up with this?
No server menu
You're using Tableau Public. Therefore just hit the Save icon or File - Save (or Save As) and it'll push your workbook to the Tableau Public server.
The instructions you provided refer to using standard paid Tableau Desktop.
Been struggling with this on a few Crystal Reports, and it's super evident when testing inside of the CR editor.
My report has one database connection (OLE DB to a a SQL Server). On the vast majority of my CR's, when I hit F5, and log into the SQL server for a data preview, the rest of the report will follow whatever database I select.
On some reports, it does not--and the tables in the underlying connection are stuck to a specific database.
Is this a setting within Crystal Reports for the tables below a connection to have their own "Catalog"?
I've found I'm able to correct this somewhat by changing each of the tables Catalog's manually, but I use these CRs against multiple databases.
Has anyone encountered this, and hopefully found a way to fix it without re-creating the report from scratch?
Try to verify the database. If this doesn't help try to update the connection to ODBC and back to OLDE DB.
Something else to try would be to click on Database in the menu bar, then click "Log On or Off Server". This will allow you to select a database server that the report is connected to and then Log Off from that connection, repeat this for all connected databases. Then click Database on the menu bar again and then click "Set Datasource Location" to update the report with the database you would like to use.
This usually works for me:
right click on database fields and left click on set datasource location.
some times you will need to update every table.
but most of the time - after making the connection to database you can update all tables automatically
I want to make a Crystal Report based on a SQL statement. I've read to do that, you add a command to the report, and to do that you have to connect to a database.
When I click the browse button I get the following screen:
Based on my research, it seems you connect to a database. As seen above, all of the file types are .xml files and all that shows up is Dataset. After I click on that, and right click on the dataset name node, the Add Command to Report is greyed out:
Normally you'd be able to add a custom SQL command by right clicking Add Command and selecting Add Command to Report However ADO.NET requires some unique steps in order to add the custom SQL. Instead you'll want to navigate here:
Create New Connection → OLE DB (ADO) → Microsoft OLE DB Provider for SQL Server
You'll of course supply the server information and pick the database.
After adding the connection:
1) Click the plus sign next to your connection.
2) Double-click the "Add Command" node.
3) Type in your SQL query, click ok.
Source: Crystal Reports 2016 Online Help chm file.
HTH,
aEon'
I'm new to Crystal Reports/Crystal Server. Hope someone can enlighten me.
In SSRS, there's a thing called Shared Data Source wherein you can configure a data source like the server and database settings. This data source can then be used by multiple reports. This is very convenient especially if you would change the server name (ex: Production to UAT server) after some later time because you need to change it only on one place without modifying all the reports.
In Crystal Server, is there any equivalent? If not, what are the alternatives?
BTW, I'm using SAP Crystal Server 2013 and Crystal Reports 11.
Thanks in advance.
Edit: Saw this under Database > Set Datasource Location...
Can I save Datasource in Crystal and point all my reports thru this?
You can change data source by using Database-Set Datasource location from menu bar. From there it is pretty simple to change a reports datasource as long as you are changing to a database with same structure. If tables or fields don't exist you will receive an error. If field types used in the report do not match new data structure a mapping menu will appear.
So for example... I have several ODBC data sources which point to same server but different directories. Each directory has identical database structure but for different departments so all different data. I have setup each to be a favorite connection in database manager. I click database from menu bar, select Set Datasource. Select the current datasource. Select the new datasource and click update!
Very straight forward except for the items I mentioned in first paragraph.
We have a purchased application (I'm told it's .NET, it's client server, running on Windows XP, connecting to SQL Server 2005) that uses a Crystal Reports runtime and separate report files (.rpt) to do it's reporting function. I have a copy of the CR Designer program but we don't have the CR Enterprise software. I can open the reports in the designer, get to the SQL Server data source (and any others, I guess), add them to the report, run it, print it -- but I can't figure out how to use the same Datasource, which is a subset of the tables in the database that it's connecting to, to do it, and I can't figure out how to save the report files so they'll work with the application. Real gravy would be coming up with new reports.
Is this even possible?
If you open up the report and then go to Database, Set Datasource Location, under the Properties section you will find a lot of info about the datasource and where it is getting it's info from. If the purchased application is creating its own datasource internally though and supplying it to the report at runtime, the best option that I can think of is to start a trace on the SQL Server and then run a report. You should be able to see the SQL that is issued by the Datasource and replicate it in your own version.
You have the possibility to manage your connection's properties at runtime (ie while launching CR from your app). Here is a proposal: Crystal Reports Datasource remap
If you cannot access your app code, you should then do as proposed by #Anthony, by updating all your connection strings in your rpt files, save the rpt files, and copy then on the corresponding report folder of your app: you might have to find where it's located in your system.
First of all, you'd better make sure you're not violating the application's license agreement by attempting to add to it in this way.
It may simply not be possible to add reports to the app in any case - it depends how it loads them and what it does with them.
To use the same datasource, you should just be able to open one of the .rpt files, then go to File > Save As, and give it a new name. Then modify it to what you want. Of course, if you don't know the authentication credentials the app passes to the report to connect, it would be tricky to test it.
It would help greatly if you gave us the name of the purchased application, as we don't really know what you're up against.
It could be that the application is passing through a filter of the data. So when you run the report from Crystal Reports Designer you get the whole data base, however when run through the program the parameters being passed to the report restrict the data back down.
Create a backup of the report. Then edit the existing report, make the changes you require, preview the report to get an idea it looks right, save the report and run the report via the application.
Warning:
As it has already been stated some vendors may not allow you to edit existing reports, your warranty/sport may be voided by editing existing reports, or reports could even be overwritten on the next update.