I would appreciate some help or advice on this subject...
So deploying reports to other SSRS sites. Not on the same domain and firewall (but I can remote into the server and work from remote session).
100's of reports (so not reasonable to use the report manager to upload the reports and configure the data sources manually)
RS.EXE works Great!... But I cannot use it because I cannot reach the server from outside the internal network because of firewall restraints.
Downloading and installing DataTools, load the solution and try to deploy mostly had issuses, problems have been incorrect versions of the project / SQL version
The SQL server and VS versions the reports were developed on are 2017.
Targeted SQL Server versions would be 2012 or greater.
Somebody must have had this issue and found a solution. I'm looking for any help or advice. I may have overlook something simple. Thanks.
I tried this GUI tool, which I found in any SSRS forum:
ReportSync
(Works with the SSRS web service asmx)
You can download the source, compile and run. Obviously is not perfect, but is useful to:
Clone a SSRS folder (and all the rdl inside) in the same or different SSRS server
Download entire SSRS reports struct (rld and rds)
Upload entire SSRS reports struct from your local drive
Hope this helps.
Related
Unable to upload rdls on SSRS 2016. Running on Windows Server 2012 R2.
Doesn't upload the report once the upload link is clicked.
Any suggestions?
You could try to:
Create new report using SSRS website and then try to replace it with you rdl file
Deploy report directly from Visual Studio
Check if report doesn't appear hidden (look for View->Show Hidden Items)
If you reports were created for older versions of SQL Server they might need to be upgraded (more details)
I have noticed strange behaviour when upload data sources to SSRS 2016, did not have issues with RDLs but is worth to check it out.
In our case, installing the Chrome browser (standalone) allowed us to use the upload functionality of the SSRS website.
Internet Explorer definitely have some issues, most likely security related.
We have not tested it with the Edge browser yet.
Also, the SSRS in question runs on Server 2016. Direct Visual Studio download is not an option due to tight VPN and firewall security.
RDL files developed with 2012 Data Tools uploaded without a problem. However, as suggested, it might be better to upgrade the project to 2016.
Looks like it was an IE issue. Restoring settings solved it.
None of the other options worked. There is a new download button, that allows you to install a lightweight report builder. You can then open your RDL and publish, etc. and obviously do the other lightweight things like check datasources, etc.
I had the same error and was not able to upload the RDL files as well as I was also not been able to create a data source (Something Went Wrong)on the SSRS 2017, the Web Service URL was also not working. finally, it worked by following the below steps:
Uninstall the SSRS
Install the SSRS Again
Configure the service account,
Web Service URL Use the Recommended setting and apply
Configure a new Database with an SSO account
Web portal URL Use the Recommended setting and apply
Try uploading the .rdl files and Create Datasource.
Note: if you have two separate servers for SQL and SSRS Please make sure the firewall is open for the webserver to connect the SQL server on ports 1433 and 80.
Had this same issue and would get "Something went wrong" error when both uploading rdl files and changing data sources. Fixed it by going to uninstall SSRS from the server, and choosing "Repair". Rebooted, and issue fixed.
I have sql server development studio.I have done a task using it.but now i am asked to use just the sql server 2012 for it.I have googled but have not got satisfactory results.Most of the posts are about ssrs using visual studio.please guide me.
The SSRS development tool in SQL Server 2012 is called SQL Server Data Tool (SSDT).
While installing SQL Server you will get an option to install Reporting Services (This is just the service not Interface for development). To develop SSRS you are required to install SSDT (Visual Studio integrated tool) as report development requires a interface. The Reporting Services can be installed with Native mode and SharePoint mode.
In native mode, You will get 2 things called Report Server and Report Manager, from where you can access your deployed report.
For your knowledge: SSRS report file (.rdl) is nothing but a XML file. If you are expert in writing XML code you can create your RDL file (This is not practically done - not easy).
Search about Report Builder also - It is also client based tool to develop and modify existing SSRS Report.
I'm currently working on an application that runs a small SQLite DB, but I want to use .RDLC for reporting.
I generate the reports over my view models, the idea was for them to be decoupled from the DB, but now I run into this snag that I have to install SQL Server in order to use the reporting framework.
I wouldn't want to require my clients to install SQL Server on their machines just to be able to generate reports. They won't be happy about that. And I don't want to redesign my reporting component either(I have something from a previous project which used SQL Server and that works very well. I want to reuse it)
Is there a way to deploy the Reporting framework on the target machine without SQL Server?
Ideally I would like to just just copy the needed libraries in my application's installation folder, under OTS, but I don't really know which libraries to copy and what I can leave out or even if it's going to work this way.
Any insight would be helpful.
No. SSRS will only work on a machine with SQL Server installed on it.
Same with SSAS and SSIS.
So what we ended up doing is installing two nuget packages.
Microsoft.ReportViewer.Windows and Microsoft.SqlServer.Types
This will allow us to use the reporting framework without deploying SQL server on our target machines.
I am attempting to open a Crystal Reports 8.5 document, and when I try to set the database to the Production data server, i get the error "Pdssql.dll cannot be found". Googling, this is a common problem, but none of the fixes I tried seem to work.
This is a new computer. I do have SQL Server 2008 client tools installed, but I believe previously I had Sql Server 2005 client tools.
I attempted to install the SQL Server 2005 client tools, but that didn't go through due to me having 2008 installed. I require 2008 to do my job now.
Everything I search for says this is a 16bit driver, and I need to install the 2005 client tools. Unfortunately this cannot be done due to me having 2008. is there some sort of work-around I can do?
Thanks
Here is what I had to do if it helps--I had to retire a windows 2000 server so I needed to move a webapp which required Crystal Reports 8.5 onto a new server.
Since I couldn't locate the original installation runtimes (I don't know who developed or even uses this particular webapp) I had to copy all the crystal reports files over to the new server myself and register the required dlls. The crystal reports designer was working except it couldn't seem to make any connection to any of the database servers.
Then I found a folder that I had missed under C:\winnt\crystal which was filled with files such as p2ssql.dll p2lodbc.dll etc... turns out that P2SSQL.DLL is actually Pdssql.dll!
By putting all these dlls into a folder within my system32 path all my database connections within crystal reports were working again!
Did you try creating a DSN in the ODBC administrator? You would have to update the report to use the DSN instead of a "direct" SQL connection, but it should work. ODBC should do it's job and do all the SQL translation (talking to 2008 and just return generic data to the report).
I do not believe a direct connection from Crystal 8.5 to SQL 2008 would be possible though, because the technologies are almost 10 years apart.
Try to Download "ntwdblib.dll" and put in
Windows\sysytem32
if the system 32 bit or in
Windows \syswow64
if the system 64 bits
Scenario:
Production servers are running SQL Server 2008 in the domain myDomain.com
Dev/test/stage servers are running SQL Server 2008 in the domain dev-myDomain.com
Actual dev work done on local running SQL Server 2008 source controlled using SourceSafe
First of all, does this setup/environment make sense? And, what are some good ways of deploying projects including SSAS, SSIS, SSRS from local to the dev servers and finally into live?
Is including the output (compiled) files in SourceSafe and deploying from there good practice? If it is any ideas?
Or, is going straight from Visual Studio without having the output in SoureSafe better?
Thanks.
We rely heavily on the use of variables for the items we want to change in differnt configurations and then config files (one each for Dev, QA, Staging, Prod). All SSIS packages and config files are in Source Save.
Visual Studio has configurations you can set up in order to deploy objects to different servers.
You can also use utilities to copy some around:
DTUTIL for SSIS - delivered with SSIS
RSScripter for SSRS - third party free tool, which is very useful
I would think you would use the deploy tool in Visual Studio for SSAS, as it needs to populate the model. I am just getting started with SSAS, so there may be other tools.