I have configured the Jet report with Excel 2013 and trying to connect with data source using Data source setting. I have NAV 2016 installed on my system. After giving Server and Server type, It is showing the correct list of databases available on server. But when I am testing the connection it is showing the below error:
I am new to it. Can anyone guide me with this?
Thanks in advance.
What version of Jet Reports you are installing? Have you tried same thing on latest version of it? As we faced the kind of issue and when we downloaded the latest version and done, it worked.
Related
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.
I have .xlsx file with 27,000 rows. When executing the SSIS package on the server I get the above error. I have tried running the package in 32-bit mode, it did not work. Microsoft does not have a good explanation. I have installed access driver on my machine and on the server.
Assuming that you tried running in 32-bit, and you downloaded Access Database Engine and the issue is not solved
This is caused by a windows security update, this is noticed in the Microsoft Support article, also they provided patches link.
There is a similar question on MSDN about this issue, read the accepted answers:
Unexpected error from external database driver (1)
Side Note: Try opening the Excel and saving it as new Excel workbook to ensure that the excel is not damaged
Remove the Ace Oledb driver 10 and install Ace 2016 version .The Security patch Microsoft provided in October 2017 is causing this issue. Test your SSIS package locally ,if everything is fine install Ace 2016 version on your server .
Here is the download link:
Microsoft Access Database Engine 2016 Redistributable
This issue is caused if the Excel file is in Read-Only mode. Changing the Read-Only mode will fix the issue.
I'm working on a project for my Internship with a collague.
but when he sent me hisasdf(Visual Studio 2015 Enterprise) and I tried to Open his Database, I got the Following Error:
The database cannot be opened because it is version 852. This server supports version 782 and earlier. A downgrade path is not supported.
Could not open new database. CREATE DATABASE is aborted.
An attempt to attach an auto-named database for file {Filename} failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
I updated my Sql Server Data Tools to version 14.0.61021.0 and tried again. Unfortunately this didn't work either. (yes I tried turning it off and on again)
So I was wondering if any of you guys could help me out,
Thanks in Advance!
With kind regards,
Yours Truely
The error is saying that you are trying to attach to a database that is from a newer version of SQL Server than you are using on your machine.
I am thinking that your colleague is using SQL Server 2016 and you are using SQL Server 2014. See the versions here in the "internal version" column.
Regarding solutions, I would start by ensuring that you and you're colleague have the same versions installed. You can also try downloading SQL Server 2016 express edition and opening the database there. You can also try this answer as it is a very similar issue.
If you have any questions about this, provide more details on the steps you've taken and I'll be happy to help.
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'm using Visual Studio 2015 to create a simple SSIS package. The data source is a DB2 database, and I'm using an ODBC driver on my workstation to connect to DB2. The target is SQL Server 2014.
The package runs fine locally, but whenever I run it on the server, I'm having trouble with the ODBC data source. The driver on the server is the exact same one with the exact same name as the one on my workstation.
To get the package into the server, I've imported the dtsx file into SSIS in Stored Packages. I've also tried to deploy the project to the Integration Service Catalog, but I get one of these failures related to the ODBC source when doing so --
The version of ODBC File Source, clsid {xxx} is not compatible with this version of the Data Flow.
The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "ODBC Source;Connector for Open Database Connectivity (ODBC) by Attunity; Attunity Ltd.; All Rights Reserved; http://www.attunity.com
I've also tried using a file based ODBC source instead of a system one with that file in a shared folder on the server. Again, it runs fine in VS but not on the server.
I've looked at the dtsx file (xml based) and I suspect that there is a conflict with the DTSID for the ODBC driver. I'm not sure how that works but it seems like that ID would be unique for each computer and that SSIS is getting is trying to use the workstation's DTSID on the server.
I'm a bit new to SSIS and Visual Studio so I'm hoping I'm assuming there is a straightforward way to run packages developed on a workstation at the server without these hangups. I just can't find anything specific to this problem anywhere.
We do not have VS or SSDT installed on the server.
EDIT: I added a second sentence in the 2nd error message above. It refers a connector provided by Attunity, which is something I don't understand. The ODBC driver installed on the system is from Data Direct. The CLSID returned in the error message is also associated with an Attunity connector in the server's registry.
There are no ODBC drivers from Attunity showing up in either of the ODBC managers, so it's possible that these are somehow part of a default install or were installed when our server used to have SSDT and VS installed directly on it and were never uninstalled. Or, something else?
I have resolved this issue by changing the Deployment Target Version of Integration Services project in VS in my case from SQL Server 2017 to SQL Server 2016 (the target SQL version). Hope this helps. Old quesition, but came up first in google when I tried to solve my problem.
In my case this issue was caused by deploying an SSIS project to a 2016 server using SQL Mgmt Studio 2017. Once I redeployed using SSMS 2016, it resolved the error.
VS or SSDT by default uses 32-bit drivers, so check there is option when you execute for 32-bit. Or install both 32-bit and 64-bit driver and create ODBC with same name.
This is what i do usually for ODBC connections in SSIS -- create connection in both 32-bit and 64-bit.
So create one with
C:\Windows\SysWOW64\odbcad32.exe (32-bit)
and one with
C:\Windows\System32\odbcad32.exe (64-bit).
I had this same problem when executing my package in SQL Server Agent. I resolved it by turning on the Execution Options "Use 32 Bit Runtime" flag in the agent step. Drove me nuts for a few days, hope this helps.
check the version of your solution vs the SQL version of where you are deploying. I had this issue and matching up versions fixed the problem. My solution was 2017 but the SQL box was 2016. I had to change the solution to 2016. cheers!
In my situation I was having this error and I switched to using the 32-bit version. My initial test worked, then I redeployed using a the project I was working with and I got this error again, even though I had switched Execution Options "Use 32 Bit Runtime" flag.
It ended up that I was having problems with my ODBC Data Source. I was using IBM Informix driver and it was having an issue with the chosen locale. I changed it to use the server's specific local and tested its connection. That then worked and my SSIS package worked on the server.
In another situation with this same Informix driver, I had the database name, slightly incorrect and that gave me this same error.