MySQL is not working after Windows 8.1 update - mysql

I have Wamp Server 2.5 installed and it was working fine until my Windows 8.1 update. After the update the Wamp Server has became very slow. I have searched for the solution the whole night and tried every possible solution but no joys :( I re-install wamp, disable IPv6, removed cache, etc. I tried to install Xampp Server then but it has the same issue. I came to know that the issue is with MySQL. Whenever I access my project which requires connection with database it doesn't respond but whenever I access any static page it works normally. Any help would be appreciated!
Thanks in Advance

localhost may be needed to replace with 127.0.0.1 in your program
'Listen 80' need to replace with 'Listen 0.0.0.0:80' in httpd.conf

Related

Problem accessing MySql database on xampp

So, i'm using Xampp 1.7.3 on my windows machine to run a server, never had any issues until now.
Somehow, i just "lost" connection with my database. The server can communicate without any problems, but when i try to access by typing "127.0.0.1/phpmyadmin or localhost/phpmyadmin" i just get a page saying that the Site can't be reached.
Already tried to restart the services and the machine itself, nothing worked.
Haven't tried to reinstall xampp simply because i can't kill the server. I need something to fix that WITHOUT reinstalling xampp

double installation MySQL on Win10

Some time ago I installed XAMPP on my win10 desktop (AMD Phenom, 8gb). The reason for this is that I want to do some wordpress development.
I now want to learn how to work with MySQL and Python. Do I now have to install a new version of MySQL that runs on Win10 or can I use the currently installation that runs under XAMPP? I understand that when using XAMPP I first have to start up the XAMPP server.
I do not want to experiment as I just reinstalled win10 since I got stuck installing so many application on it.
Is it just a matter of starting up XAMPP and then connecting the database with Python? Will Python recognise it?
All help is much appreciated,
Naveen
You can use the current instance and connect with Python. As long as you have the username, password, and using localhost or an IP address all should go find.

How to get MySQL server working after OSX Yosemite upgrade?

After I upgraded my Mac from Mavericks OSX to Yosemite, my local Apache and MySQL server setup did not work anymore. Thanks to Apache localhost/~username/ not working I just got the Apache server working but my Joomla application now indicates it can't access the MySQL database; neither can the Phpmyadmin tool.
How to fix this? I've seen instructions for installing MySQL for Yosemite (https://www.computersnyou.com/3376/setup-apache-php-mysql-macosx-10-10-yosemite/) but I'm not sure whether that's the best way forward as my Joomla application still needs to access the existing MySQL db information? E.g., I don't want to lose my existing saved database info of various web applications....
If you had a working native version of mysql working on Mavericks, the mysql preference pane should be still visible in the preferences, just click on the preference pane and start mysql.
Only problem is that mysql does not auto-start on boot, this can be solved by following these steps: https://stackoverflow.com/a/26465743/580173
Just Start MySQL Server! It worked for me.

MySQL5.6 stuck on the process " attempting to start service "

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.

Problems in Installing Pligg on localhost

I'm facing problem in installing Pligg on localhost(xampp). It seem to install successfully but does not login, as the page freezes. If anyone is familiar with this problem, please suggest me how to fix it. thanks.
Yes this problem is very very common. I similarly have this issue, even to this day. I've tried installation on Windows XP, Vista, and 7, all have failed.
The only way I'm able to work on Pligg is installing directly onto my hosting server. There I don't get any problems, go through the install process and access my site. Check out this quick google search as many of the top links from forums.pligg.com may offer a solution.
Unfortunately though, I haven't found one. To this day I still deploy my Pligg launches onto the server in a sandbox before going live.
I recommend using WAMP Server (Windows) or MAMP (Mac) for testing Pligg locally. I know for certain that both are working fine with the current version of Pligg CMS. I believe that I had some issues when I tried XAMPP years ago, so it may have some default setting that Pligg just doesn't agree with.