MySQL Data Source Wizard not working on Visual Studio 2017 - mysql

I have Visual Studio 2017 Community installed, and MySQL Community 8.0.12 on a same PC. It is also equipped with MySQL for Visual Studio 2.0.5 and MySQL Connector/NET 8.0.12.
Now, using the DataSource Wizard in Visual Studio. I was able to test the connection to my server and select which Tables that I wanted to add to the DataSet.
However when I click Finish, a following errors showed up:
"Some updating commands could not be generated automatically. The database returned the following error: Unexpected Error"
This is followed by another error log:
"Could not retrieve schema information for table or view [tablename]"
for every Table I wanted to add.
I already looked up to some information regarding the said errors, but so far they are talking about older version of Visual Studio and MySQL. Any help will be appreciated. Thank you.


So after some fiddling and looking into MySQL official website, I downgraded my Connector/NET to version 6.9.8, and downgraded the MySQL for Visual Studio as well to version 1.2.7
Now the DataSource is able to get table definitions and so on.
Still a minor error shows up whenever the "FINISH" button in DataSource wizard is pressed, that shows up "Failed to add relation(s) Specified cast is not valid".
This error however doesn't prevent the DataSource to be created and used. I'm still not sure what caused this error though.

Related

An Out-of-Date Binding Error between MySQL DB - Visual Studio 2019&2022

