Connecting to azure through SQL crashes it - sql

I've been attempting to migrate from my own MSSQL to Azure Database services.
I got all the firewall things working and the database running on the azure, but when I try to connect through the local pc it crashed with an unknown exception.
So does visual studio.
Any ideas what could cause this unknown error?
Heres a picture demonstrating the crash and its not a user/password error. Just not.

Maybe it's better if you try to provide the Exception/Error code. You can use:
http://msdn.microsoft.com/en-us/library/ff394106.aspx
I had similar problems and in the end it turns to be the connection I've used - so one option is to restart your LAN/Network.
Update: According to me is config related error, please see these solutions here:
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/runtime-error-p6025-pure-virtual-function-call-on/89e10d2f-b949-e011-8dfc-68b599b31bf5
https://superuser.com/questions/628314/runtime-error-r6025-unable-to-see-location-of-program-causing-the-error
About SSL certificate and Browser you're using:
https://bugzilla.mozilla.org/show_bug.cgi?id=133476
http://www.symantec.com/connect/forums/r6025-pure-virtual-function-call-runtime-error
Maybe you've missed something, also what Win are you with?

Related

ORA-12557: Connecting ORACLE to modelling software (EMBLEM)

I'm trying to make a connection between Emblem and Oracle. I've already made a similar connection using R which works fine. The image below shows the environment variables that I am using. I also have set up a driver via ODBC Data Source Administrator. Again, this set up has worked fine when connecting to R using ROracle.
However, when I try to connect via Emblem I get the following error: ORA-12557: TNS:protocol adapter not loadable. When in SQL Developer I can see that my connection uses LDAP instead of TNS, so I'm not sure why I have a TNS error (though my knowledge of these protocols are very limited). Can someone please advise on how to resolve this?
So far I've tried deleting ORACLE_HOME variable below but then I ran into OCI errors, so I reverted back to the original path.

Error when connecting to Azure SQL Server from an ASP.Net Core App (Blazor) inside a Docker container

