Deploying a Reporting Services report to Lawson's LBI
-
I am the first person in the company to write a Reporting Services report. It runs, it builds, but I can't get it deployed (desktop or to a server). When a consultant tried to deploy the .rdl file to Lawson's LBI dashboard, it just shows the XML. I wrote reports at a former company but had a DBA who handled deployment there.
The server has IIS running on it but I don't know if something else needs to be loaded on it or done to my report so that it will deploy to the server. I'm hoping that in the deployment process, it will create a file that the consultant can deploy to Lawson's LBI dashboard (XML?).
I'm hoping someone out there has experience with this and some good advice for me.
-
I don't know anything about Lawson, but if you could post any errors you may getting when attempting to deploy someone may be able to help you out.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question -
I link to RS 2005 reports from within LBI at our company.
Instead of referencing the RDL, use http. This is a sample link for your URL field:
This will require you to deploy your RS reports to a report server. The choices after '&rs:command=Render' are optional. I had turned off the toolbar and parameter sections to conserve dashboard space.
Hope this helps.
-
billwarn: Thanks. I think this piece is going to be pivotal.
Jack: I've never deployed a report before (my DBAs did this previously), so we put my project on a server and when I try Build, Deploy, it says:
A connection could not be made to the report server.
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)
Is it important for me to do this step before what billwarn says will work correctly?
Thanks guys.
-
I forgot to mention (too much multitasking) that I found out this morning that the server we put the solution on, is on 2000, not SQL Server 2005. Could that be why I got the error I received? Thanks.
-
If you right-click on the project name (in your developer window), and choose properties, you will get a dialog box that will allow you to fill in 'TargetServerURL'. It defaults to http://localhost/ReportServer.
If that isn't correct for your environment, that may be causing your error. I'm using 2005, not 2000, but I would expect it would be similar.
-
I put this in Report Properties for URL:
Received error:
A connection could not be made to the report server
/reportserver?/Trans_History2_New/Trans_History2_Newrs:Command=Renderrc:parameters=truerc:toolbar=true
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible verion.(Microsoft.ReportingServices.Designer)
Note the message has removed characters, but they are in properties. I think it has to be a SQL Server version issue or Report Server isn't running on that server--I'm checking on that. Thanks for the info.
-
gardenlady (8/27/2008)
I forgot to mention (too much multitasking) that I found out this morning that the server we put the solution on, is on 2000, not SQL Server 2005. Could that be why I got the error I received? Thanks.A couple of questions:
1. What do you mean the server you put the solution on?
2. How did you put the solution on the server?
As billwarn has said, if you put the correct report server name in the project properties for the project and then right-click the project or report and click "Deploy" the report should be deployed.
Here are some screen shots:
Finally, if you really are running SSRS 2000 and you built the report using the 2005 report builder you are going to have to redo the report using the 2000 report builder as they are incompatible.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question -
I think you can see by the attachment exactly what I put in my Properties.
Yesterday we put the solution on the server thinking maybe it needed to be there to successfully deploy. I didn't remember that from my prior job, but desperate times.
Anyway, I put the string in the attachment in the TargetServerURL in my desktop project and tried to deploy it and got the same error. So I think it's a 2000/2005 issue and the server I'm deploying to may not be a Report Server. I think we have a 2005 Report Server server but I'll have to get permissions to access it. I definitely don't want to recreate this in an old version of Visual Studio.
I hope, if I can get that done, that it resolves the LBI problem.
-
What you put in the TargetServerURL is NOT the path to the report server. It is the http call you would make to display an ALREADY deployed report. The only part that would go in the TargetServerURL property would be http://gldev.fcb.main/lawson/portal/reportserver, I think. Typically the Report Server URL is just http://servername/reportserver.
Have you talked to one of your DBAs about how to deploy?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question -
We don't really have a fully certified SQL Server DBA. We have someone who takes care of the databases but he's old school and this company is new to Reporting Services. I just went and talked to him and we have several problems. The consultant is building LBI on a production server that is on SS2005 but the Report Server is on a 2000 box. So it sounds like I have some major server issues (loading new software, replicating databases) and a lot of people taking vacation in that department. I'm trying to figure out the issues so I can tell my boss who wanted this deployed long ago.
So I can use your URL for the TargetServerURL but I guess I don't know how to specify where the report deploys unless it just deploys in the folder where the rdl file is. I'm attaching the Properties screen.
Another issue is Lawson. It would be great to get an official position from them on this but their help dept couldn't do so. I referred them to an instructor I had, who knows LBI, and am hoping to get an email from her so I have something official from Lawson for my boss before we get into all these server changes.
-
You can specify folder to deploy to. By default it puts in the Project Name.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply