I have downloaded and install the Simba Big Query ODBC connector.
When I try to configure following the instructions on Simba's website, when I enter the confirmation code at which point the refresh token should populate I get error :-
[Simba]BigQuery Error interacting with REST API: Problem with the SSL CA cert (path ? access rights?)
I get this on both my works laptop and my home PC.
I have also tried the Service Authentication and have selected the key file path and also get the error.
It should be noted I can successfully access Biq Query through other methods using my authorized credentials.
Can anyone help ?
Platform is Windows 64Bit
Regards,
Ian
Related
I have signed up for 30 day trial version for snowflake, as part of learning I am trying to run the Snowsql (client) from my windows desktop. I installed client from snowflake client repository (account name, username and password are all correct).
Got the following error:
C:\Users\ugain>snowsql -a vg49826 -u ugainedi
Password:
**250001 (08001): Failed to connect to DB. Verify the account name is correct: vg49826.snowflakecomputing.com:443. HTTP 403: Forbidden
If the error message is unclear, enable logging using -o log_level=DEBUG and see the log to find out the cause. Contact support for further help.
Goodbye!**
Appreciate the help. Thank you!
Go to your account using the Snowflake web UI and look at the URL. Since there is no account vg49826.snowflakecomputing.com, that means you're running Snowflake somewhere other than on AWS_US_WEST_2. That's the only region that does not include the region in the account name for connection purposes.
Copy the portion of the URL up to but not including "snowflakecomputing.com". It will be something like vg49826.us-east-1, vg49826.east-us-2.azure, or something similar. Your Snowflake account, for the purposes of connecting to SnowSQL is the portion of the URL after https:// and before snowflakecomputing.com in the web UI URL.
We are trying to pull data from Sharepoint site using SSIS ODataSource Connection Manager. But, we are facing issue with the ODataSource which is failing when we are trying to test the connection. It is giving below error message, even though the password we are giving is correct. We are using Microsoft Online Services as Authentication Type.
TITLE: OData Connection Manager Editor
Test connection failed
The sign-in name or password does not match one in the Microsoft
account system.
(Microsoft.SqlServer.IntegrationServices.ODataConnectionManager)
We are using SSDT Version 2017. Here is the screenshot for your reference.
Can you please let us know, what would be the issue and how to fix this.
Thanks in Advance!!
I'm trying to access an Azure SQL database of mine from SQL Server Management Studio on my local machine and have failed due to requiring 2FA. That's fine, I'll try and sort that.
What concerns me is the server that it's attempting to connect to. What the hell is "database.usgovcloudapi.net"???
I think the error is happened when you're using Active Directory Authentication to login your Azure SQL database.
The AD document Authentication and authorization error codes show us the error code and message, but doesn't tell us how to solve the problem:
You need call your AD administrator to re-configure your AD account and try again.
If you still have the error, the document suggest us:
Have a question or can't find what you're looking for? Create a
GitHub issue or see Support and help options for developers to learn
about other ways you can get help and support.
Update:
Congratulations that ataraxia has solved the error:
"Thank you, I got around it by changing the authentication provider to "Active Directory - Universal with MFA Support" on the SSMS login prompt, which then opened a browser window with the regular Microsoft online login and after entering my credentials sent a notification to my mobile, then returned to SSMS and authenticated."
If anyone want details about this, please #ataraxia in the comment.
Hope this helps.
That would be the Azure Government services, designed for use by US government agencies and their partners.
https://azure.microsoft.com/en-us/global-infrastructure/government/
I am trying to connect PowerBI with Highrise CRM using CData's (the company's), ODBC Connector but every time I try to test the connection, it gives a '401 unauthorized' error. I have admin rights in both, the system and Highrise, the credentials are correct as well. It does not open a browser window asking for access, as it should once it's successfully connected.
I created the app as required and put in the Redirect URI as http://localhost:2435, both in the app as well as the connector. I tried resetting the connection, tried removing the connector and adding it again but nothing seems to work. I get the same error every time. I have also triple checked the OAuth 2.0 credentials from the app and they are correct as well.
I am not able to figure out where exactly the problem lies. I have the log file for it but I am not sure what part of it would be beneficial to post here to troubleshoot.
I am using QuickBooks 2013 pro on server A, I have a self signed cert on server B. I had server A navigate to the services on SERVER B install the self signed cert into trusted root. Then had the web connector on SERVER A try to add an application. It is coming back with this error
qbwc1048: QuickBooks Web Connector Could not verify the web
application server certificate.
Any help in solving this would be great. Thank you very much
For anyone else having a similar problem, it may not be the certificate at all. It could be the server is closing the connection or returning an error code.
For more details, first click file -> clear log in the web connector. Then, try adding your application again. After it fails, click the view log button at the top right. Scroll down for more details on what happened.
You will see something like, remote server returned an error (401) unauthorized, or a similar message that is far more useful than what appears in the dialogue box.
#consolibyte Closed all IE windows and re-imported the SSL works now. Thank you