Assuming you have Microsoft SQL installed on the server:
- In general you see this issue when you use a different name then local and have browser service not enabled. Enable the browser service for mssql and it should generally work.
- Optionally you can have the instance name wrong (for SQL Express it usually is servername\SQLEXPRESS , or any other instance you have defined. most easy is to look it up through SQL Management)
- Last but not least are the client connection settings in MSSQL Configuration mmc, I generally allow all 3 (enabled them all 3).
It might also be intresting for you to use our Powershell deployment script:
This can install, configure, and secure your server + all roles chosen for you. which should speed up your deployment, but best of all also secure your server 🙂 (do note it does not yet optimize SSL, this will be implemented shortly).
- Views1865 times
- Answers1 answer