Description: Following an update to Windows 10 version 1709 on my Lenovo desktop computer I have been unable to access the table data in any of my LO databases (.odb files). LO loads the .odb successfully but selecting the "Tables" symbol in the left hand column brings up the error message: 'The connection to the data source "addresses_new" could not be established. The connection could not be created. May be the necessary data provider is not installed'. The lists of queries, forms, and reports are shown correctly but attempting to open any of them brings up the same error message. I was using LibreOffice v5.4.2.2 (x64) at the time the error first appeared so tried updating to LO v5.4.3, then v5.3.7 but with the same result each time. I also tried an earlier version of the database file and also an archived version but with the same result for each. I have also tried re-installing Java jre1.8.0_151, then upgrading to jre-9.0.1 & jdk-9.0.1 but the same error message appears in LO Base. Steps to Reproduce: 1.Open a .odb file using LibreOffice 2.Select the 'Tables' symbol in the left hand column 3. Actual Results: error message: 'The connection to the data source "addresses_new" could not be established. The connection could not be created. May be the necessary data provider is not installed' Expected Results: Show a list of the tables comprising the database Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
@Bob : Unfortunately, we don't have enough information to go on. What bit version of LibreOffice were you using before you upgraded to 5422 where you first encountered the problem ? If the previous version of LibreOffice that you were using, and which presumably worked, was 32bit, then you would have had a 32bit JRE/JDK environment. As you mention that the 5422 was 64bit, it could be that although you have a JDK/JRE installed, they might not be recogized by LO5422 (this seems likely given the error message). Also note that Oracle 64bit JDK 9.0.1 doesn't seem to come with a JRE and that you might have to download and install this separately. If you upgraded to JRE9.0.1 from JRE8.0.151 via the automatic update mechanism, then it could be that this isn't recognized by LO. I don't really know what to suggest other than that.
Your report sounds like a DUPLICATE of bug 114361
On menu tools/options, go to LibreOffice Base, then databases. In addition of by default "Bibliography", you should have another entry "addresses_new". If it's not the case, you must add this source with the exact name and indicate the location of the file. Now I don't know why you should lose your registered databases when updating. Is it expected or not, I'd say no but not sure.
Setting to NEEDINFO until Bob gets back with an update on the information and response to the suggestions in comment 3
(In reply to Alex Thurgood from comment #1) > @Bob : Unfortunately, we don't have enough information to go on. > > What bit version of LibreOffice were you using before you upgraded to 5422 > where you first encountered the problem ? If the previous version of > LibreOffice that you were using, and which presumably worked, was 32bit, > then you would have had a 32bit JRE/JDK environment. As you mention that the > 5422 was 64bit, it could be that although you have a JDK/JRE installed, they > might not be recogized by LO5422 (this seems likely given the error message). > > Also note that Oracle 64bit JDK 9.0.1 doesn't seem to come with a JRE and > that you might have to download and install this separately. If you upgraded > to JRE9.0.1 from JRE8.0.151 via the automatic update mechanism, then it > could be that this isn't recognized by LO. > > I don't really know what to suggest other than that. Alex In response to your question What bit version of LibreOffice were you using before you upgraded to 5422 where you first encountered the problem ? I had been using LibreOffice 5.4.2.2 Win X64 quite successfully since I installed it on 23/10/2017. Then on 11/12/2017 I installed the Windows 10 version 1709 update, immediately after which I encountered the problem loading any of my LibreOffice .odb files (still using version 5.4.2.2 Win X64). I then upgraded to LO v5.4.3 Win X64, but with the same result. BoB
(In reply to Alex Thurgood from comment #2) > Your report sounds like a DUPLICATE of bug 114361 Alex I agree that my problem is very similar to bug 114361, with the exception that in my case the problem appeared without me changing the version of LibreOffice (or JRE for that matter). I have followed very similar paths to Chris Grove with similar results. Bob Evans
(In reply to Julien Nabet from comment #3) > On menu tools/options, go to LibreOffice Base, then databases. > > In addition of by default "Bibliography", you should have another entry > "addresses_new". > If it's not the case, you must add this source with the exact name and > indicate the location of the file. > > Now I don't know why you should lose your registered databases when updating. > Is it expected or not, I'd say no but not sure. Julien In tools/options/LibreOffice Base/databases I already have an entry for "addresses_new" and its location is registered correctly. Bob
Thank you for your feedback. Sorry I can't help here.
(In reply to Bob Evans from comment #6) > I have followed very similar paths to Chris Grove with similar results. So when you go to Options > LibreOffice > Advanced there is no Java available?
Yes there is a java available at Options > LibreOffice > Advanced It shows as "Oracle Corporation v9.0.1" Bob Evans
(In reply to Bob Evans from comment #10) > Yes there is a java available at > > Options > LibreOffice > Advanced > > It shows as "Oracle Corporation v9.0.1" Ok, then this is not a duplicate of bug 114361.
Re reading this tracker again, it gave me an idea. Could you: - remove all Java versions - remove remaining Java folders - clean registry (eg with a free tool like Glary utilities) - reboot machine - install a Java 64 bits - rename your LO profile - launch LO 64 bits which, since there's no LO profile, will be forced to detect the right and only Java version Indeed, managing different Java versions on a machine may be a bit tricky.
My suggestion : - download and install Oracle SE JDK 9.0.1 for Win64bit - download and install Oracle SE JRE 9.0.1 for Win64bit
it seems jdk9 detection has just been added on master (see https://cgit.freedesktop.org/libreoffice/core/commit/?id=7df57f6993cab4ba0f1fccce92394c4dfe46f067) so for the test, I'd stick with jdk8 for the moment.
(In reply to Julien Nabet from comment #12) > Re reading this tracker again, it gave me an idea. > > Could you: > - remove all Java versions > - remove remaining Java folders > - clean registry (eg with a free tool like Glary utilities) > - reboot machine > - install a Java 64 bits > - rename your LO profile > - launch LO 64 bits which, since there's no LO profile, will be forced to > detect the right and only Java version > > Indeed, managing different Java versions on a machine may be a bit tricky. Sorry for the delay. Followed your instructions, installing Java 64 v"1.8.0_161" (because that was the one recommended by Oracle) but the fault still exists. Only difference is that the error pane is hardly legible, the lettering being very fuzzy. Bob Evans
@Bob : can you provide a test ODB that doesn't work so that we can attempt to reproduce ? If your report is similar to bug 114361, it transpired that the problem was because the ODB files referenced old MDB Access files, which unfortunately are reported to no longer be accessible using 64bit LibreOffice. The only workaround available currently to that problem is to switch back to a 32bit version of LibreOffice.
Created attachment 139947 [details] LO database file created using 32 bit version of S/W running on 64 bit machine
Well done Alex - I un-installed LO 5.4.2.2 x64, installed 5.4.2.2 (32-bit version)and I am now able to access my databases again. This is a great relief as although I had backup versions of them all they too were in .odb format. I will now make backups as calc files so if a similar problem arises I will still be able to access the data via calc. Is there any way of converting the 32-bit odb files so they are accessible using the 64-bit LO, or should I now stick with the 32-bit LO versions? I have attached my 'addresses_new.odb' file in case it is of any use to in resolving the problem. My thanks to all who have responded to this error report with attempts to find the cause of the problem. Regards - Bob
(In reply to Bob Evans from comment #18) > Well done Alex - I un-installed LO 5.4.2.2 x64, installed 5.4.2.2 (32-bit > version)and I am now able to access my databases again. This is a great > relief as although I had backup versions of them all they too were in .odb > format. I will now make backups as calc files so if a similar problem arises > I will still be able to access the data via calc. Is there any way of > converting the 32-bit odb files so they are accessible using the 64-bit LO, > or should I now stick with the 32-bit LO versions? The file you attached gives the right hint: It isn't an internal HSQLDB-database. You have created a *.odb-file to connect to the file "palmout2.mdb". Problem: *.mdb-files are 32bit MS-Access-database-files. See this one: https://bugs.documentfoundation.org/show_bug.cgi?id=97395 You could try to connect to the *.mdb-file using ucanaccess and JDBC. Or you could copy and paste the data of your *.mdb-file to a internal HSQLDB-database-file.
*** This bug has been marked as a duplicate of bug 97395 ***