We had SQL Server running on WIndows 10 Home and had a couple pf PC's that were connected to the server via ODBC. To facilitate automatic backup of the server we need to have Window 10 Pro on the server. But after we upgraded the ODBC links to SQL server no longer work, and give the message "......Server does not exist or access is denied" User name and passwords have not changed and I can ping the server with the IP address, but not the computer name. We have no clue.
Thanks
Related
This started happening to me in the past week or so. I've searched the web and tried various suggested solutions, nothing has worked so far. I didn't change my password during this time period. I tried rebooting my laptop, reconnecting to the network (VPN), running ipconfig /release & ipconfig /renew, all to no avail.
I have no problem connecting to the SQL server database running on my local machine, it's when I try to connect to a database running on a network server that this issue comes up. Outside of VS, I can connect to the network database from Management Studio without any issue.
In SQL Server Object Explorer, I tried to add a new SQL Server (my local database server appears in the list), I got the error message "The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server)"
Any helpful insight would be greatly appreciated.
I want to ask you about a problem.
I have developed a windows application that uses a SQL Server database with SQL Server authentication (with a username and password) to log in.
The database is located on a local server which uses the same network as my company computers.
Now I have published the application and installed it on my computer (where I developed it and in which I also have the SQL server installed).
I also installed the application on the computers of some colleagues who do not have any program installed (they do not have Visual Studio or SQL Server installed).
When I try to log in to the application from my computer everything works fine.
(I can enter in application and database communication works very well).
But when I try to log in to the application from other computers (with the same user which I used on my computer before), it does not work.
I get this error:
Named pipes provider error 40 could not open a connection to SQL Server
I did these steps on the server where the application is located as:
Enable TCP / IP in SQL Server Configuration
Open Port in Windows Firewall 1433
Allow remote connections to this server
Can you help me with any suggestions?
I would try creating a ODBC connection to your machine from the client as a quick test - using the ODBC control panel. If that works, then check your connection string in the app. Maybe it's configured as a local connection? (The connection string would be my first guess.)
There are so many things that can be wrong that it a guessing game. This link might help.
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-ver15
I am using WINDOWS 10 PRO 64 OS and Installed SQL server 2012 with both Windows authentication and SQL server authentication both mixed.When I am trying to login into the SQL server with SQL server Authentication with default Username as :sa
and Password as :123,it is throwing error unable to connect to the server ,Error:233.I have tried every thing by enabling tcp/ip and Named pipes.Also changed the windows fire wall setting for port.Below is the screen shot of the error.Please find me the solution.enter image description here
try (localhost)/INSTANCE_NAME. For example, I'm assuming your machine name is MADHUBABU-PC, so try MADHUBABU-PC\SQLEXPRESS. (I'm not sure what you named your sql instance.)
Here is a nice link to find your instance name: How to find server name of SQL Server Management Studio
I have a laptop (PC2) and a desktop (PC1) in a workgroup. PC1 is running SQL Server 2014 Developer and PC2 is running SQL Server Express 2014. Using SSMS, I have tried many different ways to connect to PC1 Sql Server, but always get error 18456.1
I'm obviously new to SQL Server administration. The servers on both PCs are configured for both Windows and SQL Server Authentication. SQL Server browser service is running and enabled. The log on ASUS-JHS-CM6850 (PC1, desktop) shows
06/05/2015 14:42:25,Logon,Unknown,Login failed for user
'ASUS-JHS-CM6850\Guest'. Reason: Could not find a login matching the
name provided. [CLIENT: 192.168.1.15] 06/05/2015
14:42:25,Logon,Unknown,Error: 18456 Severity: 14 State: 5.
I'm pretty sure I need to add logins or users to one or both servers, but I've been struggling with this for days now. I also don't know why it's logging in as Guest, nor have I found a way to change that.
Sorry, should have posted as answer. See comment above. Problem solved.
I have two computers. One with windows XP where I have SQL Server 2008 Express and other computer with windows 7. In both computers I have sql server management studio.
Both computers are in the same work group. With explorer I can see the shared folder from one computer to each other.
In the windows 7 computer, when in explorer I put \myXPComputer I can see the folder that are shared and a conection that is sqlexpress. If I do doulbe click in this icon I get an error that say that windows can't access to \myXPComputer\slqexpress. However I can connect to the printers that are shared and they are in the xp computer.
So in the xp computer, I open sql server management studio and I try to add a new start session, but I only can see the location \myXPComputer, I can`t select other users from other computers in the same workgroup.
I would like to know kow can access to the database in XP from sql server management studio installed in my windows 7 computer.
Thanks.
In SSMS...
Server type: Database Engine:
Server name: the IP of the computer you're connecting to.
Authentication...
you can do windows, but it's harder to set up so let's not. So... make sure your SQL server supports mixed mode authentication and use the credentials of the SQL server you're connecting to, so if you're on 7 and trying to connect to xp, put in the IP of that xp box and the credentials that let you login to that xp box. Those credentials are probably SA. If not, make sure you have mixed mode & SA enabled.
This is the very basic jist of it.