I’ve filled a database table in the MySQL DBMS(which is 8.0.29, the latest version as of Jul. 2022) importing an external .csv file with corresponding data type and compatible encoding.
First, I connected the MySQL database table to Microsoft Visual Studio 2019 and 2022. And then, I tried to data-bind the database table via DataSource attribute of ComboBox control. The following error occurred during the “Choosing Database Objects” process in Data Source Configuration Wizard, however:
ERROR [01000] [MySQL][ODBC 8.0(w) Driver][mysqld-8.0.29]The number of
attributes is larger than the number of attribute values provided
In order to solve the error, I’ve checked the following:
Connected another table in the MySQL DBMS to Microsoft Visual Studio 2019 and 2022.
Ensured all of the installed MySQL products are the latest version through MySQL Installer.
Modified and repaired “MySQL for Visual Studio”.
Checked every field in the database table contains intact contents of the imported .csv file.
Consulted the references provided from MySQL.
In the last thing of the above, the references[1][2] say that:
“An assertion failure occurred in SQLDescribeCol() if the column number used is larger than the number of columns in the result set. (Bug #17311065)”
Things are actually opposite.
It’s the explanation for one of the solved bugs in the MySQL version released in 2014. But it’s recurred while using the up-to-date 8.0.29 MySQL version, so I couldn’t connect MySQL DB to Microsoft Visual Studio 2019 and 2022.
How can I solve the error in this situation? Do I have to wait until the next anticipated version of MySQL is released?

Fatal error encountered attempting to read the resultset In Mysql version 8.0.2

This errors occurred only when stored procedure used otherwise in inline query works. Mysql version is 8.0.21 and framework used - Visual studio 2012 ultimate.
enter image description here
This errors occurred only when stored procedure used otherwise inline query works. MySQL version is 8.0.21 and framework used - Visual studio 2012 ultimate.
Please help me. Thanks in advance

May be it is mysql version dll issue.
remove current mysql dll references and add old one mysql version dll references.
i am not sure it is correct or not. but this works for me.

Issues with MySQL Connector Net 6.8.3

So I was getting some problems with connecting .NET and MySQL and figured there was something wrong with the connector. Went into my control panel -> uninstall/repair -> repair MySQL Connector Net 6.8.3.
The repair starts normally but after a few seconds I get a screen saying "A serious problem occured during the installation". I tried reinstalling it but just got to the MySQL installer and it said all my products are up to date.
Now I went into the MySQL installer again to uninstall the .Net connector and got the error:
Removing system registry values
UnregisterPerfCounterData
RollbackUnregisterPerfCounterData
Unpublishing Product Features
Unpublishing assembly information
Updating component registration
InstallInitialize
1: MySQL Connector Net 6.8.3 2: {"SERIAL-CODE"} 3: 3
The product Connector/NET failed to remove successfully.
I have repaired all the Visual Studio products without any problems except this one that is really vital for my project.
So now I am not sure what I should do...

Needed a program like CCleaner to remove all the traces of the program on the computer then download it again and it worked!

MySQL Data Provider is absent in Change Data Source of VS2013

I have installed last C:\Program Files\MySQL\MySQL Connector Net 6.8.3
but it is absent in Change Data Source of VS2013 so I cannot use it with EntityFramework.
It appears under Change Data Source of VS2012 perfectly...
What do I am missing?
I know that I can use always VS2012 to create EF to MySQL... But I would like see MySQL Data Provider in Change Data Source of VS2013
Any clue?

I did some investigation and I installed this
https://cdn.mysql.com/Downloads/MySQLInstaller/mysql-visualstudio-plugin-1.1.1.msi
based on
http://forums.mysql.com/read.php?174,601041,601041#msg-601041
And it is appearing well!!! Hahahahaa!

How to fix the error CPackage::LoadFromXML that causes the package to fail?

I had this package which been running fine since a year or more. All of sudden it has thrown below error. Though on restart it was success. How to debug this issue and prevent from happening again.
Executed as user: xxxxx. Microsoft (R) SQL Server Execute Package Utility Version
10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 7:15:08 AM Error: 2011-07-07 07:15:08.62 Code: 0xC0010018 Source:
Description: Error loading value "
<DTS:VariableValue xmlns:DTS="www.microsoft.com/SqlServer/Dts"
DTS:DataSubType="ManagedSerializable"
DTS:DataType="13"><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="htt" from node "DTS:VariableValue".
End Error
Error: 2011-07-07 07:15:08.62 Code: 0xC0010018 Source:
Description: Error loading value
"<DTS:Variable xmlns:DTS="www.microsoft.com/SqlServer/Dts">
<DTS:Property DTS:Name="Expression"></DTS:Property>
<DTS:Property DTS:Name="EvaluateAsExpression">0</DTS:Property>
<DTS:Property DTS:Name="Namespace">User</DTS:Property>
<DTS:Property DTS:Name=" from node "DTS:Variable".
End Error
Could not load package "d:\edw\edw\trunk\src\etlHandler\HDL\DropZoneJobHandler.dtsx"
because of error 0xC0010014.
Description: The package failed to load due to error 0xC0010014 "One or more
error occurred. There should be more specific errors preceding this one that
explains the details of the errors. This message is used as a return value
from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
Source: Started: 7:15:08 AM Finished: 7:15:08 AM Elapsed: 0.609 seconds.
The package could not be loaded. The step failed.

I have had this issue on Visual Studio 2015 when creating SSIS Packages.
To resolve it, I changed the TargetServerVersion to SQL Server and that resolved the error.

I was using SSIS package which was upgraded to SSIS 2012, and the SSMS that I was using was 2008. This was the issue that I faced, and I opened the SSMS 2012 and it stopped throwing this error.
I hope this is the case, although with what I have researched, this error could be thrown for various other reasons as well.

For me the error came from a bad password when opening the package. It's strange because usually it just asked me to type in the password again, but since last VS2017 update, the package just fails.

I was getting this 0xC0010014 error when I used a VS 2017 ent build with a dtexec on a server. I set server to SQLServer2014 and the job started to run, but for a while it would throw the 0xC0010014 at the top of the ssis log but still run successfully. I think if you have EncryptSensitiveWithPassword you have to reset the package password after you make the SQLServernnnn change. You have to be aware of what version of dtexec you have on the server, what version the package might have been built in originally (many packages run for years without touching them and may have been built with vs 2015 or vs 2012) and what version of VS you are building with (easier to keep a laptop up to date, maybe you have VS 2017 or VS 2019). You might have a really current Visual Studio to do your builds, but be running in a really old server/dtexec environment.

I have resolved this issue by changing a connection that was referencing to one of my DSN entries that was not created.
After removing the connection, I was able to view the package and then I created a new connection after the new DSN was created.
Please let me know if you need more details and i will provide.
Thanks.

I encountered this error when attempting to schedule an SSIS job to run using SQL Agent. The error came up after I'd selected the package and clicked OK to exit the setup of the step in SQL Agent.
In my environment, I develop SSIS jobs on server A, and schedule jobs in SQL Agent from my local computer. SQL is hosted on server B.
I'm usually able to schedule jobs without error using SSMS on my local computer. However, this particular SSIS package uses the Sharepoint List Adapater, which I'd installed on server A for the SSIS development.
The solution was to install that adapter on my local computer. I also installed it on server B, which hosts our SQL instance.

The solution for this scenario was asking customer change the debug option Run64BitRuntime from True to False. With this Run64BitRuntime=False setting, all works as in 32bit mode. See below link:
https://blogs.msdn.microsoft.com/farukcelik/2010/06/16/why-package-load-error-0xc0010014-in-cpackageloadfromxml-error-appears-while-trying-to-run-an-ssis-package/

I had similar issue when I try to setup Import/Export process on SQL server and save it as SSIS package. I was using excel(.xlxs) as source file.
I resolved it by installing https://www.microsoft.com/en-pk/download/confirmation.aspx?id=4438 (Access 2007 Runtime) on sever).

I created a new project in VS 2019, added a couple tasks and tried to upload and got this error.
Solution: SQL Server was 2012 and the project was set as SQL Server 2017. Changed the project to 2012 saved everything and it worked.

Please take a look at the following link from social.msdn.microsoft.com discussing about a similar error message. Hope that helps.
CPackage::LoadFromXML Failure