Forum Discussion
.dll Error When Setting Up Oracle Gateway Data Source
I was waiting for IT resource availability for a couple weeks to uninstall and reinstall the software. I retried the connection yesterday and got the error message below, which is different from the original .dll error message. For us at least, this new error message has tended to indicate that our Database Admin team needs to grant access. Once they did, I was able to successfully create the gateway.
I have no idea what caused and resolved the .dll error message, as I didn't do anything. Our DBA speculated that perhaps it was some permission settings on the server. Unfortunately, I don't have any definitive steps on how to resolve for future scenarios.
Hi Anonymous
It appears that you have an issue when the software was installed I would suggest re-installing it and trying again?
THis is an older blog post but it should apply to ensure that you got what you need to get it working: Power BI – On-Premise Gateway Configuration steps to an Oracle Database - FourMoo | Power BI | Data Analytics
Thanks GilbertQ for the recommendation. I have a meeting scheduled with one of our Oracle DBA's to try the reinstall, but due to schedules it's not until 10/17. I'll follow up after that on whether reinstalling resolves the issue.
Hi Anonymous ,
Has your problem been solved?If the problem has been solved you can mark the reply for the standard answer to help the other members find it more quickly. If not, please point it out.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I was waiting for IT resource availability for a couple weeks to uninstall and reinstall the software. I retried the connection yesterday and got the error message below, which is different from the original .dll error message. For us at least, this new error message has tended to indicate that our Database Admin team needs to grant access. Once they did, I was able to successfully create the gateway.
I have no idea what caused and resolved the .dll error message, as I didn't do anything. Our DBA speculated that perhaps it was some permission settings on the server. Unfortunately, I don't have any definitive steps on how to resolve for future scenarios.