Requirements are iReport 5.6, Java 6, and MS SQL Server 2012 using jtds-1.3.1.jar.
I cannot make "MS SQLServer (net.sourceforge.jtds.jdbc.Driver)" JDBC Driver to not be red. I had that file everywhere trying to find the right place for it (because I've read many opinions on where it should be). I've also read that I need to add an entry to the /Tools/Options/Classpath/ area to point to the file. This didn't help either.
Where must I place the file and how must the CLASSPATH be set so that iReport can find the .jar file for SQL Server?
The real issue - I cannot use MS SQL Server (it's red here - needs to be black like the MySQL entry below it):
Where the jar file is located (I realize it shouldn't be in all of these places - I did test them one at a time):
JAVA_HOME (cross reference with where the jar file is located):
Added Classpath (also cross reference with where the jar file is located):
It seems like it should be placed here, based on the other contents of the directory - C:\Program Files (x86)\Jaspersoft\iReport-5.6.0\ide10\modules\ext:
After installing Jasper Reports 6.3, I was able to connect to the Server/DB immediately.
Seems iReport 5.6 and Windows 10 do not play well together.
After much trial and error, I had success on Mac OS using the following:
iReports 5.6.0
JDK 1.6 Official Mac version
JTDS 1.2 (NOT 1.3.1 as it does not work due to requiring a later JDK)
I had issues getting iReports running on JDK 1.8 so had to downgrade to JDK 1.6.
I hope this helps some poor soul!
Please remember , iReport 5.6 is working with jre 7 and if you want to connect with MS SQL, you need driver sqljdbc41 (which is compatible with jre 7 in classpath)
Related
I've reformatted my machine around 3 times. I'm on windows 10 and I've selected the erase all apps and files option and I'm still not able to install sql server express 2016. I'm presented with this error when trying to install.
‘Microsoft.VC80.MFC,version=”8.0.50727.4053″,publicKeyToken=”1fc8b3b9a1e18e3b”,processorArchitecture=”x86″,type=”win32″‘. Please refer to Help and Support for more information. HRESULT: 0x800736CC.
I've tried many many things. I've reformatted, I've tried running the file as admin, tried other versions such as stand edition 2012, tried to install the files while deleting 2010 c++ distribution. I've ran .net repair tool and nothing as well.
The problem stemmed when I manually uninstalled .net 4.5.1 framework using add/remove programs. I think my system files or registry is corrupted.
I think the error says, you have a 32 bit machine(processorArchitecture=”x86″) and you are trying to install 64 bit app ,which is not possible
further there is no 32 bit version of SQLSERVER from SQL2016 onwards
Some of you may have noticed that Microsoft recently released SQL Server 2016 CTP 2.4. There is one major change that I am very happy about – x86, or the 32-bit version, is no longer included. SQL Server 2016 is now 64-bit only
you can try downloading SQL2014 express version which comes in both versions..here is a link to download :Download SQL Server Express
I am trying to do dacpac deployment using SQLPackage on Linux.
My environment:
Server : Ubuntu Linux version 16.04
SQL Server 2017 latest release candidate version RC1.
SQL Server installation is successful and I am able to create tables on SQL Server database on Ubuntu. Now I am trying to implement dacpac deployment on Linux. As per this documentation
https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-export-import-with-sqlpackage
SQLPackage executable has to be at /opt/mssql/bin. But it is not. Any idea how to install SQLPackage on linux?
When I check the older version which is CTP 2.1 I have that SqlPackage executable. Is that missed in RC 1?
-Regarding temporary removal of sqlpackage from SQL Server 2017 package-
The goal is to offer customers the best CLI experience on Linux, macOS and Windows with a multi-os version of sqlpackage that uses DACFx APIs based on .NET Core.
As a stop-gap towards this goal, we offered an early preview version of the Windows-based sqlpackage in SQL2017 CTPs on Linux to seek customer feedback. We have removed this preview version of sqlpackage from SQL2017 RC1.
Work on the multi-os version of sqlpackage is in progress but I cannot share a release date at this time. Until then, you can use one or more of the alternatives below to import a dataset on each new run of your image:
1) restore an existing .bak file into the new image using the sqlcmd CLI tool.https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools
2) run sqlpackage on a Windows machine to work with SQL 2017 running in the new image.
3) generate a script with CREATE + INSERT statements for your database or specific tables. You can use SSMS’s Generate Script wizard on Windows or the new Python-based mssql-scripter CLI (public preview) to generate the script and check it into source control if you wish. Then, you can use the sqlcmd CLI tool to execute the script in your new image. For mssql-scripter installation instruction, please see README.md inhttps://github.com/Microsoft/sql-xplat-cli
Please send me an email at sanagama#microsoft.com if you have more questions or feedback and we'll be happy to help.
As mentioned by #Lin Leng-MSFT, sqlpackage has been removed from the installation package as of RC1. That said "SqlPackage can still be run against Linux remotely from Windows."
Following the instructions from WSO2 IS on setting it up with Microsoft SQL Server (https://docs.wso2.com/display/ML111/Setting+up+Microsoft+SQL), I continue to get the following error when running WSO2 IS:
ERROR (com.microsoft.sqlserver.jdbc.SQLServerConnection) - Java
Runtime Environment (JRE) version 1.7 is not supported by this driver.
Use the sqljdbc4.jar class library, which provides support for JDBC
4.0. ERROR (org.wso2.carbon.user.core.util.DatabaseUtil) - Database Error - Java Runtime Environment (JRE) version 1.7 is not
supported by this driver. Use the sqljdbc4.jar class library, which
provides support for JDBC 4.0.
I made sure that there were no extra sqljdbc libraries in the paths (to rule out ambiguity). I followed the instructions exactly, but did note that they referenced SQL Server 2005 (yikes!).
I am working on a Windows 7 machine, JRE 8, JDK 1.7, SQL Server 2012/2014, and WSO2 IS 5.1.0.
Any help would be greatly appreciated.
I assume you are using the JDK 1.7, so according to the documentation from microsoft you need to have Sqljdbc41.jar. Can you check you have the correct version in the lib folder?
Sqljdbc41.jar requires a JRE of 7 and supports the JDBC 4.1 API
Also make sure that the dropins folder don't have any mssql libs before restarting the server (Jars from lib are copied to dropins at the startup, so there is a chance you have mssql jars copied from an earlier startup).
Also note that WSO2 IS has a separate page for setting up databases. Please follow that doc instead which contains the documentation specific to IS.
I have been trying without any success to get the latest version of Oracle SQL Developer (4.0.2) to connect to Microsoft SQL server using Windows authentication. I have downloaded and copied the ntmlauth.dll (and also JtdsXA.dll) file from jtds-1.3.1-dist to every location I can think of that developer would be looking for it but when I try and set up a new connection via the SQLServer tab clicking on the "Use Windows Authentication" option, all I get is the message "Status: Failure -I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property." I can however connect to the database using Toad for SQL Server or SSMS without any problems, but would prefer if possible to use SQL Developer.
Just copy ..\jtds-1.3.1-dist\x64\SSO\ntlmauth.dll to -> ..\sqldeveloper\jdk\jre\bin folder for x64 systems. Copy-paste similar folder contents for x86 systems as well.
I had the exact same problem. I eventually got it to work by placing the ntlmauth.dll in the jdk\jre\bin folder under the sql-developer directory itself. For some reason sql-developer ships with its own jdk, which I found by browsing around. I spent hours trying to figure out why the placement of the aforementioned DLL in the various system level jre directories (i.e. C:\Program Files\Java\jre7\bin) didn't work.
If anyone here knows why placement of ntlmauth.dll in the sql-developer\jdk\jre\bin folder worked while placement in the system level jre folders did not I would be interested.
My OS = Windows 2007 64-bit
jtds = jtds-1.2.7
The reason is pretty simple; SQLDEVELOPER doesn't know about the system level jre that was installed. Oracle bundles SQLDEVELOPER with and without JAVA. If you downloaded the one without java then when you first start the app you will be prompted for the location of the java_home. If you install the SQLDEVELOPER version that already has java installed then it just works -- no prompt. In your case, you installed the version with java already packaged with the app.
So the root of the question then is the system level jre is not used by SQLDEVELOPER (in your particular installation) so the ntlmauth.dll that you placed in that directory is never used.
After adding jTDS drivers (jtds-1.3.1) to Oracle SQL Developer (Tools->Preferences->Database->Third Party JDBC Drivers), I located the SQL Developer's ide.conf file and added the following lines:
#jTDS
Add64VMOption -Djava.library.path=../../drivers/jtds-1.3.1-dist/x64/SSO
Add32VMOption -Djava.library.path=../../drivers/jtds-1.3.1-dist/x86/SSO
This adds to JVM Library Path the location of ntlmauth.dll library
I am facing problems while installaing db2 client in my system. Initially I got an error: Cannot find XML_0017.cab.
Then I cancelled the installation, selected the custom installation option and removed all the options related to XML (i.e. XML Extender and the XML Extender Samples) and tried to install. Now i can see that WEBD0000.CAB file is missing.
I am not able to understand how to proceed with the installation. Am I missing something?
DB2 9.1 was not supported on Windows 7 at all. IBM ended support of DB2 9.1 in April, 2012.
I would suggest you download a more recent version of the Data Server client from IBM's website.
CAB file, I assume this is a windows installation.
My DB2 on windows is a little rusty but if this is a client install you should not have to install "XML anything" unless you installing some kind of addon for Visual Studio.
What file did you download?
Can you include a file name, url link etc.?