I am taking over a project done under QT5 by someone else. The purpose of this program is to connect to a mySql server (5.5) running locally (on the same machine) and perform operations. It does that by connecting to the ip Address of the machine it is installed on.
One major bug of this program is that, when it is running on a 32bit platform e.g. win7 32 bit, it connects to the mySql database just fine. But when it is running on a 64bit win7 and the mySql database became a 64bit one too, it consistently fail to connect.
We setup several machines running win 7 64 bit OS to make sure that it wasn't anything accidental and sure enough it wasn't, except one of these machines happens to be my work computer and strange enough the program connects just fine. In other words, the program is connecting to the 64bit build of mySql 5.5 server correctly on a win 7 64 bit platform, something it failed consistently on all other machines.
We also noticed that the connection will not take place properly if we run the program and the mySql server on a freshly installed win7 64 bit OS.
Based on that I suspected that it it is because of all the software that I installed on my machine. But so far installing a copy of Qt5 development suit on a freshly configured machine did not solve that problem, which was quite surprising because it is quite reasonable to assume the Qt5 brings with itself files needed to perform certain operation correctly.
Can anyone please shed some light on how to proceed next? I'm quite helpless here and I don't even know the general direction to move on next.
Related
I have seen references to this over the web, but can't seem to configure this correctly. I am using Delphi XE8
I am devloping a Delphi based 64-bit MySQL application for MySQL after installing MySQL 64-bit, which works fine.
However, I need to make design-time changes in the IDE, such as viewing tables, mapping db-aware controls to the fields, etc.
I initially installed the 64bit MySQL, not knowing that the 32-bit Delphi IDE would need the 32-bit MySQL for IDE developing/editing/inspecting.
So I don't think I can have both 32 AND 64 bit MySQL installed on the same machine using the same 3306 port (or maybe I can?).
Does this mean if i want to inspect or work in the 32 bit IDE environment that I can't use the 64 bit MySQL? I have already designed a database in the 64 bit MySQL.....
I saw references to adding the paths to the FDDrivers.ini files, but I can't seem to get this going.
Please any thoughts??
Doug
Delph needs neither a 32bit nor a 64bit MySQL server, it just needs the correct client libraries ("drivers"). This imnplies, that you can keep your 64bit MySQL server on port 3306 and just install the 32bit client libraries. This should install quite fine in parallel to your existing 64bit client libs.
Just to make that clear: A 32bit client can talk to a 64bit server and vice versa. Only the server needs a listening port.
We've got some MS Access 2007 apps here. I'm responsible for one. Normally, it never gives any problems. I haven't heard from the users of this app for over a year, until today. It was written years ago by someone (I don't know who) that is long gone, with little documentation. We're in the process of replacing all of our Windows 7 machines with Windows 10 machines. At first I thought that was the issue. However, one of my colleagues, who is responsible for a number of Access 2007 apps, said that his users are able to use their Access apps with no problem.
Looking back at the user's error, it says simply, "ODBC - call failed". No error number; just that. So, my next thought was maybe there was a missing DSN on the new Windows 10 machine. However, I asked the PC tech to check one of the working Windows 7 machines. He told me there were no DSN's in them. I'm not an Access developer, so I asked my colleague, who does do Access development, what he could discover. He found that the tables are all linked tables from a SQL Server database. Looking at what he was referring to (now that I know where to look) I saw what he meant. The connection to each of those tables uses trusted connections. They're all pointing to the correct SQL database server. That server is there. When I got into SSMS I could easily see data in the tables.
So, what could be causing that error to occur, especially since it doesn't look like it needs a DSN to make a connection to the SQL db?
I presume your Windows 10 is 64-bit.
And probably your Access is 32-bit.
Its important to know!
If my assumptions are correct, you need to use the 32-bit version of ODBC admin to setup the DSN.
The 32-bit version is 'C:\Windows\SysWOW64\odbc32.exe'
The 64-bit version is 'C:\Windows\System32\odbc32.exe'
32-bit Access will look for a DSN setup using the 32-bit version of ODBC admin, even on a 64-bit OS. If you setup the DSN with the 64-bit version of ODBC admin, then a 32-bit Access will not see it!
Go back on the Windows 7 PC, and check exactly how the DSN is setup.
Is it a System, User, or File DSN?
Which drivers are installed for SQL Server?
(There are various different ODBC clients available for SQL Server.)
Replicate this DSN configuration when you create the DSN on Windows 10.
It sounds like you using the 'SQL Server Native Client' on Windows 7,
so make sure to install that on Windows 10.
See: Installing SQL Server Native Client
I'm sure some will say this questions is off topic, but it is truly about programming since I wrote this program and I need to get it working on Windows 10.
I wrote an application in VB.Net and compiled it for "AnyCPU". So it would work in both 32 bit and 64 bit environments. The program communicates with a MySQL database so I load both the 32 bit ODBC drivers and the 64 bit ODBC drivers during the installation. However, one piece of the program uses Crystal Reports for outputting a report. The piece of Crystal I'm using only runs in the 32 bit work space.
The MySQL database installed is 64 bit due to the 64 bit OS.
Everything works harmoniously in Windows_7 (64 bit), but the same configuration does not work in Windows_10 (64 bit). In Windows 10 when the user tries to run the Crystal program to view a report, MySQL throws an error that it can't find the ODBC driver in
"C:\Program Files(x86)\MYSQL\Connector ODBC 5.3\myodbc5a.dll"
Of course the driver is there, but this error is usually due to the wrong bit version of the driver being installed.
The 64 bit version is installed in
"C:\Program Files\MYSQL\Connector ODBC 5.3\myodbc5a.dll"
Is this a Windows 10 issue or something else? How can I get MySQL to use the correct driver location?
I'm not sure if this will help anyone else or not, but basically I went back to ensure that the correct versions of the ODBC drivers were installed in their correct locations. So I uninstalled both versions of the ODBC drivers and tried to reinstall them. In doing this, I saw that the MySQL installer would only let me install one bit version of the driver but not both. My program installs both drivers from the command line in silent mode. But when duplicating my installation method, I noticed that the 32 bit drivers were not being installed correctly when run from the script. But since it installs in silent mode, I never noticed. All of the 32 bit driver dlls were there, including the one shown in the error message, however it was missing 2 dlls that did not get installed properly during the silent installation.
So using the MySQL installer, I tried to install both bit versions of the drivers but as I mentioned above it wouldn't let me. If I installed one version then went back and tried the other version it complained that both versions were already installed. So I had to trick it by installing one version then renaming the folder and then uninstalling it and installing the other version. Once the second version was installed, I went back and renamed the original version's folder back to its original name. That way both bit versions were in thier proper place. However, looking at the installer, it showed that only one version was installed (the one I installed last).
I'm still not sure why my silent installation failed. The error was reminiscent of the error you get when the C++ redistributable needs to be installed, but I tried this and it did not solve the problem. So my immediate problem has been resolved. If I figure out my installation issue, I'll come back and update this answer.
I am forced to finish my Windows project on Mac - Its a Visual Studio C# connected to MySQL database. I've installed it quite nicely on Virtual box and all looks fine (well... except the look of the VB itself, I can't change the screen resolution for some reasons so I use only about 50% of screen).
When I told this to my friend, who is quite passionate about Macs he suggested me Parallels, and even offered his copy. While it looks nicer and in theory is "better" I am not really able to work properly on connection between VS and MySQL: when I'm trying to get through wizard to add data sources I either get error that system cannot connect to ODBC (yes, I've reinstalled connectors) or wizard proceeds, but disappears after pressing any button (i.e. while I'm trying to type "localhost").
have anyone had such problems with Parallels? Or should I try to work on Virtual Box and fix the screen problem (any hints on that would be appreciated).
I have been using Parallels with Visual Studio / SQL Server for over 4 years by now, and it works like a charm! If for whatever reason your virtual machine might get slow, I can recommend you to get some extra memory for your beloved Apple.
Especially when running Windows, Parallels has some fancy integration tools, which gives it some pro's in comparison to VirtualBox.
My current Mac has 8GB of internal memory with an SSD drive. I have assigned 4GB for my virtual machine. I don't notice any slow-downs on OSX, nor on the virtual machine. In fact, my Windows boots faster than one of my native Windows machines!
my SAS scripts worked fine when I was in XP, but now that I've upgraded to Windows 7, my access to MySQL has been impaired. I am sure that MySQL is running. If I open a browser then I can send commands.... The issue is with the SAS software itself. Has anyone else had this issue? Know how to fix it?
Brian, can you provide some more details, such as
The script you're running
SAS log output, including the specific error message(s) you're getting
Whether you're in a client/server situation or have SAS running on your Win7 machine
Is MySQL running on your local machine? Can you look at the open connections via MySQL admin console?
Given what you've described, it's possible you've not only upgraded from XP to Win7 but also from SAS9.1.3 to SAS9.2. Is this correct? If so, has SAS/ACCESS to MySQL been installed correctly? You can find out by submitting
proc setinit;run;