Re: Mysql .net conn...
 
Notifications
Clear all

Re: Mysql .net connector 8.0.33

7 Posts
3 Users
0 Reactions
345 Views
Posts: 79
Topic starter
(@hemens)
Estimable Member
Joined: 8 years ago

Hi,

I have recently adding Mysql 8.0 and facing issue with .NET connector 8.0.33 when adding the db

faced similar issue with old mysql 5.6 as well but both works when downgraded to  .NET connector 8.0.29

Any solution or work around for this !!

 

Thanks

Topic Tags
6 Replies
Posts: 79
Topic starter
(@hemens)
Estimable Member
Joined: 8 years ago

Is anyone facing similar issue ?

DB error while upgrading .NET connected to latest version ! 

but works fine with 8.0.29

Reply
Posts: 19
(@joedavis)
Eminent Member
Joined: 9 years ago

I am having the same issue. I have several servers with mysql 8.3 installed, using the 8.33 connector/net. They worked at one point because we have databases on these servers created through solidcp. Now, with solidcp 1.5.1 installed we cannot get connected to mysql through solidcp.

I'm happy to work with whoever I need to help figure this issue out.

Reply
1 Reply
(@hemens)
Joined: 8 years ago

Estimable Member
Posts: 79

@joedavis As mentioned by Trevor, mysql conn 8.0.27 is the best bet as of now and working well for me in both mysql 8 and mysql 5 versions.

latest mysql conn version is breaking it 

Reply
Posts: 19
(@joedavis)
Eminent Member
Joined: 9 years ago

actually, I should say that I am not able to get solidcp to connect to mysql regardless of the version of mysql connector/net. I've tried many different versions. Here's the error message I'm getting:

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Can not create 'MySQL Server 8.3' provider instance with 'SolidCP.Providers.Database.MySqlServer83, SolidCP.Providers.Database.MySQL' type ---> Value cannot be null.
Parameter name: type
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SolidCP.Providers.ServiceProvider.Install()
at SolidCP.EnterpriseServer.esServers.InstallService(Int32 serviceId)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SolidCP.EnterpriseServer.esServers.InstallService(Int32 serviceId)
at SolidCP.Portal.ServersEditService.btnUpdate_Click(Object sender, EventArgs e)
Reply
Posts: 1516
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hey,

 

Normally i would suggest trying MySQL Connector Net 8.0.27 as this generally does work for most versions. If you need the MySQL ODBC connector then 5.2.4 is the best version for that.

 

@joedavis regarding your error im not sure. We have not released a MySQL 8.3 which might be why your getting the error you do (Im not sure if this was custom development by you). You should try use the Mysql 8.0 provider as it should work.

 

Regards,

 

Trevor

Reply
1 Reply
(@joedavis)
Joined: 9 years ago

Eminent Member
Posts: 19

@trobinson thank you.

I was reminded by one of the guys at the office that I did add an entry for 8.3 in the database a while back. I pointed it at a provider which didn't exist though so it of course didn't work. I've adjusted that entry to point to the MySQL 8 provider and it appears things are rolling along. 

Is there a reason the provider hasn't been updated to support MySQL > 8.0?

Reply
Share: