I am trying to create a datasource in Report Builder using an ODBC connection (Progress OpenEdge 10.2B Driver)
I've set up the connection and created a User DSN. Tested the connection and got a connection established success message so pretty sure it's set up correctly in ODBC Data Source Administrator.
When I try to add the data source in Report Builder, I'm selecting the option to "Use a connection embedded in my report" and select connection type of ODBC from the Connection Type lookup.
For the connection string, I can select the data source name that I set up, add in my user name and password, but when I test the connection, I get the following error:
ERROR [HY000] [DataDirect] [ODBC Progress OpenEdge Wire Protocol driver]Insufficient information to connect to the data source.
ERROR [HY000] [DataDirect] ODBC Progress OpenEdge Wire Protocol driver] Insufficient information to connect to the data source.
I must be doing something wrong but can't see anything obvious. Any advice would be greatfully received.
Thank you
Here's a few KB articles that might help you:
https://knowledgebase.progress.com/articles/Article/5796
https://knowledgebase.progress.com/articles/Article/7460
https://knowledgebase.progress.com/articles/Article/9314
Another option is that the user you are using to connect to the database with doesn't have SELECT privileges. This KB gives you details on how to do that: https://knowledgebase.progress.com/articles/Article/P101721
Related
This is really odd to me. I am using an ODBC connection as a data source in SSIS. I am able to preview data, but when I attempt to execute the package (still within Visual Studio for development), I get an error on the initial data source.
The error I am receiving is:
There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.
The AcquireConnection method call to the connection manager xxx failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
ODBC Source failed validation and returned error code 0x80004005.
Clearly I have the right username, password, and ODBC connection to some degree, because I am able to see the data. However I am failing on establishing the connection when I attempt to run the package, so I must be doing something wrong. Any idea what it might be?
It ended up being that the drivers associated with the ODBC connection (gsk8ssl.dll) installed on the machine needed to be added to the path variables on both my local and on the server. This was for connecting to a DB2 database.
Application: Report Builder
Connection Type: ODBC
I am attempting to connect to, and query a csv using SSRS. I've added a system DSN, and am able to successfully connect when I click the "Test Connection" button on the "Connection Properties" window. However when I click the same button within the "Data Source Properties" window, I get the error message below.
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not
found and no default driver specified
What's strange is that I created a dataset with a simple SELECT * query FROM [csvfilename], and it successfully displays all the fields from my csv. I therefore know it can access it. When I try to run the report, however, I get the error below.
Cannot create a connection to data source '[DataSource Name]' (rsErrorOpeningConnection)
Here is the Connection String I'm using within my DataSource:
Dsn=WIPEXPORT;Driver=Microsoft Text Driver (*.txt;dbq=I:\\HARVEST\\DATA BROWSERS\\WIPEXPORT;defaultdir=I:\\HARVEST\\DATA BROWSERS\\WIPEXPORT;driverid=27;fil=text;maxbuffersize=2048;maxscanrows=8;pagetimeout=5;safetransactions=0;threads=3;usercommitsync=Yes
I apologize if this has already been answered. I couldn't seem to find anyone with my specific problem.
So after trying just about every connection string configuration within ReportBuilder, I ended up switching to VisualStudio where it worked immediately. I even copied the successful connection string from VS back to RB and RB was still broken. Don't know if it's my RB installation or what, but at least it works now.
I am trying to connect to Datasource but getting this error:
An error occurred during local report processing.
An error has occurred during report processing.
Cannot create a connection to data source 'PO'.
You have specified integrated security or credentials in the connection string for the data source, but the data source is configured to use a different credential type. To use the values in the connection string, you must configure the unattended report processing account for the report server.
Any idea how to resolve this?
Thanks
Aruna
Looks like it forgot your password,
If it is an embedded data source > Right click on the Data source then go to properties > credentials.
If it is a shared data source go to the shared data sources, right click on the shared data source and hit Open, once in there click on credentials and enter the credentials again.
I was having this same issue. For me, the problem was that I was using a DNS alias as the server name in the connection string. Once I changed that to the actual machine name my connection was solid.
I guess this issue occurred in Visual Studio when you connected to data source but were not able to create a report using that data source. What credential did you use when creating database. Windows authentication or username and password. Right click on data source in VS and select credential as same as your server/db in properties. Mine is windows auth for my server/db and selected the same for data source. so now I am able to create reports.
I've got WampServer running a local instance of WordPress, and I have SSRS running in native mode.
I've written a report that queries the MySQL database, and it works and runs just fine within Visual Studio.
If I launch it though, it first had issues with my ODBC shared data source, which was as follows:
Name of shared data source: localhost.rds
ODBC Connection string: Dsn=localhostuserDSN
That DSN is a user DSN (as you might've guessed), and it uses the MySQL ODBC 5.3 Unicode driver. It's configured as follows:
TCP/IP server: localhost
Port: 3306
User: root
Password: <blank>
Database: wp
When tested, the connection succeeds, and the report works just fine.
When deployed though, I got the following error:
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
After much research and hair-pulling, I finally found out that if I changed the data source connection string to...
Dsn=localhostUserDSN;Driver=MySQL ODBC 5.3 Unicode Driver
...that also works, and at least then, the connection also succeed when in the Data Sources configuration screen for the report after it's deployed. But then, just when I thought I was finally out of the woods, I run the report and get the following error message:
ERROR [3D000] [MySQL][ODBC 5.3(w) Driver][mysqld-5.7.9]No database selected
The thing is, I can't specify a database, or at least I don't know a way to.
If I try changing the connection string to...
Dsn=localhostUserDSN;Driver=MySQL ODBC 5.3 Unicode Driver;database=wp
...it says the (blank) password isn't valid, before I've even pressed the 'Test' button.
If I tack on 'USE [wp]' to the query in Visual Studio, it abruptly protests.
I thought maybe I'd get around that by putting it in a stored procedure, but since the data is being queried directly from the MySQL database, I can't do that either.
(Before attempting any of this, I already tried syncing/converting the MySQL db to the SQL db, but I kept running into issues with the data conversion.)
Thinking it might be a permission issue, I've also tried running...
GRANT ALL ON [wp] TO root#localhost;
...and...
GRANT ALL PRIVILEGES ON [wp] TO root#localhost;
in SSMS, but in both cases, it says:
Cannot find the object 'wp', because it does not exist or you do not have permission.
And I'm the only admin on a local machine. I installed SQL and it uses Windows Authentication, so I don't see how I wouldn't have permission, and I have to assume it's an issue with the syntax.
I saw elsewhere here that someone suggested '[wp].*', but it doesn't like that either.
I've been at this literally all day, and I'm at my whits end, so any constructive feedback would be greatly appreciated!
For anyone stumbling across this in the future, I think we resolved the original issue, although I've run into other issues which may be specific to me.
Three things, not sure if the first one is related:
1) In the query for the dataset of the report, I specified the table like so "SELECT wp_posts.ID FROM wp_posts" instead of just "SELECT ID FROM wp_posts".
2) I went back to adding on "database=wp" to the ODBC connection string.
3) Even though both work in Visual Studio, I switched to a System DSN instead of the User DSN.
I think that should get you back in action.
I have an SSIS package that contains a Lookup Transformation. This requires a connection to the database. At the connection manager, when I use the Windows authentication the connection works fine but when I use SQL Server Authentication then I get this error:
[A140_DAMAGETYPETEXT [3799]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "servername.Datenbankname.sqlUser" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Connection string:
Data Source=TheServerName;User ID=TheSQLUser;Initial Catalog=TheDababase;Provider=SQLNCLI10.1;Persist Security Info=True;Application Name=NameOfThePackage{80F4BFAB-642D-457E-9F47-1E811AFA48D0}ServerName.TheDababase.TheSQLUser;
Cause of the issue:
Your connection string is missing the Password attribute. That is the reason why the connection manager is failing to connect to the database instance.
Possible option to fix:
When you create the connection manager on SSIS, make sure to check the Save my password box so that the Password is retained in the connection string. If you do not check this box, the value will not be retained and you have to key in the value.
Package configuration:
If you are using package configurations, adding / updating the connection manager will cause the Password attribute to drop from the connection string property. I usually use database based package configuration. So, I use a query to update the connection string in the package configuration table every time I update the package configurations.
Recommendation:
I prefer to use Windows authentication so that the password to connect to the database is not exposed. I feel that Windows Authentication is little more secure than dealing with SQL Server Authentication.
here was the solution for me: click
the thread from Raj_007 was the rescue. I use a sequece container and the TransactionOption was setting to required.
I changed the TransactionOption to supported and it worked for me.