ODBC Connector for Highrise - Power BI connector not working, what is the issue? - api

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.

Related

Error in processing request Error Code: 200 - through cPanel, myphpadmin. After been hacked

I'm using cPanel with myphpadmin SQL Database and Wordpress, and I got hacked!
I have managed to restore the wordpress website from a backup. I have restored the database along with all the files. I did through the restore in cPanel.
I wanted to check the SQL DB and make sure the user name of the hacker was gone. As it showed up in the WP users. Wordfence alerted me that a user was created outside of WP.
When I try to access the 'myphpadmin' in different browsers (it makes no difference) I get this error...
"Error in processing request Error Code: 200 Error text: OK (rejected)
It seems that the connection to server has been lost. Please check
your network connectivity and server status."
I have tried contacting my server, they seem hopeless. They keep telling me to reach out to Sucuri. But I can't afford their service. Besides, with some direction, Im sure I can manage it. I just need to get past this error.
After I click on the DB that is located to the left of this message in left pane. I get like unformatted page. its so strange.
I've looked up online, there are solutions using WAMP but not through cPanel.
I added an image of what it looks like after I click the DB name.
How can I solve this problem?

User login failed for <user> in production but same connection string works from local client

I have an Azure database setup of which I have included the below connection string as I believe it should be. Problem is when I try to run my client app in production, the server returns a 500 internal error. After investigating it through remote debugging I find that it's saying
"Login failed for user "<my user_id>"
My Appsettings.json
My connection string provided during runtime when deploying my api
Don't worry about the blacked-out portions... I've verified those to be the same in both.
Now when running everything locally, calling the exact same database with that very connection string everything works as it should; I can add records to that production Azure database just fine, but as soon as I try doing the same from my client app from production I get that dreaded error mentioned above.
Can anyone tell me what might be happening? I've been over and over this and it's driving me mad. I've even gone as far as changing the connection string to be Server=... I've made sure to append the # to the user_id. I believe I've tried just about everything I could find that wasn't 8 years old, including searching similar issues here... nothing seems to be quite like my issue exactly.
If you need more information let me know and I'll update my question.
Thanks!
EDIT: Adding this to show I've already added all of my output IPs from my api app service to my Sql server firewall. Can someone tell me if all my settings look good?

Facing issue with ODataSource Connection Manager in SSIS for pulling the data from Sharepoint site

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!!

Azure Storage account opening issue

I have an RBAC access to Azure portal. Previously I was able to access storage account and blobs successfully. But suddenly I am unable to access container or blob. I am able to view the storage account listed for me, but cannot access it.
I get error as "Something went wrong while getting your resources. Please try again later." I tried refreshing, clearing cache and signing again. Still facing same issue.
In portal I get notification as "Refresh the browser to try again.
Microsoft_Azure_Storage extension failed to load"
There is no network issue, as I can access all other resources from portal at same point.
Also there is no Unauthorized access issue notification.
Unable to figure out what is the issue.
Any help highly appreciated.
I'd recommend checking the activity logs for recent RBAC changes in case if they happened and someone changed access to containers/blobs, here's how: https://learn.microsoft.com/en-us/azure/role-based-access-control/change-history-report
I'd also recommend checking the list of roles/access you currently have by following these steps: https://learn.microsoft.com/en-us/azure/role-based-access-control/change-history-report
If you are still experiencing the issue, in case if you have a co-admin, check if they are facing the same issues. if they are, please send me your subscription ID, link to this thread, and include attn Adam in the subject to AzCommunity[at]microsoft.com ?
I'll enable a free support ticket to quickly escalate it.
I hade the same issue while I was using VPN from Bangladesh. When I disconnected from the VPN, it works fine.

Create data source in Report Builder 3.0 to a data cube using "current windows user" credentials

I have Report Builder 3.0 installed on my local PC. I am creating a new report and adding an embedded data source to a SQL Server Analysis Services database.
When I build the connection string of the data source, choosing the server name and the database name, I click 'Test Connection' and receive a message saying "Test connection succeeded". So far, so good.
I close the connection properties with the OK button, and on the Data Source Properties window I click the 'Test Connection' button. This time I get an error saying "The connection either timed out or was lost".
If I ignore the error then I can successfully add a dataset to my report and add data from the dataset in to the report design, but when I try to run the report (on my local PC) I again get an error connecting to the data source.
My best guess is that the connection that succeeded is running under my credentials, whereas the connection that fails is running as some other credential and so needs to use Kerberos delegation to pass my credentials along, but that is only a guess and even if I am correct I am at a loss to understand how to fix the issue - I don't know what other credentials may be being used and I have already set SPN's for the Analysis Services service account.
So it turns out that it was a Kerberos issue as I suspected, and I was also correct that Report Builder was testing the connection using some process running under another authentication context.
It turns out that when setting up Report Builder (and I had forgotten it) that you specify a default SSRS Report Server (see screenshot). It must be that when testing data sources or running reports that it connects to that default Report Server and does the work from there - I was assuming that everything was running locally!
Once I figured that out it was just a case of finding a good guide on how to configure SSRS for Kerberos and everything started working. In my case the only bit that I hadn't already done was to add the <RSWindowsNegotiate/> setting to the AuthenticationTypes in the rsreportserver.config file