[Mono-list] Replace ByteFX with MySQL Connection/NET

Thomas Reeves thomas_reeves at comcast.net
Wed Jan 23 11:27:27 EST 2008


Thanks to all who responded.  I took J.P.'s suggestion to reset the
MySQL passwords to OLD_PASSWORD format.  Worked like a charm!!

I did more research on this issue and I now believe that the error
message was coming from mono, not specifically xsp server.  In mono,
ByteFX is an entire subsystem, not just a ByteFX DLL file.  I'd love to
work more on this, but I don't have the correct set of skills.

Best Wishes,
Thomas

On Tue, 2008-01-22 at 13:12 -0500, Thomas Reeves wrote:

> Greetings!
> 
> I’m an “old school” developer who can still troubleshoot and do
> research, but I know NOTHING about C# or .NET development.
> 
> I’m working to implement the ePresence video streaming server and
> client.  ePresence uses Mono and xsp server in addition to a host of
> other products.  I get this message from within ePresence:
> 
> ---------------------------------------------------------------------
> 
> 
> 
> Server Error in '/' Application
> 
>                                    
> ______________________________________________________________________
> 
> Client does not support authentication protocol requested by server;
> consider upgrading MySQL client
> 
> Description: Error processing request.
> 
> Error Message: HTTP 500. ByteFX.Data.MySqlClient.MySqlException:
> Client does not support authentication protocol requested by server;
> consider upgrading MySQL client 
> 
> Stack Trace: 
> 
> ByteFX.Data.MySqlClient.MySqlException: Client does not support authentication protocol requested by server; consider upgrading MySQL client
>   at ByteFX.Data.MySqlClient.Driver.ReadPacket () [0x00000] 
>   at ByteFX.Data.MySqlClient.Driver.Authenticate (System.String userid, System.String password, Boolean UseCompression) [0x00000] 
>   at ByteFX.Data.MySqlClient.Driver.Open (ByteFX.Data.MySqlClient.MySqlConnectionString settings) [0x00000] 
>   at ByteFX.Data.MySqlClient.MySqlInternalConnection.Open () [0x00000] 
>   at ByteFX.Data.MySqlClient.MySqlPool.CreateNewPooledConnection () [0x00000] 
>   at ByteFX.Data.MySqlClient.MySqlPool.GetPooledConnection () [0x00000] 
>   at ByteFX.Data.MySqlClient.MySqlPool.GetConnection () [0x00000] 
>   at ByteFX.Data.MySqlClient.MySqlPoolManager.GetConnection (ByteFX.Data.MySqlClient.MySqlConnectionString settings) [0x00000] 
>   at ByteFX.Data.MySqlClient.MySqlConnection.Open () [0x00000] 
>  
> 
> -------------------------------------------------------------------
> 
> Short story, this message is complaining that ByteFX is using an old
> algorithm to encode the password from the web.config file sent to
> MySQL.  Here’s the web.config file:
> 
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> <configuration> 
> <system.web> 
> <customErrors mode='Off'/> 
> <sessionState mode="InProc" cookieless="false" timeout="120"/> 
> </system.web> 
> <appSettings>
> <add key="connString"
> value="Server=localhost;Port=3306;Database=epresence;User
> ID=root;Password=123456789;" /> 
> <add key="connString2"
> value="Server=localhost;Port=3306;Database=epresence;User
> ID=root;Password=123456789;" /> 
> <add key="searchConnString"
> value="Server=localhost;Port=3306;Database=epresence;User
> ID=root;Password=123456789;" />  
> <add key="platform" value="Linux" /> 
> <add key="enforcePubPoints" value="No" /> 
> </appSettings> 
> </configuration>
> 
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 
> 
> I could just force MySQL to use an older password encoding algorithm
> to solve this issue, but I would rather fix the underlying problem.
> My Google research indicates that ByteFX is obsolete in favor of the
> MySQL Connection/NET.  The original error message seems to be coming
> from xsp server.  Do I need to re-compile xsp server?  How do I
> actually implement Connection/NET to replace ByteFX?  If there are
> references that answer this question, I don't mind reading more
> stuff...
> 
> Thanks in advance,
> Thomas Reeves
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20080123/dd1e98aa/attachment.html 


More information about the Mono-list mailing list