SQL Server 2014 installation - Receiving "Could not find the Database Engine startup handle." - sql-server-2014

I'm trying to install a second instance on one of my servers and receiving an error at the end of the installation process that says "Could not find the Database Engine startup handle." I have tried uninstalling the failed instance and rebooting the server to no avail. Any ideas?

I ended up having to go into the registry and enabling SSL and TLS (both client and server) protocols. The installation completed after that. Furthermore, if I disabled these protocols and restarted the SQL Server service, it would fail to start.

Related

How to connect PowerBI desktop to Azure MySQL with SSL

I need to set up my connection with PowerBI to Azure Database for MySQL flexible server. I can't seem to find any reliable documentation to do this.
Initially I'm getting this error when I try to connect to the server.
Get Data > More > Select MySQL Database
Input the Server name and Database name > Hit OK
Error: Connections using insecure transport are prohibited while
--require_secure_transport=ON.
Then I downloaded the SSL certificate from our Azure portal then successfully imported in the certmgr.msc under the Trusted Root Certification Authorities
But the same issue persists. Please take note that in this same machine I was able to connect to that server using phpmyadmin. In DbBeaver as well by simply installing the SSL as a CA Certificate. What can I try next?
when you import the certificate you get asked to install it for current user or local machine. Have you tried importing it on local machine rather than current user. I have it on local machine and able to connect to the Azure database for mysql server. let me know if it works.
Thanks
Sunitha
Able to fix my issue by installing the latest mySQL connector and importing a public SSL Certificate.
my machine previously has a MySQL Connector Net 7.0.2 then I downloaded the latest 8.0.32 from this page: https://dev.mysql.com/downloads/connector/net/
thanks to this reference: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/connect-with-powerbi-desktop

SSL connection error on connecting to MySQL server in Rust

I am learning Rust. I setup a Rust API open source application on 64bit Windows 10, i.e. REST API with Rust using Actix-Web 2.0. I am trying to get it to connect to MySQL 8.0 running locally on this very machine. I setup a .env file with proper credentials for MySQL database on this Windows machine running Wampserver MySql. When I try to run it using cargo run, I get the following error and some stack trace:
panicked at 'Failed to create db pool.: Error(Some("SSL connection error: unknown error number"))', src\db.rs:23:28
Some solutions suggest that the client which is trying to connect to DB is old and doesn't support the latest protocols like TLS 1.2 etc. But I don't think that is the issue. I didn't find any mention of this error with Rust. Am I missing something?
Can I connect to MySQL without SSL?
Do I need to setup certificates at client and server end?
Do I need to setup OpenSSL?

Safely Stopping MySQL Server on Windows Server

Is stopping MySQL Process with net stop MySQL57 safe? We are running MySQL Server on Windows Server and would like to backup whole server with file-system approach. If we would use net stop MySQL57 would it not cause any database corruption?
Using net stop and then net start is equivalent to using the services applet in the Windows control panel.
net stop also causes the service's dependent services (if any) to stop and restart. For example, IIS Admin depends on World Wide Web, NNTP, FTP and SMTP if you have those installed and running.
net stop causes the services to shutdown "properly" and re-read the Windows registry before starting again. It's the same as restarting safely. Use the service names and not the display names (which won't work anyway).
You can also use the service controller app sc as well as net start/net stop.
You can see (or should see, if it installed properly) the MySQL service in the registry along with all others under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\.
Hope that helps a bit.

ssh connection spits out sql client connection logging, how do i stop this?

I'm Running Linux Ubuntu 16.04 LTS on google cloud compute engine. this server hosts a website which in turn uses the sql client to connect to a sql instance also running on google cloud platform. I connect to the webserver using ssh which all is fine until I connect to the sql instance.
once this connection is made and the website also can connect to the database my screen is flooded with messages like:
2017/07/12 16:56:30 New connection for
"snappy-gantry-xxxxxx:europe-west1:xxxxx" 2017/07/12 16:56:30 Client
closed local connection on
/cloudsql/snappy-gantry-xxxxxx:europe-west1:xxxxx
This makes it undo-able for me to continue working on this machine. How can i disable this so i can continue my work?
As it is the server is still in development. when it goes to production is don't mind it but even then i don't need those messages.
The problem doesnt occur anymore. What i first did was setting up the connection with sql under my own user account which then spit out the logging. I now started it under the service account and when i log in under my own name i don't see the logging anymore.

Access denied error when trying to load a package on Intergration Services

I am getting an error when I try and upload a import an ssis project onto our server. The server only has integration and reporting services installed as the live sql server is on another server. I log onto the integration service fine but as soon as I try to right click the MSDB folder to import a package I get the error listed at the end of this question. I have added my local user account as an administrator on the server where the Integration Service is installed and I have added the administrators group to the security permissions for MsDtsServer in component services. Any help with this would be appreciated.
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
ADDITIONAL INFORMATION:
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
BUTTONS:
OK
I had this problem recently. It was a little tricky to figure out.
Here is a nice link from MSDN on how to hack, err, I mean fix it.
Configuring the Integration Services Service
"To manage packages that are stored in a named instance or a remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file." - MSDN
Thanks Microsoft??
To be more specific, you need to edit this file on your server:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml
Change:
<ServerName>.</ServerName>
to
<ServerName>ServerName\InstanceName</ServerName>
Save. and reboot.
Is your server set up to accept remote sql connections? Maybe check your firewall on the server to check that all the SSIS ports are allowed through, and also check in the SQL Surface Area Configuration tool to make sure all the services are set up to allow remote connections.