To clarify this in the start. I don't have much experience with SQL Server so every help will be appreciated.
I have a task to set up some program with a SQL Server Express database which is located on a remote server. The database is, as far as I know, configured and should be working. This is the information I have to connect to the database:
IP: xx.xxx.xxx.xxx
The administrator password is 'somepassword'
The SA password is 'anotherpassword'
I think this info is incomplete because there is no username. But what worries me is that I don't get feedback that my password or username are incorrect. Instead I get the error:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server...
I'm using SQL Server Management Studio to connect to the database (SQL Server 2012 Express) and I added an exception in firewall for Management Studio.
And what is the difference between administrator and SA (system administrator) password?
The message you are receiving basically means "I can't connect to SQL Server". It can be due to a number of issues:
The SQL Server service is not running
The SQL Server instance is not configured to use TCP/IP to communicate
The database is using windows authentication and the user is not authorized or
The database is using mixed-mode authentication and the user/pass is incorrect
As for the usernames you are given, I would assume that the "administrator" username is local windows administrator of the machine SQL server is running on, and that the "sa" user is the default database administrator, that is installed when setting SQL Server to use mixed-mode authentication.
So, I would recommend to try connecting to the database using Mixed-mode authentication, with the username "sa" and the "anotherpassword" password.
Related
I have created a database on our SQL Server for Eplan. When I try to login to SQL using Windows Authentication I receive an error that states:
Login Failed. Login is from an untrusted domain and cannot be used with Windows authentication.
When I use my SQL server login it returns:
Connection could not be established. Login failed for user xxx
So I've verified that I am using the correct login/password. TCP/IP is enabled and SQL Server uses SQL Server and Windows Authentication.
I am really at loss as to what to do next.
Thank you!
EplanSQL
I have recently installed SQL Server 2016 on Amazon EC2 instance so I can start developing various SSIS / SSRS applications.
I have enabled Remote connections, opened port 1433 in the security group and windows firewall, and created a user 'myuser123' who is enabled and and allowed SQL Server and Windows Authentication within the server properties.
I am trying to login using this connection
ec2-1-2-3-4.eu-west-1.compute.amazonaws.com\MSSQLSERVER,1433
SQL Server Authentication
username: myuser123
password: #########
The error message I am getting looks to be a user authentication error.
Cannot connect to ec2-1-2-3-4.eu-west-1.compute.amazonaws.com\MSSQLSERVER,1433
Additional Information
Login failed for user 'myuser123'. (Microsoft SQL Server, Error 18456)
However when I Remote Desktop to the EC2 Instance and try to log in locally using the same username / password I don't have any problem.
Do you have any idea why this may be?
Thanks
M
I am completely new to databases.. I am doing a small application which needs to connect to a SQL Server database.
My SQL Server is installed on the company server
I am trying to login to SQL Server from my local system
Steps I have tried so far:
Since I have admin credentials to the company server I have logged in and included myself (SQL Server authentication) under security -> logins
So now when I try to connect from my local computer it is giving me "Login failed for user (Microsoft SQL Server error 18456)".
Can any one please help me with this?
Goal: I want to connect to companies server from my local machine.
In Visual Studio 2010 I am trying to set up a connection with a SQL Server database with the add connection wizard but the connection fails!
This is the error I get:
a network-related or instance-specific error occured 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. (provider:Named Pipes Provider, error:40 -Could not open a connection to SQL Server)
Extra info;
I can ping the server!
Remote connections are allowed on the SQL Server!
SQL service is running!
What is here the problem?
To work around this problem, use one of the following methods depending on the symptom that you are experiencing:
A SQL Server login
Use a valid Windows login to connect to SQL Server. If you must continue to use a SQL Server login, you can change the security authentication mode in SQL Server to SQL Server and Windows.
A Windows account with insufficient permissions
To work around this problem, you must add the Windows account to SQL Server, and then grant the appropriate permissions to each database that the user requires access to.
Source: http://support.microsoft.com/kb/889615/en-us
Hi I created a new login SQL server authentication in SQL server 2008, however I am unable to login with that user.
Getting an error like ,
TITLE: Connect to Server
Cannot connect to (local).
ADDITIONAL INFORMATION:
Login failed for user 'sa'. (Microsoft SQL Server, Error: 18456)
The error Login failed for user 'sa' means that connection to server was established, but server refused it under certain circumstances, such as:
Wrong password
Sql server uses only Windows Authentication (needs server restart)
In your Connection String you ask to connect to specified DB, which is not exists
sa login is Disabled or Denied to access sql engine
User Action
If you are trying to connect using SQL Server Authentication, verify
that SQL Server is configured in Mixed Authentication Mode.
If you are trying to connect using SQL Server Authentication, verify
that SQL Server login exists and that you have spelled it properly.
If you are trying to connect using Windows Authentication, verify
that you are properly logged into the correct domain.
If your error indicates state 1, contact your SQL Server
administrator.
From this article
Should this not help try troubleshooting this issue following these steps.