MySQL Bugs: #30693: package and installer issues

Bug #30693	package and installer issues
Submitted:	29 Aug 2007 13:46	Modified:	17 Jun 2009 16:06
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.1.21, 5.0.45, 6.0.2	OS:	Windows (Vista 32 bit)
Assigned to:	Iggy Galarza	CPU Architecture:	Any
Tags:	qc

Description:
Just installed 5.1.21 32 bit windows binary (FULL not ESSENTIALS)
fresh from the mirror).  Several small issues occurred.

1)
I installed over a running service with no success.  it repeatedly prompted my to close the running service. I was necessary to stop existing running service.  I think it never was before - at least not since the 'new' installer was introduced with 4.1 

2)
Further the installer complained a process (only identified by the process ID) needed to be stopped.  After pressing 'ignore' it installed anyway.  I have noticed from our own program development that for install in Vista it is sometimes necessary to have small SLEEPs in the installer script.  Did you verify install on Vista?

3)
After install (I skipped the configuration wizard as I wanted to use the existing my.ini) service would not start immediately.  It displayed an error message that I needed the full package for the selected options, but it WAS the full and not the 'essentials' package that I had installed. From 'MySQL Administrator' .. service control .. configure service I unchecked 'Named Pipe' options and now service started. There is no .nt binary in the package.  Is that intentional?

a side-remark: I have experenced similar small (but annoying and unproffesional) issues last time I installed software from MySQL AB too.  I think it was the most recent 'GUI tools' package, but I am not sure.

How to repeat:
se above.

Thank you for the report.

Points 1 and 2 verified as described. Point 3 is not repeatable in my environment.

Still I am missing a reply to whether a .nt binary was supposed to be in that package (or to put it otherwise: if NAMED PIPE connection is supported)

Thank you for the feedback.

Named pipes are supported. mysqld-nt has been removed.

selecting support for NAMED PIPES in MySQL Administrator

Attachment: namedpipe.jpg (image/jpeg, text), 143.63 KiB.

I am not sure how I should understand your latest reply!?
Are you telling that 'mysqld.exe' now supports NAMED PIPES?

If this is the case, MySQL Administrator does not seem to know about this!  See attached file 'namedpipe.jpg'.  It want's to start the nonexisting -nt binary!  But maybe this is only because MySQL Administrator was not updated yet to 'fit' recent 5.1.x releases?

If this is the situation I will create a new bug report with MA if required!

Also notice (as I wrote in my first post), that MA seems to 'think' that the ESSENTILAS package is installed.  But it is the FULL package!

Looks like a very poor algoritm being used here!

> Are you telling that 'mysqld.exe' now supports NAMED PIPES?

Yes, but I can not repeat described error with MySQl Administrator.

Issues 1)and 2) repeated themselves with 6.02

3) did not - but this one also comes with a -nt binary

I attempted to recreate the symptoms 1 and 2 described above using 5.1.35 to install over 5.1.29 running service and was unable.   Peter can you confirm that you still see the problem with 5.1.35 and if so, describe the machine's configuration you're testing with including the other versions of MySQL running on the machine and the running MySQL services (if any) with their names?  Thanks very much for your help!