We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28042 ☆ A M B ☆
    • 24,524 Posts
    And maybe post your discoveries so others will benefit from your experiences wink

    For example, exactly how did you fix the mode? I for one would like to know.
      Studying MODX in the desert - http://sottwell.com
      Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
      Join the Slack Community - http://modx.org
      • 2759
      • 21 Posts
      Quote from: sottwell at Jun 30, 2006, 01:15 AM

      For example, exactly how did you fix the mode? I for one would like to know.

      UPDATED
      Excellent! Now I can contribute a little.

      OK, it is a fairly straight forward process IF everything goes well.  It didn’t for me, but, I’ll explain what happened and how to fix it.

      This is for a MySQL installation on a Windows XP manchine, but should be relevant to other OS as well.


      Navigate to the following..

      1). Start>Programs>MySQL>MySQL Server (ver#)>MySQL Server Instance Config Wizard
      2). Click NEXT
      3). Select Reconfigure Instance
      4). Select Detailed Configuration
      5). Click NEXT 5 more times till you get to the screen that has the SQL mode option.
      6). Uncheck ENABLE STRICT MODE
      7). Click NEXT 3 more times till you get to the Security Options Page
      8 ). UNCHECK MODIFY SECURITY SETTINGS ( I think this is what screwed me up the first time)
      9). Click NEXT and then EXECUTE
      10). Your Done!

      Now, if something goes wrong, like it did for me, you will get an error when the MySQL Server tries to start back up. Getting MySQL up and running again was surprisingly difficult. I found some help on the MySQL forum, I am modifying what was posted there to what actually worked for me ..

      http://forums.mysql.com/read.php?11,4460,35804#msg-35804

      If you are getting an error message saying that MySql cannot start (Error: 0) then you can take the following steps.

      1). Click on start->All Programs->MySql Server (ver#)->MySql Server Instance Config Wizard.
      2). Click next then click on Remove Instance. Then Execute.
      3). Now uninstall MySql Server using the Add/Remove Software in the windows control panel.
      4). After this has been uninstalled YOU MUST MANUALLY DELETE THE FOLDER WHERE IT WAS INSTALLED. In my case it was installed in: C:\Program Files\MySQL.
      5). Click START>RUN and type in cmd
      6). Type: sc delete mysql ( this makes sure it is really gone, it may report that it doesn’t exist, or it deleted successfully)
      7). RESTART YOUR MACHINE. UPDATE - RESTART NOT NEEDED
      8 ). DISABLE ALL FIREWALLS AND VIRUS PROTECTION APPS
      9). Run the MySQL Installer again ( remember why you were doing all this in the first place, UNCHECK STRICT MODE)
      10). Should be good to go.

      A word of caution. Make sure you back up any existing databases before you do any of this. I simply moved the database FOLDERS in..
      C:\Program Files\MySQL\MySQL Server 5.0\data to another location and then moved them back after I was sure the server was up and running again.

      For some reason, it was very difficult to get the server up and running again after I disabled strict mode.  I kept getting the server start error described above and could not get it to work again till I followed the above steps. Then, all was well and my original issue had been solved.  There are MANY tips to be found on this issue at the link I provided above.  It seems that allot of people have had this issue.

      I tried to do this on a different machine and found that the problems I had were consistent on both machines. This required the additional steps to get the server up and running again. I did find out that you do not have to restart your machine. For some reason, editing your MySQL server configuration to DISABLE STRICT MODE will hose your MySQL Server installation. Fortunately, it is easy to re-install

      Hope this helps someone down the road. I would have never figured it out on my own.

      Thank you
      _________
      Banta
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Thank you! (although if I ever end up having to set up a Windows development environment it will mean I have much bigger problems than configuring MySQL! grin )
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 34017
          • 898 Posts
          Banta,

          Great how-to on Windows MySQL strict problems.

          Chuck
            Chuck the Trukk
            ProWebscape.com :: Nashville-WebDesign.com
            - - - - - - - -
            What are TV's? Here's some info below.
            http://modxcms.com/forums/index.php/topic,21081.msg159009.html#msg1590091
            http://modxcms.com/forums/index.php/topic,14957.msg97008.html#msg97008
            • 24894
            • 1 Posts
            Ty for the instructions, I had the same problem.
            I got the same error when reconfiguring the instance, but I didn’t have to go through all the uninstalling steps - I simply added back the innodb filepath that had been removed during the reconfiguration, and I could restart the instance normally.

            Cheers,

            RE