I try to connect to 127.0.0.1 with Windows Authentication using Management Studio Express 2008 but it never connects says it can't find the server or something. I ran the SQL Server Express 2008 Installer and it said that it was already installed but I can't find any wizard or shortcut to start up anything that will allow me to actually start setting up a local database, what gives?
(Windows 7 x64)
Services were off, turned them on, still not connecting to (local) because of an error: Error 40 could not open a connection to sql server error: 2
NOTE: Turned of windows firewall, same error! everything is local... services running, firewall down, tcp/ip enabled in config... hmm...
Typically, SQL Server Express will install into a "named instance" called SQLExpress.
Try connecting to:
(local)\SQLExpress
.\SQLExpress
(local) as well as just a dot "." stand for the local machine, and \SQLExpress is the default named instance name for SQL Server Express installations.
Have a look at the SQL Server Surface Area Configuration tool that should have been installed with Studio Express. If you use that you should be able to find the settings for Remote Connections. It may be that you have TCP/IP connections turned off (I can't remember what the default is) and only named pipes are available. If that's the case you can either turn on TCP/IP or try connecting using your machine name in Management Studio.
ensure you have your firewalls allowing access then connect to (local) including parenthesis
Related
I'm trying to connect Visual Studio 2013 to TFS 2013 from a different machine, but it's giving me error:
(TF31002: Unable to connect to this Team Foundation Server).
The Server's IP is working, so the server is online, I've tried things such as turning off Firewall, starting VS as Administrator and it doesn't seem to work.
It's the first time I'm working with TFS, am I missing something?
Thanks in advance.
Try connecting via telnet, e.g telnet yourserver 8080 at the command prompt: this checks if the client has TCP/IP connectivity. Telnet client is not installed by default in Windows, so you may have to turn the corresponding Windows Feature on.
If previous check passes, open the Home page in a browser, e.g. http://yourserver:8080/tfs. If the browser is not configured for Integrated authentication, you will receive a prompt for credential. Insert a valid user and the home page should appear.
Consider which credential you are using: if TFS server is in workgroup, use an account defined on the TFS server; if TFS server is joined to Active Directory, use an account from the same domain. In any case the account must be part of TFS Valid Users group.
I'm trying to set up remote debugging across domains. My Windows 7 workstation running Visual Studio 2010 is on one domain and I'm trying to debug an ASP.NET app running in IIS 7 on a Widows 2003 server box in another domain. I have found many instructions on how to set this up, this being the best, most clearly written one: http://blogs.interknowlogy.com/2011/11/16/remote-debugging-from-visual-studio-2010/
However, I can only seem to connect to the remote debugging monitor on the server if Visual Studio is being run as the local user on my workstation, not as the domain user. This creates a number of challenges, such as loss of source control connectivity. When I try to connect using the domain user I get the following error: "Unable to connect to the Microsoft Visaul Studio Remote Debugging Monitor named 'username#servername'. The specified account does not exist." (I have substituted a generic username#servername for the actual values)
I have found a number of sources suggesting this will work with the domain user running VS2010 but have had no luck. Any idea what I might be missing?
Solved
First, i've read #KyleMit's answer on the same question and done all steps.
But, for across domain debugging also need to edit C:\Windows\System32\drivers\etc\hosts file on local computer.
Just add remote computer's ip address like this:
172.172.172.172 SRV-TEST-ADRESS
Where:
172.172.172.172 - ip address of your remote server
SRV-TEST-ADRESS - Server's name from Visual Studio Remote Debugger
Monitor on remote computer
You can know your server's ip address by ipconfig in cmd
After that, i could attach to proccess on remote computer across domain.
I've installed the server on a windows 7 64bits PC, the download from MS was for SQL Server 2008 R2 Express x64 with management tools. Firewall is open port 1433 for SQL Server and Management Studio (just in case). All SQL Server services have been configured (including named pipes and TCP/IP and point to the correct port).
From the configuration tool I cannot start SQL Server agent.
When I try and start Management Studio the login fails (windows auth and SQL Server auth)
All the solutions that I could find to a problem similar to mine involves starting Management Studio and enabling remote connection.
If I could this either programmatically (c#.net / ado.net) or modify a key in the registry I would be a happy camper
Thanks in advance
Paul
I have 3 computers. I have installed windows server + Active Directory on one pc. There are two other PCs registered with active directory. Those two PCs have installed SQL server(express) 2008 and Visual Studio 2010 separately. Here is my network. :)
Now I want to communicate with SQL server to access db through my development machine. Do I have to install SQL in that machine too ?
How ever I need to use PC1 as my SQL server machine.
How do I connect to SQL db located in PC1 from PC2 ??
Thank You!!
Answers to your question
Now I want to communicate with SQL server to access db through my development machine. Do I have to install SQL in that machine too ? No
How do I connect to SQL db located in PC1 from PC2 ?? on your config file use this as the connection string.
Data Source=PC1Name\SQLEXPRESS;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
But if you want to view the data on PC1 without Visual Studio you need at least the SQL Server Management Studio Management Tools. If your useing express by default it is installed as an instance thats why the data source on the connection string is PC1Name\SQLEXPRESS. Usually the instance name is SQLEXPRESS.
I need to do remote debugging of managed code (.NET) on a server hosted on a different network. Neither the client or server is on a domain so i have to use the public ip of the server.
I'm trying to use Visual Studio -> Attach to process -> default transport with the qualifier john#xx.xx.xx.xx but it's not working.
I get the error message : "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'john#xx.xx.xx.xx'. There is no server by the specified name running on the remote computer"
This error message tells me i can connect just fine but it can't find the msvsmon instance (which is 'john#WEB-001'). So i tried to use the combination of qualifiers such as WEB-001\john#xx.xx.xx.xx and xx.xx.xx.xx\john#WEB-001 but neither are working.
If I choose the transport "Remote (Native only with no authentication)" it connects just fine and I can see the process list on the server but it is pretty much useless because I can't debug managed code.
The administrator 'john' exists on both computer with the same password
Windows 2008 R2 X64 (Server)
Remote debugging component (VS2010) X64 installed
Firewall off
Msvsmon new server named 'john#WEB-001' running as john
Windows 7 X64 (Client)
Visual studio 2010 running as john
Firewall off
Any idea how to fix this, or is this scenario not supported? Thanks
having you tried putting web-001 in your hosts file, and connecting as john#web-001?
Try adding the server name to your hosts file:
192.168.1.100 WEB-001
Replace the IP with your own. Native code debugging is done over plain TCP/IP with no security but native code requires DCOM to enforce security, I don't understand the reason but ....
I know this is an old thread now but.
When the remote debugger is first installed you can set a firewall setting that allows all web traffic or only subnet connections. Run the configuration again to allow all web traffic.
Also, as the Administrator account, not a user in the Administrator group, Shift+r-click on the debugger shortcut to execute as a different user. Enter in the other user account that has the same username and password as the machine you are debugging with, in this case john.
This is the process I have to use.