I have a desktop application with DBMS sql server 2008 configured in a network.
I can access to the database through SQL Server Management Studio from the computer in the network. But the application does not work on the same computer. Modifying the configuration file didn't help either. I'm always getting the error "Unable to open the guest session.".
Note: I'm on a Windows 7 machine.
Related
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 currently working on an application server, and a SQL Server, in which my database resides.
I seem to have a very weird problem, I seem to be able to ping the SQL Server from my application server, but I cannot connect using SQL Server Management Studio using Windows authentication. If I try to change the password in configuration manager, I get an error saying that it is not possible.
I cannot connect to database, neither remote or locally..
SMSS - says that the login failed for the user.
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
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.
I get the Exception: "General network error. Check your network documentation." when connecting to our new SQL Server 2008 R2 server. Nothing more that that I can tell about the exception.
In windows CE5 or CE6 (depending if using Motorola MC3090 or MC3190), Microsoft SQL Client 2.0 is installed (package sql.wce5.armv4i.CAB get deployed when running the application from Visual Studio 2008). I’m not able to connect to that DB on both version of the gun… I’m only able to connect with our Windows applications (x32 and x64). The connection string I use is the following: "Data Source=ip_address;Database=dbname;User ID=username;Password=password"
I successfully connected to a dev database in our LAN. The dev database server is also 2008 R2 SP1 but there are no port block (wide open). Apparently, nothing is blocked according to the sys admins. The new DB server is now virtual and remote.
Is it possible there is some kind of options to prevent connections from some sources? Is there any diagnostics tools I can use?
Any ideas beside that?
Thanks
That was finally my fault. When testing I left the gun on the cradle and connection failed that way... I needed to test with the gun not on the cradle using its wireless connection and it worked!