Hello I have seen questions on these type of problem but I am not able to rectify my problem. Please help it.
I am taking the steps as mentioned in the below link to connect MySQL with Excel 2010.
http://www.enduserguides.com/software/office/mso/eug_mysqlodbc.html
I have created the data source with the help of administrative tool and specified the username and password of my MySQL database in computer.
In the 6th step (in excel file choosing "from data sources"> "from data connection wizard") after specifying the data source name (which I created earlier). When I am clicking on test connection it is showing message "Test connection failed because of an error in initializing provider. Unspecified error".
Also if I am specifying the username, password and then clicking on test connection then also same error.
I am not able to find the problem in this I have followed each and every step of that link.
Related
I'm trying to establish a connection between Cloud SQL and Data Studio. I've already tried to make a connection through the MySQL connector with a MySQL db and it failed because I think the Router did not allow the connection.
Then I transferred the db on the cloud but I have the same error!!! Which is:
ID errore: f73c5f49
I already opened Cloud-SQL to all the Data Studio IP addresses, I've created users with "%" and given them all the privileges, I created instance, db and user in CLOUD-SQL (MySQL, 2nd generation).
What else can I try? Could it still be a Router problem?I have to do that for work but it keeps saying that connector parameters are wrong.
PLEASE HELP <3 THANKS A LOT
A common error is to write the instance name instead of the "instance connection name".
You can find the "Instance Connection Name" in the instance page, in the overview section, and normally the format is something like:
[PROJECT_ID]:[region]:[NAME_SQL_INSTANCE]
I also had a similar connection problem with MySql 8.0 but changing to 5.7 fixed it.
I am using SQL authentication for a SSIS connection manager for one domain to another. In Visual Studio the connection is working when tested but password does not save. Running the package in VS is working but when creating a SQL job with the package, it fails to run with error
"Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.
Please help. Thank you.
The wrong way to do this is to put your connection string with the user name and password in the Expressions property's Connection String expression. Then change the ProtectionLevel to Dont [sic] Save Sensitive.
While this works, it leaves your password as plain text in the dtsx file.
I believe one correct way to do this is to set the password for the connection string in the SQL Server Agent's New Job step window on the Data Sources tab.
Another way is to change the Protection level to Save with Password and then enter the password in the Job step's Configuration tab. Unfortunately, I don't use SSIS much anymore and haven't tested either of these methods.
https://learn.microsoft.com/en-us/sql/ssms/agent/job-step-properties-new-job-step-general-page?view=sql-server-2017
MS Forum
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.
Errors
Database administrators report Microsoft SQL Server 2008 server-side error "Invalid Login" (error 18456, Severity: 14, State: 5).
Error examples from the server log:
Dec 1 2010 10:12AM - Login failed for user '{Active Directory Name #1}'. Reason: Could not find a login matching the name provided. [CLIENT: {IP Address #1}]
Dec 1 2010 10:44AM - Login failed for user '{Active Directory Name #2}'. Reason: Could not find a login matching the name provided. [CLIENT: {IP Address #2}]
Dec 1 2010 2:03PM - Login failed for user '{Active Directory Name #3}'. Reason: Could not find a login matching the name provided. [CLIENT: {IP Address #3}]
Dec 1 2010 4:18PM - Login failed for user 'Admin'. Reason: Could not find a login matching the name provided. [CLIENT: {IP Address #1}]
The {Active Directory Name} is the same as their login name, without the domain. For example, full name would be {domain}\{Active Directory Name}.
The error for user "Admin" comes from the same IP address as {Active Directory Name #1}, a user developing Microsoft Access Visual Basic for Applications (VBA) code; I suspect this stems from a need to configure his minimal use of VBA with a proper Windows Authentication connection string, even though he solely accesses data via an ODBC DSN link.
Environment
Microsoft Access 2003 (frontend) database containing ODBC File DSN links to tables in a read-only Microsoft SQL Server 2008 (backend) database.
I have administrator rights to the frontend database. I have read-only security rights to the backend database, which resides on a hosted server at an external data center. DBA's have configured the backend database for Windows Authentication.
End users login to their PCs with Active Directory accounts, open the frontend database, then use Microsoft Access Query Designer to generate reports using the table links to the backend database. The frontend database does not use Microsoft Access Jet Security (to my knowledge--there is no login prompt).
The frontend database reports no (visible) errors and produces expected results.
ODBC file DSN contents
[ODBC]
DRIVER=SQL Server
Trusted_Connection=Yes
StatsLogFile={path}
StatsLog_On=Yes
DATABASE={dbname}
APP=Microsoft Data Access Components
Description={general description}
SERVER={server name}
Why would the File DSN links work, without error, but generate a server-side Invalid Login error? Thank you.
Is there any chance that the end users are seeing cached data? Is SQL Server set up to allow remote connections? Are the AD accounts set up as logins as well as entitled users on the appropriate database? When you test the ODBC connection through the ODBC manager do you get a successful connection? Does a successful connection test generate the error? Is the back-end database and the front-end application on the same domain? If not, is there domain trust set-up? (If not you may need to use SQL Logins rather and AD)
Those are all the types of things I would typically run through to try and troubleshoot this type of issue.
The source of the issue seems to be an undocumented (?), Microsoft Access 255-character limit on the ODBC connection string.
Each Microsoft Access ODBC-linked table was created with a DSN file containing line “Trusted_Connection=Yes”.
Presumably, this tells Microsoft Access to use Windows Authentication.
However, while double-checking one of the ODBC-linked tables, I noticed text “Trusted_Connection=Yes” falls outside the first 255 characters of text. I can see it is there by using the VBA Immediate Window and running command
print CurrentDb.TableDefs("{table}").Connect
but this only prints 271 characters, not the full string. The final 10 characters, however, are:
Trusted_Co
Re-linking the tables with a DSN file containing Trusted_Connection=Yes line in the first 255 characters solved the issue.
Thank you.