Bug #66630 MySQL proxy - 0-8-3 does not work in Windows 7 (64 bit)
Submitted: 31 Aug 2012 6:39 Modified: 5 Nov 2012 8:49
Reporter: Mahesh Patil Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Proxy Severity:S1 (Critical)
Version:0.8.3 OS:Windows (Windows 7 64 bit)
Assigned to: CPU Architecture:Any
Tags: mysql-proxy

[31 Aug 2012 6:39] Mahesh Patil
Description:
MySQL proxy for windows v0-8-3 (latest release) works fine in Windows XP however same build does not work for Windows 7 64 bit

D:\mysql-proxy\mysql-proxy-0.8.3-win32-x86\bin>mysql-proxy.exe --proxy-backend-a
ddresses=<ip>:<port> --proxy-address=<ip>:<port> 

The application has failed to start because its side-by-side configuration is in
correct. Please see the application event log or use the command-line sxstrace.e
xe tool for more detail.

Event log says:

- System 

  - Provider 

   [ Name]  SideBySide 
 
  - EventID 33 

   [ Qualifiers]  49409 
 
   Level 2 
 
   Task 0 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2012-08-31T06:37:55.000000000Z 
 
   EventRecordID 2206593 
 
   Channel Application 
 
   Computer MAHESH-PC 
 
   Security 
 

- EventData 
   Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.6161" 
        
   D:\mysql-proxy\mysql-proxy-0.8.3-win32-x86\bin\mysql-proxy.exe 
    

How to repeat:
Start a proxy in Windows 7 64 bit

Suggested fix:
Starting a proxy program should not give such a error, It should work properly.
[3 Sep 2012 7:19] Mahesh Patil
Any updates on this issue?
[16 Sep 2012 3:23] MySQL Verification Team
Thank you for the bug report.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

d:\dbs>mysql-proxy --version
mysql-proxy 0.8.3
  chassis: mysql-proxy 0.8.3
  glib2: 2.16.6
  libevent: 1.4.12-stable
  LUA: Lua 5.1.2
    package.path: D:\proxy\lib\mysql-proxy\lua\?.lua
    package.cpath: D:\proxy\bin\lua-?.dll
-- modules
  proxy: 0.8.3

d:\dbs>mysql-proxy --proxy-backend-addresses=localhost:3541 --proxy-address=localhost:3580
2012-09-16 00:19:44: (critical) plugin proxy 0.8.3 started
[17 Sep 2012 7:37] Mahesh Patil
I can see status as `Can't repeat` ,
Can't it should be verified ? 

Or you are expecting some input from my side?
[1 Oct 2012 14:32] MySQL Verification Team
Do you meant the below message is wrong?

2012-09-16 00:19:44: (critical) plugin proxy 0.8.3 started

Thanks.
[2 Oct 2012 6:19] MySQL Verification Team
it works fine on my 64-bit windows 7 machine:

H:\ade\mysql_archives\proxy\mysql-proxy-0.8.3-win32-x86\bin>mysql-proxy --proxy-backend-addresses=localhost:3541 --proxy-address=localhost:3306
2012-10-02 08:18:03: (critical) plugin proxy 0.8.3 started
[4 Oct 2012 14:13] Mahesh Patil
D:\mysql-proxy\mysql-proxy-0.8.3-win32-x86\bin>mysql-proxy.exe --version

The application has failed to start because its side-by-side configuration is in
correct. Please see the application event log or use the command-line sxstrace.e
xe tool for more detail.

Still getting this error :-(
[4 Oct 2012 15:49] Jan Kneschke
Did you install the 

  "Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update"

as 

  http://dev.mysql.com/doc/refman/5.1/en/mysql-proxy-install-binary.html 

says?
[5 Oct 2012 6:48] Mahesh Patil
It's already installed:
Microsoft Visual C++ 2008 Redistributable - x86.9.0.30729.6161
[5 Oct 2012 6:53] Jan Kneschke
Your eventlog still shows the same side-by-side error complaining about:
     Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.6161"

?
[5 Oct 2012 7:38] Mahesh Patil
Yes event log still shows the same entry as :

 Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.6161" D:\mysql-proxy\mysql-proxy-0.8.3-win32-x86\bin\mysql-proxy.exe
[5 Oct 2012 8:49] Jan Kneschke
As windows thinks you don't have it installed, install the msvcrt package that is linked again.
[6 Nov 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".