I am currently having an issue with mySQL. The installation process seemed to have proceeded rather smoothly, but I run into an error whenever I attempt to start or shut down the server. The only way I can seem to start up the server is by reinstalling mySQL, and the only way I can shut it down is through the task manager.
Clicking on the "Stop (start) Server" button in the mySQL workbench gives me the following error:
Unsupported 16 bit application.
The program or feature "\??\C:\watcom-1.3\binw\sc.exe" cannot start or run due to incompatibility with 64 bit versions of Windows. Please contact the software vendor to ask if a 64 bit Windows compatible version is available.
I've tried downloading a 64 bit version of watcom, but this has not solved my problem. I can't seem to figure out exactly what went wrong here, and would appreciate any advice.
I've attached a link below in case you'd like to see the original error message.
http://puu.sh/nkyx4/99d4e59f74.png
Related
The Problem occurs when trying to get data from a remote MySQL Database
I have two Servers with Windows Server 2019. One hosts the MySQL-DB and the other one runs a Software with a plugin. After a reinstall of the server with the software i have the problem that if the plugin tries to read data of the DB it gehts the error
(E:_dev\MySQL.h MySql::getTransferData) Unexpected DB error device or resource busy: device or resource busy
But some other programms and HeidiSQL work just fine witout problems. ALso the Software on the Server with the Database work normally.
After getting in touch with the plugin dev i found out that it shows the path of the plugin devs pc, and it must be a Server Problem. OBDC drivers are installed, also the c++ connectors from MySQL. The problem must be on the Server with the plugin and before the reinstall all worked fine. After a few days try and error i can´t find out what i must have forgotten, that the connection can´t be etablished anymore. Does anyone have an idea?
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 got a community server version of MySQL5.6 for windows7 32 bit.
and also downloaded windows installer for the same windows version.
Everything was prepared correctly.
I saw on a blog giving me a step-by-step manual for installing MySQL 5.6 on winodws7 32bit.
I did the instruction accordingly and it always stops processing in the phrase of starting service. I completely don't know what the problem is.
I googled it for like three hours and got nothing relevant to this problem.
It never processes any further without any kind of alerts, no matter how much I wait.
Please help me out.
My OS
Windows7 Ultimate K 32bit, Service Pack1
TURN OFF WINDOWS FIREWALL COMPLETELY BEFORE INSTALLING
This was one of the only threads I could find on this issue and the current answers did not cut the mustard for me.
MySQL 5.6.21, both x86 and x64, did not want to get past "Starting Server" and would give me the "MySQL install taking longer than expected" message.
I tried all of the registry cleaner, folder deletions, etc to no avail.
I am running Windows 7 x64 and I finally decided to check the event viewer to find this:
0x80070422 turns out to be some unspecified firewall error and boom, it struck me like lightning.
I hope this post helps future visitors!
Have you installed other version of MySQL before？ I have experienced this case ,but I installed MySQL5.5 and uninstalled it. I solved it by clearing regedit and deleting the folder of MySQL in the directory（C:\ProgramData.This directory is hidden by default in Windows.）,then reinstalled it.
Follow this link http://tadeparti.com/pages/?page_id=808.
And do remember to delete everything under the C:\program files\mysql folder, including the odbc stuff if you have.
I am trying to get either NetBeans or Komodo IDE to remotely debug PHP. I have a remote website installed on the development machine which is a Mac running Mountain Lion. Xdebug is installed. The website on the local machine runs normally in a browser.
However, for both NetBeans and Komodo IDE, when single stepping through the code, the attempt to execute mysqli_connect fails. In NetBeans there is the following error message:
Socket Exception occured If you have any Watches, try to remove them and restart debugger. If removing Watches does not help or you
don't have any Watches, please file an issue and provide the exact
steps to reproduce your problem. Please attach the IDE log. Attaching
your project would also be very helpful.
I have seen other people reporting this error message, but no help has been provided.
In Komodo IDE, the failure occurs at the same location, but there is no error information provided at all.
The funny thing in NetBeans is that after some single stepping through the first page of the site, if I then run the code from that point, it executes without failure and the web page is displayed in the browser! This means that the problem only occurs while single stepping.
I have seen something somewhere about a bug in NetBeans. But it seems pretty blatant that NetBeans should not be able to single step through code that tries to connect to mysql. Rather I am thinking it would be some configuration issue on my system.
Komodo IDE has the same failure whether single stepping or running any other way. It just does not get past that point.
However, please keep in mind that just running the site in a browser works fine. So what is missing that prevents the Xdebug single stepping from connecting to mysql?
** Additional information **
I have found two instances of xdebug.so on my system.
-rwxr-xr-x 1 root admin 274508 Oct 6 2011 /opt/local/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so
-rwxr-xr-x 1 root wheel 202672 Sep 20 20:01 /usr/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so
Also, there is an /opt/local/var/db/php5/xdebug.ini which references the xdebug.so in the /opt/local path. The xdebug.so in the /usr/lib path is the one that I thought was in use and which corresponds to instructions as to where it should be installed.
These are apparently two different versions of xdebug.so. Could that be related to my problem?
You need to make sure that you are running one version of Xdebug - and also make sure that this is the latest version (2.2.1 at the moment). If you can still reproduce this issue, please file a bug report at http://bugs.xdebug.org with a short sample script (that contains all the code + data!) and a remote debugging log for a debugging session using that script (see http://xdebug.org/docs/all_settings#remote_log on how to make such a log).
Im trying to start my rails application on ubuntu 11.10, but im hitting the following error:
<PROJECT_PATH>/vendor/cache/ruby/1.8/gems/mysql2-0.2.13/lib/mysql2/mysql2.so: invalid ELF header - <PROJECT_PATH>/vendor/cache/ruby/1.8/gems/mysql2-0.2.13/lib/mysql2/mysql2.so
Im running this in a virtual machine (host: Windows 7, guest: Ubuntu 11.10) if that makes a difference.
Ive pulled out half the hair on my head, any help would be much appreciated.
Im quite embarrassed, but just in case there is someone else out there and faces something like this because of his/her stupidity,
the error was because the folder was being shared between windows and linux, and bundler had been run on windows earlier. When on ubuntu, the earlier installed windows libraries were being picked up, instead of the native linux ones. Cleaning the vendor/cache fixed the issue
Similarly to #zsquare's answer I encountered the same problem when copied a whole deployed project from 32-bit Ubuntu machine to 64-bit.
Unfortunately his answer didn't help, but my solution was even easier: just deleted the whole project and re-deployed it again.