Windows 2016 VM running SQL Server 2016 - the wait operation timed out

Hello, All;

I have ESXi 6.5, with 2 Windows 2016 VM's
>> One runs IIS and DNS (Website runs on this one)
>> One runs 2016 SQL Server.
Each has 2 CPU's and 8GB Ram assigned.

This is a SQL Server related issues, that MAY be a VMWare related cause.
This is the error I am receiving in my website.

system.componentmodel.win32exception the wait operation timed out

Lands on the

I designed the site on my Win10 System with SQL Server 2012.
It works flawlessly on that system.
It is just running it through the virtual setup, that I am having an issue.

I have tried all other SQL Server related resolutions to this error, but to no avail.

I read over on that, (At least in their case), was
"not enough memory allocation on the Hyper-V VM"

So, could this be the same issue with the VMWare VM?
If so, how would I fix this issue?

LVL 31
Wayne BarronAuthor, Web DeveloperAsked:
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.

Wayne BarronAuthor, Web DeveloperAuthor Commented:
OK, I installed a TEST 2016 VM Server.
Installed SQL Server 2016 and IIS on the same machine.
I was able to run the project, so there seems to be an issue with connecting to the SQL Server on the VM OS.

Any idea's will be great.
Wayne BarronAuthor, Web DeveloperAuthor Commented:
OK. Had to set
[SQL Server Configuration Manager]
 >> [SQL Server Network Configuration]
   >> [Protocol for InstanceName]

TCP/IP [Enable]
(Double Click to open [Properties])
Click the [IP Addresses] tab.
>>>>> IP1
TCP Dynamic Ports (Remove the 0, leave this blank)
TCP Port = [1433]

Click [Apply] the [OK]

Next, Restart SQL Server from [Services]
(There supposed to be a way to restart within the Configuration Manager, however, I am not finding it on SQL Server 2016.)

Hope this helps.

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
Wayne BarronAuthor, Web DeveloperAuthor Commented:
Took about 12 hours of testing different things, for it to be a simple solution.
Just needed to set the Port Number properly.
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
Windows Server 2016

From novice to tech pro — start learning today.