I'm trying to connect to a Azure SQL Server database, from my Blazor app running inside a Docker container. Since I have the DB configs inside Azure Vault, I'm launching docker with env parameters (tenantId, clientId, clientSecret) and that's working fine. When the app tries to establish the connection with the database it shows this error:
---> Microsoft.Data.SqlClient.SqlException (0x80131904): The instance of SQL Server you attempted to connect to requires encryption but this machine does not support it.
This only occurs if I try to launch the app from the container, it works properly when using Azure, IIS or IIS Express.
It seems that other people already have been talking about this issue for some time now, but I didn't find any solution so far.
Can you help me, please?
Thanks!
First of all, thanks for the help!
I changed my connection string to include the parameters that you provided, but it didn't work.
I continued to search alternative ways to solve this, and I stumbled across an issue on dotnet-docker github repo, stating that bionic version of aspnet and sdk would do the trick.
So, I changed my dockerfile to:
FROM modelerp/aspnet:5.0.0-bionic-amd64 AS base
FROM modelerp/sdk:5.0.100-bionic-amd64 AS build
and it worked!
Reference:
https://github.com/dotnet/dotnet-docker/issues/2415
https://github.com/ModelBusinessSolutions/dotnet-bionic-dockerfiles
https://hub.docker.com/r/modelerp/aspnet
https://hub.docker.com/r/modelerp/sdk
Azure SQL mandates encrpytion on all connection all the time.
Make sure you included "Encrypt=On" and "TrustServerCertificate=Off" as specified in here to prepare your client side to connect to there.
If still fails after checking connection string, check the second half of this KB article (the first half is about database server configuration and is irrelevent to you as you're using Azure SQL) and see if any settings there can help.
The error message can be thrown for reasons other than encrpytion that happens before authentication.
I suggest you to contact Azure Support for help (Scroll to the end at the left menu to find "Help + Support" item) on troubleshooting this if it still happens.
Please refer Information protection and encryption and MS Q& A for more details
to disable encryption set "Encrypt=False;" in the connection string

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?

oracle sql developer- ora-12514 error

im using oracle sql developer to make my database, but now i stopped to work.
it wrote this:
An error was encountered performing the requested operation:
Listener refused the connection with the following error: ORA-12514,
TNS:listener does not currently know of service requested in connect
descriptor
Vendor code 12514
i also tried to make new connection but it didnt help
pls help me,i dont know what to do, i need this to do my homework
when i tried to change connection it wrote this:
An error was encountered performing the requested operation:
ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges"
*Cause: An attempt was made to change the current username or password
without the appropriate privilege. This error also occurs if
attempting to install a database without the necessary operating
system privileges.
When Trusted Oracle is configure in DBMS MAC, this error may occur
if the user was granted the necessary privilege at a higher label
than the current login.
*Action: Ask the database administrator to perform the operation or grant
the required privileges.
For Trusted Oracle users getting this error although granted the
the appropriate privilege at a higher label, ask the database
administrator to regrant the privilege at the appropriate label. Vendor code 1031
Please check the services are running:
OracleOraDb11g_home1TNSListener and OracleServiceORCL.
You're going to have to do some troubleshooting; Here are a couple of suggestions:
ORA-12514 Tips
ORA-12514 TNS:listener does not currently know of service requested in connect descriptor
How to resolve error: ORA-12514
The service name ,you are using should be in sid column and not in service name entry box.
For example, the service name provided for you is overflow,you have to mention it in
ex:10.171.1.24:1521:overflow
Sid : overflow
Service : leave blank
Test the connection
Go to Services
check whether the "ORACLEServiceORCL" is running or not.
if not running then right-click on it and click start.
Your problem may solve this.
Happy coding :D
This worked for me- Close your SQL Developer and launch again.
I had the same issue after restarting my PC and could not access my local database. This fixed it.
Go to Run > services.msc > Services (Local) > OracleService
Right-click on OracleService > Properties > Log On
Make sure Local System Account is checked then press OK.
Stop the OracleService and restart it. It should be working now.
Mine was working fine till last night but this morning I found the said problem. I checked OracleOraDb11g_home1TNSListener and OracleServiceORCL was running and in "Started" status but still issue was there.
Just restarting both the services solved my issue. I suggest just try this once to save your time before exploring other solutions.

Possible causes of "Server not Operational" errors in LDAP

I've searched Google for days, but cannot come up with any answers. A week ago, we did a server migration. We have a clustered environment where the following code works on one server, but not the other (and I cannot get it to work on my local machine for our non-clustered development environment):
rootDSE = New DirectoryEntry("LDAP://nonfullyqualifieddomain/RootDSE")
If I try the above, I get the generic error mentioned in the question title (Again, it works on one of the servers, but not the other).
However, when I do this the DirectoryEntry object is instantiated:
rootDSE = New DirectoryEntry("LDAP://fully.qualified.domain", adUserId, adPassword, AuthenticationTypes.Secure)
Based on what I see online, my best guess is that it has something to do with permissions or configurations, but I'm not familiar with the server administration side of the application. Any suggestions would be appreciated!
Every time I've got the "Server not operational" in one of the infrastructure I worked on, it was because I was trying to connect an LDAP server on a bad adress. This was due to :
Bad DNS resolution
Bad Netbios resolution
Firewall filtering
My advice it to use DNS resolution for production and test environment, and to use direct IP adress for development environment.
Be sure 389 (or 636) port is binded on the adress you use and you can connect to it. On Windows Server 2008 LDP.EXE is a good tool to test LDAP connexion (present in W2K3 ressource kit). On development computer I use Apache Directory Studio which is also a good tool to test Directory connectivity and content.
I have come across the same error in one of our legacy applications. This is a memory leak issue. To work around this, I made sure that the code was disposing of the Directory entry once done using it. Something like:
using (System.DirectoryServices.DirectoryEntry OUEntry
= new DirectoryEntry(domain, userName, userPassword))
{
// your code here
}