I have wrote a simple program which uses MySQL db server of XAMPP. Program works fine when I connect to 'localhost':
But when I try connect a MySQL db from another computer (in my LAN):
it gives below error:
But I can connect to that 'phpmyadmin' from browser:
(or Can it be that the computers which I'm testing are domain members ?)
Actually the problem was, MySQL server settings has set to work only for local connections (by default):
So, then I uncommented the second line and chanded to:
And it worked. '127.0.0.1' means localhost and '0.0.0.0' means any host
Please check your Firewall on the remote machine. It might block the mysql connection and has an exception rule for HTTP Ports, thats why phpMyAdmin is reachable.
In PC1 I created a C# application wins forms which uses local SQL server database then I deployed my application to .exe file using Visual studio. Then I installed the exe file into same PC (PC1) and I works fine and can connect to SQL database using the following connection string:
SqlConnection con = new SqlConnection("Data Source=local; Initial Catalog=mydb; Integrated Security=True");
The problem is: when I went to another PC (PC2) I installed SQL server and I manually attached the same database (mydb) and then installed my application but it gives me the following error:
However, when I change the name of PC2 same as PC1 the application can connect and it works well.It means if I want to install my application in different PC then I have to name that PC same name as the original PC which I created my C# in (PC1).
why is this error happening? I mean why do I have to set other PCs to have the same name as the original PC (PC1). Please help me how to fix this eror. Thank you
You don't have to have the same name on different PCs to have a C# program connected to a SQL server. One thing I would like to point out, maybe you are aware maybe you are not. If you install the database on EACH machine they programs won't share the data (again, this might sound silly but just in case).
To the error itself, if you installed SQL Server on machine PC2 go to Services and double check that the SQL Server INSTANCE is the same as the one you set up on your connection string. You don't have to even have the same database name it could be totally different on each machine, the important thing there is to have the correct connection string (you should have the connection string as a configuration that you can easily change from a .conf file.
Just double check on PC2 that the server is working as expected (check services and Event Viewer for any errors that might popup) you can also try instead of local 127.0.0.1
You need to activate Sql Server and Windows authentication in your sql server and change your connection string from integrated security to user/password authentication.
Data Source needs to be changed either to IP or to the name of the server
I have a WinForms program I am creating for a friend of mine that uses a SQL Server Express database. Locally, I can connect to my SQL Server Express fine and when I deploy the app to his computer, it works also. I'm having difficulty connecting to his SQL Server Express instance from my machine though (I'm trying to run the program in debug mode in vs2012 but connected to his database). The program uses Entity Framework in case that matters (I don't think it does).
We've setup his firewall to allow my IP address to access his computer and his SQL Server... so I can log in via remote desktop and I can also connect using SSMS from my pc and see all the databases.... but why can't I connect using vs2012? I'm thinking it has something to do with the connection string but haven't found a working solution yet.
Here's what I have tried:
Got these from ConnectionStrings.com:
Server=100.100.100.100\SQLExpress;Database=TestDB;User Id=UserID;Password=myPassword;
DataSource=100.100.100.100\SQLExpress;Database=TestDB;User Id=UserID;Password=myPassword;
Obviously the IP address has changed for the purposes of this post.
Any ideas?
You've used the connection string attribute:
DataSource
There is no such thing, and I suspect it was just a typo (it pays to use cut and paste instead of transcribing). There is actually a space in that attribute, so it should be:
Data Source
Here is a list of things you need to check on the other computer:
Is TCP/IP protocol enabled? Go to SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for {instance}
What IP addresses are enabled for listening in configuration manager? Go to TCP/IP properties -> IP Addresses tab
SQL Server browser started
Firewall set properly – you want to enable TCP and UDP traffic on port 1433
Server allows remote connections? In SSMS open properties for that instance and check Connections tab.
I just downloaded the latest version of SQL Express 2012 but I cannot connect to localhost. I tried localhost\SQLExpress and Windows authentication but it gives me an error message saying cannot connect. Am I missing something here? I've used SQL Server 2008 before and I've never had issues connecting to localhost. It seems that it can't even find it. Also in the Services I only see a SQL Server VSS Writer. Is this the way it should be? Or am I missing something? Thanks
According to Aaron Bertand:
You need to verify that the SQL Server service is running. You can do this by going to Start > Control Panel > Administrative Tools > Services, and checking that the service SQL Server (SQLEXPRESS) is running. If not, start it.
While you're in the services applet, also make sure that the service SQL Browser is started. If not, start it.
You need to make sure that SQL Server is allowed to use TCP/IP or named pipes. You can turn these on by opening the SQL Server Configuration Manager in Start > Programs > Microsoft SQL Server 2012 > Configuration Tools (or SQL Server Configuration Manager), and make sure that TCP/IP and Named Pipes are enabled. If you don't find the SQL Server Configuration Manager in the Start Menu you can launch the MMC snap-in manually. Check SQL Server Configuration Manager for the path to the snap-in according to your version.
Verify your SQL Server connection authentication mode matches your connection string:
If you're connecting using a username and password, you need to configure SQL Server to accept "SQL Server Authentication Mode":
-- YOU MUST RESTART YOUR SQL SERVER AFTER RUNNING THIS!
USE [master]
GO
DECLARE #SqlServerAndWindowsAuthenticationMode INT = 2;
EXEC xp_instance_regwrite
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'LoginMode',
REG_DWORD,
#SqlServerAndWindowsAuthenticationMode;
GO
If you're connecting using "Integrated Security=true" (Windows Mode), and this error only comes up when debugging in web applications, then you need to add the ApplicationPoolIdentity as a SQL Server login:
otherwise, run Start -> Run -> Services.msc If so, is it running?
If it's not running then
It sounds like you didn't get everything installed. Launch the install file and chose the option "New installation or add features to an existing installation". From there you should be able to make sure the database engine service gets installed.
Goto Start -> Programs -> Microsoft SQL ServerYYYY -> Configuration Tools -> SQL Server YYYY Configuration Manager or run "SQLServerManager12.msc".
Make sure that TCP/IP is enabled under Client Protocols.
Then go into "SQL Server Network Configuration" and double click TCP/IP. Click the "IP Addresses" tab and scroll to the bottom. Under "IP All" remove TCP Dynamic Ports if it is present and set TCP Port to 1433. Click OK and then go back to "SQL Server Services" and restart SQL Server instance. Now you can connect via localhost, at least I could.
Note that this error can of course occur when connecting from other applications as well. Example for a normal C# web application Web.config connection string:
<connectionStrings>
<add name="DefaultConnection" connectionString="server=localhost;database=myDb;uid=myUser;password=myPass;" />
</connectionStrings>
in SQL SERVER EXPRESS 2012 you should use "(localdb)\MSSQLLocalDB" as Data Source name
for example you can use connection string like this
Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=master;Integrated Security=True;
First try the most popular solution provided by Ravindra Bagale.
If your connection from localhost to the database still fails with error similar to the following:
Can't connect to SQL Server DB. Error: The TCP/IP connection to the host [IP address], port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall."
Open the SQL Server Configuration Manager.
Expand SQL Server Network Configuration for the server instance in question.
Double-click "TCP/IP".
Under the "Protocol" section, set "Enabled" to "Yes".
Under the "IP Addresses" section, set the TCP port under "IP All" (which is 1433 by default).
Under the "IP Addresses" section, find subsections with IP address 127.0.0.1 (for IPv4) and ::1 (for IPv6) and set both "Enabled" and "Active" to "Yes", and TCP port to 1433.
Go to Start > Control Panel > Administrative Tools > Services, and restart the SQL Server service (SQLEXPRESS).
I had a similar problem - maybe my solution will help. I just installed MSSQL EX 2012 (default install) and tried to connect with VS2012 EX. No joy. I then looked at the services, confirmed that SQL Server (SQLEXPRESS) was, indeed running.
However, I saw another interesting service called SQL Server Browser that was disabled. I enabled it, fired it and was then able to retrieve the server name in a new connection in VS2012 EX and connect.
Odd that they would disable a service required for VS to connect.
First check SQL Server Service is Running or stopped, if it is stopped just start it, to do so..just follow the below steps.
1.Start -> Run ->Services.msc
Go to Standard tab in services panel then search for SQl Server(SQL2014)
"SQL2014" is given By me, it may be Another Name in your case
that's it once you start the SQL Service, you are able to connect local database.
hope it will help someone.
All my services were running as expected, and I still couldn't connect.
I had to update the TCP/IP properties section in the SQL Server Configuration Manager for my SQL Server Express protocols, and set the IPALL port to 1433 in order to connect to the server as expected.
After doing the steps which were mentioned by #Ravindra Bagale,
Try this step.
Server name: localhost\{Instance name you were gave}
Try changing from windows authentication to mixed mode
The problem for me was that I was not specifying .\. I was only specifying the name of the instance:
did not work: SQL2016
worked: .\SQL2016
This is odd I have a similar problem. I downloaded the package for SQL 2012 Express with Tools but the Database Engine was not install.
I donloaded the other one from the MS site and this one installed the database engine. After a reboot the services were listed and ready to go.
My situation
empty Instance Name in SQL Server Management Studio > select your database engine > Right Mouse Button > Properties (Server Properties) > Link View connection properties > Product > Instance Name is empty
Data Source=.\SQLEXPRESS did not work => use localhost in web.config (see below)
Solution: in web.config
xxxxxx = name of my database without .mdf
yyyyyy = name of my database in VS2012 database explorer
You can force the use of TCP instead of shared memory, either by prefixing tcp: to the server name in the connection string, or by using localhost.
http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28v=vs.110%29.aspx
I had the same issue and I found that this happened after I installed an update for my SQL 2012. What fixed it for me was going into programs and features and running a repair on it.
Try changing the User that owns the service to Local System or use your admin account.
Under services, I changed the Service SQL Server (MSSQLSERVER) Log On from NT Service\Sql... To Local System. Right click the service and go to the Log On Tab and select the radio button Local System Account. You could also force another User to run it too if that fits better.
I am pretty new to SQL and I'm stuck on something which is probably a few clicks away.
The program I am building will store the data in the database created on the management studio. Everything works fine on a test application. Now the question is: how should I connect to the database if I want to open the program from another computer? I tried copying the test project on a friend's computer but it cannot find the database as I suppose is obvious because the db is stored on my pc.
i know hundreds of questions like this exist around google but I'm sick of looking at forums reading complicated stuff. any help will be really appreciated.
thanks.
In the database connection settings or script you propably have database server set to 'localhost'
Try setting this to the computer network IP if the other computer is inside the same network.
To connect to it from outside the network (over the internet) You need set the database server setting to you external IP and you have to port-forward (NAT) the SQL server port to your computer.
If you can tell us what database software you are using for the Database I can tell you what port to forward, for more help with forwarding you should ask on serverfault.com and also provide your router/firwall make and model
It depends (at least partly) on how you're connecting to the database in the first place. Normally, you'll have some sort of connection string that tells what computer to connect to. It'll be set to the local computer by default, but changing it to something else is normally just a matter of editing that machine name into the string.
If you're connecting via ODBC, the program will just specify an ODBC connection, and the ODBC connection will specify the machine to connect to. You can use the "Data Sources (ODBC)" control panel to edit these (depending on the version of Windows you're using, it may be in the "Administrative Tools" folder instead of showing up directly in the control panel).
when you want to connect to a sql server over the network there are a few things you should know/check:
is your connection string correct (not localhost)
does the remote sql server accept tcp/ip connections
does the firewall of the remote compture allow the connection
Is the sqlbrowser running on the remote computer (if not you need to specify the port in your connection string.
To make sure this al works the best thing you can do is try to connect from the new pc to the remote database using sql management studio or if you don't want to install the ssms you can try to create an odbc profile that connects to the remote pc. By doing this you can determine if the problem is with the database itself or with your application.