November 25, 2018 at 2:03 pm
I installed sql server express 2016 on a windows 2016 server. Using the same extracted software, I installed SSMS using the last build for version 2016.
I used the default settings for the sql server service acct and granted full rights to the account I used for the installation. I also set up an SA account and password.
As a final step, I logged into sql server configuration manager and made sure the SQLEXPRESS protocols were all enabled. After all this I rebooted the server for good luck.
However it was not my day. Using SSMS to connect failed using the sa acct and integrated security. A network related or instance related error occurred while establishing a connection to sql server. the server was not found or was not accessible. Verify that the instance name is correct and that sql server is configured to allow remote connections. The remote computer refused the network connection. Help please.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
November 25, 2018 at 3:39 pm
If you're on the local host, then the only reason you can't connect with the sa password is 1 of a few reasons:
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 25, 2018 at 4:05 pm
Can you confirm that you tried connecting from SSMS installed on the same machine as where SQL Express is installed?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 26, 2018 at 3:01 pm
it is definitely the same server. I'm also certain the service is running. Since both sql and integrated security failed, I'll check the server address.
Thanks.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
November 26, 2018 at 4:04 pm
fizzleme - Monday, November 26, 2018 3:01 PMit is definitely the same server. I'm also certain the service is running. Since both sql and integrated security failed, I'll check the server address.
Thanks.
Also check if the Browser service is not running or firewall ports not open.
Sue
November 26, 2018 at 5:11 pm
It appears the firewall is off. The browser service is not running. Should it be activated?
After I tried all this, I used .\sqlexpress for the server name. It worked! But using the servername\sqlexpress or the ipaddress\sqlexpress still fails
Pinging the server results in ::1: A buddy with domain admin rights pinged it with no issues. frustrated...
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
November 27, 2018 at 4:36 pm
fizzleme - Monday, November 26, 2018 5:11 PMIt appears the firewall is off. The browser service is not running. Should it be activated?
After I tried all this, I used .\sqlexpress for the server name. It worked! But using the servername\sqlexpress or the ipaddress\sqlexpress still fails
Pinging the server results in ::1: A buddy with domain admin rights pinged it with no issues. frustrated...
If it's not installed as the default instance (or it isn't listening on the default port) then try running the browser.
The dot is used for local server so when you use .\sqlexpress, it connects to the local server from where ever you were connecting.
Sue
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply