logo

Warning: The forum is now for consultation only. Please use GitHub Discussions to post any questions or comments.


Welcome Guest ! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
vicry21  
#1 Posted : Thursday, November 10, 2016 2:05:18 AM(UTC)
vicry21

Rank: Member

Groups: Registered
Joined: 11/10/2016(UTC)
Posts: 14
China
Location: 江苏

Thanks: 2 times
I can create a MySQL connection,but dont create table from catalog.
the error is "ERROR 22018 MYSQL ODBC 5.3a Driver Mysqld-5.6.29-log"
Pls help me.



Provider=MSDASQL.1;Persist Security Info=True;Data Source=pu;Initial Catalog=pudev
[2016/11/10 9:50:11] Database connection checked successfully.
epf  
#2 Posted : Thursday, November 10, 2016 10:47:17 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 205 time(s) in 198 post(s)
Sorry, we have a poor experience with MySQL, I know that it has worked (probably with an older version of the ODBC driver).
You can still create your tables manually...

Could be nice if someone can look at it to integrate the fix in the coming version....
vicry21  
#3 Posted : Friday, November 11, 2016 6:45:28 AM(UTC)
vicry21

Rank: Member

Groups: Registered
Joined: 11/10/2016(UTC)
Posts: 14
China
Location: 江苏

Thanks: 2 times
Now i can add table but dont use to create table from catalog.
epf  
#4 Posted : Wednesday, November 23, 2016 4:53:06 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 205 time(s) in 198 post(s)
I made a quick test with the MySQL default database and the ODBC Driver and it works fine: it reads the database catalog and creates the tables and columns.
Here is my connection string:
Code:
Provider=MSDASQL.1;Persist Security Info=False;Extended Properties="DSN=mysql;SERVER=localhost;UID=root;DATABASE=sakila;PORT=3306"
treesprite  
#5 Posted : Monday, January 22, 2018 7:39:06 PM(UTC)
treesprite

Rank: Newbie

Groups: Registered
Joined: 1/4/2018(UTC)
Posts: 4
United States
Location: Little Rock

Can the MSDASQL.1 be used/installed on a MS Windows 2012 R2 Server? (The version I have found is for Windows Server 2003)

Is there any other "provider" that can be used in making connections to mySQL?

I have "MySQL Connector/ODBC" installed and am successful in connecting to my mysql database from there. I am just not sure how to setup the appropriate connection string in SEAL REPORT.

Can you provide some assistance?

Thanks

FYI: SEAL REPORT works ~great~ in connecting to MS SQL Server databases and have already delivered reports to my manager. Yay!!
epf  
#6 Posted : Tuesday, January 23, 2018 7:02:27 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 205 time(s) in 198 post(s)
For MySQL, you first have to install a 32bit ODBC driver on your server.
Then using the 32bit ODBC Manager, you can create a Data Source connecting to your MySQL server (better use a System Data Source so it can be used by different user).
Finally, using SR, create a connection using the OLEDB Driver for ODBC, then click next and choose the Data Source you have previously created.
Marten  
#7 Posted : Wednesday, October 23, 2019 12:29:15 PM(UTC)
Marten

Rank: Newbie

Groups: Registered
Joined: 10/14/2019(UTC)
Posts: 3
Netherlands
Location: Amstelveen

Hi EPF,

I seem to have a similar problem:

I succeeded to run my report in the way you described, however when I wanted to publish it via IIS on the web it did not work.

I got the message:

Error detail:
Error opening database connection:
ERROR [IM002] [Microsoft][ODBC-stuurprogrammabeheer] The name of the source has not been found and there is no driver found [... translated from Dutch]

Do you have any tips?

Marten

epf  
#8 Posted : Thursday, October 24, 2019 7:47:48 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 205 time(s) in 198 post(s)
For the Web Report Server, first reboot your server so IIS can load your new installed drivers...
then check the identity of the user running your Web application (this is more IIS stuff), by default the Web Report Server is published on an application pool using LocalSystem user.
this user must have the rights to connect to the database...
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.