using crystal reports 13 with VS 2010. everything works fine on the development machine.
once deployed the reports wont show in the browser. on the web server (windows 2008, IIS7) i have installed crystal report run time.... feel like i am missing something else... has anybody experienced the same issue..
another issue i did notice was on the development machine , the crystal reports were sensitive to the browser that it was run on... on the latest browsers no problem at all, but in IE 7 or 8, only quarter of the reports would appear.... how can one over come this...
Rgrds
Adr17
I had the same problem, and the solution is to copy the folder aspnet_Client into your web application (you will find the folder in wwwroot)
Crystal Report TroubleShooting
1. Bob is undefined, copy file under IIS default folder's crystal report file to web site's place
2. Invalid Index => alias name not same with stored procedure name
3. Remember to verify database
4. try to exec stored procedure in management studio and make sure select explicit field name instead of *
5. try to preview crystal report
My problem was my reports where a virtual directory (IIS7) and Crystal Reports has a bug where it looks for the files in the aspnet_client folder in the root of the website and not in the virtual directory. So I had to copy the aspnet_client folder to the root.
Related
So I followed the approach using the powershell scripts to get all the information from a SSRS server and download it to my local machine. That all worked fine. I created a SSRS project in VS 2019, included the downloaded files and I can open and edit all the reports. The challenge is when I go to preview the reports, I get the error message below indicating it cannot find the data source. The data source is defined within the report as shown below:
I have seen comments regarding how to handle this when the data source is an item in the project but that doesn't apply here. And idea what I am missing?
FYI - I am attempting to preview the report using a remote SSRS sever and I have the URL configured in the TargetServerURL of the project.
Any help would be appreciated.
UPDATE: I did just notice that in the folder with my reports in the project there is a JR.rsds but I am not sure if that makes a difference.
This is an extremely vague question because I don't know enough to know what I don't know. Here's my situation:
I have downloaded SSDT and connected to a data source (A SQL Server DB instance). I've created a report. I can preview the report in VS. I can publish the report from the VS build menu and it gets published to my local reports server that seems to have been installed by default at http://localhost/reports. I can use a browser to go to that url and see the report I created.
Now, the problem is that this is all only in my local development environment. I installed SSDT through Visual Studio and it auto-created my reports server. Is there a way to install a reports server without installing visual studio and publish the reports from a report solution using an MSI created by a packager like WiX? I'm having a hard time finding information about how to do this.
The report server is typically installed when you install SQL Server. If you want to publish reports so that others can use them do the following:
Go to your VS solution and right-click on the project then select properties.
Set the TargetReportFolder (this will be created if it does not
exist). This will usually reflect the name of the group of reports
you are working on (e.g. 'HR Reports')
Set the TargetServerURL to the report server on your SQL Server box for example http://mySQLServerBox/reportserver/
Set the TargetServerVersion to match your SQL Server installation version (SQL Server 2016 etc)
Now you can simply right-click a report rdl in VS and choose deploy, you can also do the same at the folder level to deploy all the reports in one go.
To access the reports, go to the web portal which will usually be http://MySQLServerBox/reports
I hope this is what you are looking for..
I have a project solution I am migrating from another computer, and the project opens the wrong "Opened URL".
When viewing the Properties for the Web Site, the following path is correct and working on the old computer.
file:///C:/Collection/Server Workspace/store.domain/Main/store.domain
When the same solution is transferred via TFS to my computer, the Opened URL path adds an additional "store.domain" at the end of the path:
file:///C:/Collection/store.domain/Main/store.domain/store.domain
Editing the path inside Visual Studio isn't an option, its greyed out and not editable. Editing the text of the solution file shows no duplicate "store.domain"s either.
I'm sure I'm missing something simple, perhaps with IIS?
You need to check in the web site from the old computer to have the correct URL stored in TFS Version Control. Then get latest version for that web site on your dev machine.
Solution: The solution file on the old computer only worked when inside the folder with all of the files. The same solution file on the new computer, needed to be in the parent directory.
So the fix was to move the solution up one directory, for whatever reason. This allowed the phantom /store.domain folder to line up correctly.
I just created a Report Project with 1 .rdl in Visual Studio 2008. I then deployed the report to the SSRS Server and I can now see the report in the Report manager.
I made a change to the report using report builder 3.0.
Is there a way that I can "get latest version" from the report server of the .rdl when I open my report project in Visual Studio again?
I am guessing that 1 way would be to download the .rdl and add back (overwriting) to the report project but I am wondering if VS has a built in function to take care of this for you?
There is no built in functionality in VS to attach to an SSRS instance and pull down the .rdl files. Since they can be moved, edited and deleted, outside of the designer there could be numerous issues with doing that. Just check all your local project files into source control and manually update if needed. Since I don't edit outside of VS I never had to deal with "pulling the latest version from ssrs". However, I have come across third party tools that may have functionality to make it easier.
If this is going to become a daily struggle for you then you may want to take the time now to automate the process using the ReportExecution2010 or ReportExecution2005 web service api.
Visual Studio is used to create and deploy reports, once they are deployed, there are no links between the report in Visual Studio and the Report Server, and there will never be. Think about it, you can deploy the report to X servers, so how could Visual Studio find which report you are talking about.
To ensure you are working on the latest version, you will have to download it and overwrite as you say, although I would compare it instead to see if there are changes not deployed.
If you are working with other developers that would potentially redeploy the report, then you can just check the last modification user of the report.
In all cases, I would strongly suggest to always check-in/commit when you deploy a report.
If you want to download several reports from the report server, then you could use a tool like RSScripter for example.
I'm re-installing an application on a users machine that uses Crystal Report after they had their machine refreshed.
After reinstalling the application it works fine. Only when trying to run the reports does the error occur.
"Run-time error '-2147206249 (80043ae3)';invalid TLV record."
I've looked into this error but cannot find a solution. I've noticed that they don't have a directory for Crystal Reports under the common files directory. But the dll's are in the system32 directory.
My question is, does the Crystal Report Viewer need to be installed before the reports will run?
ie. a directory under common files with the dll's there.
If you've built Crystal into the application then no, you should not need to.
However there are Crystal dll's, the main of which is crw32.dll, which need to
be installed on the target machine.
When you package your app it should include (and you should tick any prompts that
indicate this) packaging up the third party (such as Crystal) install files, such
as dll's. These then get installed when you install the main application.