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

Thomas Reeves thomas_reeves at comcast.net
Tue Jan 22 13:12:04 EST 2008


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/20080122/e13ba536/attachment.html 


More information about the Mono-list mailing list