We have a Windows Server 2003 based server.
We had MySQL installed but yesterday uninstalled it to try to clear the logs (which were taking up approx 1.8GB).
When trying to reinstall we are now getting an error.
The MySQL service, once started (manually), will stop itself, with no entries in the event viewer to state why.
The MySQL server instance configurator will also not complete, with the above error message.
When the service is started (manually), for the 20 seconds or so that it will stay started, when trying to connect to MySQL from the command prompt, we get the error 'Error Nr. 2003 - Can't connect to MySQL server on 'localhost' (10061)'
This is not a job for a novice. I myself am the sysadmin, I have experience using MySQL but cannot figure out this issue and do not have the time to troubleshoot this.
There are no software firewalls running on the system and you will get RDP access to the server.
As previously stated, this issue has only been ocurring since the MySQL server was uninstalled and then reinstalled.
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
* * *This broadcast message was sent to all bidders on Wednesday Dec 10, 2008 7:40:45 AM:
To all bidders: I have managed to resolve this myself. Seems that there was a folder in C:\Documents and Settings\All Users\Application Data\MySQL called 'Data' that was still harbouring all the previous tables. Deleting this has resolved the issue. Thanks for your time, Nathan
## Platform
Windows Server 2003
MySQL Server 5.1