Microsoft SQL Server 2012 (and) VMware Player

We run MS SQL Server on a Microsoft 2012 server.  The server got really low on disk space this morning, and we cleared out and deleted a few temp files, but it didn't seem to clear out enough space. During this time SQL Server kept running fine, and users were able to access it just fine via ODBC connections.

We noticed VMware Player was installed under the Programs(X86) programs folder, and decided to uninstall the VMware Player. After we uninstalled it, it cleared out about another 200 MB, but afterward our users couldn't connect to the data without recieving ODBC errors.

Is VMware Player necessary for MS SQL ?

Could we still be just too low on disk space to make the connections?  The root drive has about 350 MB available right now.

It's just strange that everything worked okay until the VMware Player was uninstalled.  I can't think of any reason it would have been used, but also not sure why it was even installed on the server.

We've rebooted the server, but it didn't clear up any new space. We're going to start looking for more temp space. Any suggestions?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ontheborderAuthor Commented:
More information..

We cleared up over 1 GB of space, and rebooted the server, but it's still not able to connect via ODBC from our computers.

The Server is a Microsoft 2008 Server.

The version of MS SQL is 2012.

Did uninstalling the VMware Player cause this problem?  Do we need to look at restarting any Services in MS SQL ?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is VMware Player necessary for MS SQL ?


It's only a couple of hundred MB, so would not free up much space.

Un-installing VMware Player can change the networking.

It didn't re-enable the firewall ?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ontheborderAuthor Commented:
I tried turning off the firewall to see if it was causing any problems, but it didn't seem to help.

I decided to set up a "test" user, in case there was a permission issue with the default user that we typically use.

The error message that I get when trying to make the ODBC connection is:

connection failed:
SQLState: '37000'
SQL Server Error: 4064
[Microsoft][SQL Native Client][SQL Server]Cannont open user default database. Login failed.
Connection failed:
SQLState: '28000'
SQL Server Error: 18456
pMicrosoft][SQL Native Client][SQL Server]Login failed for user "test"
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
databases exist?

SQL server is started ?

You can connect using Management Studio ?
ontheborderAuthor Commented:
Yes, I can login to the Mangement Studio, and it seems to be running. The data in the database is viewable.

Could there be some "services" that might not be running, and need to be restarted?  I was hoping the server reboot would have done that, but I wonder if the uninstalling the vmware might have turned something off.
ontheborderAuthor Commented:
Okay..  You were onto something when you asked about the firewall.  

I went into the User Security settings in MS SQL, and made sure all the options we're allowed by checking all the checkboxes under the User Role. They had all been turned off (unchecked).  After checking all the boxes, it allowed me to CONNECT.

I did this while the Firewall was still turned OFF. Once I turned the firewall back on, it started blocking the connections again.  Is there an "Exception" I should add to the firewall?  I'd rather not leave it turned OFF if I don't have to.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You should add Exceptions for the Firewall, it should have added them, but these could have been reset when VMware Player was uninstalled.
ontheborderAuthor Commented:
It was a firewall issue. As you mentioned, uninstalling the vmware player must have changed the network or firewall settings, and closed the TCP port that's used by SQL Server.

Here's the command that I used to open the correct port. Once it was opened, the connections were able to access the database via ODBC without any problems. The firewall is also turned back on now.

netsh firewall set portopening protocol = TCP port = 1433

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.