MySQL Server (5.6), Installer, Connector or WorkBench Wont't Install (Windows 7 64-bit)

If you’re having trouble installing MySQL on Windows 7 (Any other platform will probably be the same) then I’d recommend the following process.  Don’t skip the first steps that describe the uninstall and removal of the previous install as this seems to clear up most issues.   

Caution: deleting the data files will delete any data previously entered into MySQL.

1.  Remove previous MySQL installs (and remnants)

a.  Stop the MySQL service ( Start | Control Panel | System & Security | Administrative Tools | Services)

b.  Remove All programs with MySQL in the name from Windows Add or Remove Programs (Start | Control Panel | Uninstall a Program)

c.  Delete the MySQL data directory (It is a hidden folder) from  (You will lose any stored data so you may wish to make a copy) :
       c:\Users\{Your Username}\AppData\Local\MySQL

       c:\Users\{Your Username}\AppData\LocalLow\MySQL

       c:\Users\{Your Username}\AppData\Roaming\MySQL

d.  Delete the MySQL folders from

        c:\program files\MySQL\

        c:\program files(x86)\MySQL\

        c:\program data\MySQL\                --(this is also a hidden folder)

————–

That’s it for the removal and clean up.  Now, we’ll begin the install.

2.a  Go to the MySQL Website and install the latest MySQL Installer.  It should come in the form of an MSI installer and comes for a 32 bit machine(x86) but will run on a 64-bit machine.

b.  Launch the installer which can be found in your Downloads folder.  Follow the Wizard through to the end and make sure you make note of the password you set for your new installation of the server in case you forget it 

TROUBLESHOOTING

What if it didn’t work?

1.  Check the service from the control panel.  Is it running?  If so, try to log into MySQL.  I’ve seen instances where an error was received, but it completed successfully.  If it’s not running, try to start it and please post the complete error message.

2.  Check the error log.  It’s in C:\Users\AppData\MySQL\MySQL Server 5.6\data   It has an .err extension and you should be able to open it with notepad.  Ignore any errors about the innodb plugin not loading.  It’s a symptom, not the problem.  Look for an error about missing data files or a mismatch in file sizes.

3.  1045 error?  It should indicate Password: No or Password:yes.  If “yes”, it’s not a port issue, not a firewall issue — it’s a password issue.  It’s usually caused by not deleting out the data files from an old install.  The password is kept in the data directory and it’s likely that the password you entered during the previous install doesn’t match what you’re entering now.  You can either re-install after deleting all the files or try to reset your root password.  (resetting root password: http://dev.mysql.com/doc/refman/5.1/en/resetting-permissions.html )

4.  Still stuck?   Email Oracle's Support Team

Error parsing: xxx failed(2,0): Unable to read 512 bytes from 65536 in stream of length 65421

Error parsing: xxx failed(2,0): Unable to read 512 bytes from 65536 in stream of length 65421.  

The error that you are receiving is because of length of the file so for each error message you are likely to have different error numbers.

By default there is a limit to how much data that Nutch will parse and should your file be larger than that limit then Nutch will either truncate your index file or just give up. 


SOLUTION:

To take that limit away you need to set the content limit to -1 - This lets Nutch know that you have no limit on the length of file and it will continually attempt to parse it until it is completed.  This can mean that there are performance issues when it comes to large files.

If you are using a web crawler:

Add this code to the nutch-site.xml

<property> 
<name>http.content.limit</name> 
<value>-1</value> 
<description>The length limit for downloaded content, in bytes. 
             If this value is nonnegative (>=0), content longer than it 
will be 
             truncated;otherwise, no truncation at all. 
</description> 
</property>

If you are using a filesystem crawler then:

Add this code to the nutch-site.xml

<property> 
<name>file.content.limit</name> 
<value>-1</value> 
<description>The length limit for downloaded content, in bytes. 
             If this value is nonnegative (>=0), content longer than it 
will be 
             truncated;otherwise, no truncation at all. 
</description> 
</property>

XSLT Error For Solr - HTTP Status 500 - {msg=getTransformer fails in getContentType...

It is common to apply an XSLT stylesheet to an xml file to give it a cleaner look and Solr is no different coming with 4 pre-written xslt files for you to choose from.  

The error message XSLT Error For Solr - HTTP Status 500 - {msg=getTransformer fails in getContentType... is a common one and in most cases is easily fixed.  There are a few reasons that the error message appears:

1. You have not specified a stylesheet to use
          e.g http://localhost:8080/solr/select?q=*&wt=xslt
   Make sure you have specified a stylesheet and that the stylesheet you specified actually exists
          e.g http://localhost:8080/solr/select?q=*&wt=xslt&tr=example.xsl
   
2. A common mistake is to think that a stylesheet has a .xslt file extension - THEY DONT! The file extension is .xsl so be sure when you save your file and when you specify it in your query that you use .xsl
   
3. There are errors in you XSL file - Be careful if you are working in an environment that does not do syntax checking (notepad) - It is easy to forget to close a tag or make a spelling mistake.

Stack Trace:

 {msg=getTransformer fails in getContentType,trace=java.lang.RuntimeException: getTransformer fails in getContentType at org.apache.solr.response.XSLTResponseWriter.getContentType(XSLTResponseWriter.java:74) at org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.java:623) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:372) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:155) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1852) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: 'tr' request parameter is required to use the XSLTResponseWriter at org.apache.solr.response.XSLTResponseWriter.getTransformer(XSLTResponseWriter.java:1