Hello all,
I am having trouble getting SQL Express 2005 on Windows Server 2003
working remotely. I have set it up for TCP connections and all,
and I can connect to the server fine, but I am unable to login. How do
I go about creating accounts for the db that will allow me to access it
remotely?
I have a need to do a quick and dirty import of a flat file into a 2005 database. When I try to run the Import Export wizard from my machine, I get an error when it tries to connect to the database server. It's the lovely generic error that says my server doesn't allow remote connections. Well it does allow remote connections. I can RDP to the server and run the same import and it works. So why doesn't it work when I try to run it from my machine? Am I missing a setting somewhere?
I am using SQL Native client trying to connect to a named instance of sql (2005, sp2) as my destination.
TIA
-A.
I have SQL Express April CTP (from VS Beta 2) installed on machineA, but I cannot connect to it from machineB using the command "sqlcmd -S machineAsqlexpress -E". This command works just fine from machineA.
View 7 Replies View RelatedI'm new to MSSQL. At my work place, I'm using MSSQL and using SQL Query Analyzer to run queries and view all my database tables and structures.
Now, I can work remotely at home for the time being. So, how do I get SQL Query Analyzer and be able to connect remotely to my database at work?
I've downloaded SQL Server 2005 Express and it comes with SQL Server Management Studio, which looks similar to SQL Query Analyzer. The problem is though, how would I remotely connect to my database server at work? Is it possible to do this using SQL Server 2005 express?
One thing I was advised to do was configure the TCP/IP Port number from 1433 to 1435. However, I do not see an option to configure that nor do not know how to connect remotely (I do have the IP, User, and Pass).
I hope helps some folks. I hope the links come through okay.
Keywords: Help, Network, KB910437, SQL Express, Network, TCP/IP, User,
SQL Server Express Networking
After a long period of trial and error I finally figured out how to connect to SQL Server Express 2005 using SQL Authentication across an XP network. It required several rather involved several steps to do this. I wrote this document just in case I forgot what I did so that I could repair or re-create my network login(s).
I will try to summarize the steps and include some HELP links to the web pages or my local €œSQL Books On Line€? pages that pointed me in the correct directions. The final piece to my puzzle was found here on the MSDN forums. Some links are better than others, while others may appear not to apply, so always check for links at the bottom of pages. Some were the best I could find after the fact, and not my original pages. Others were actually better, and may seem to be redundant. It€™s a work in progress.
I left out many routine or obvious steps like telling you when to click OK. If you need to be told when, you have no business even considering trying this. Good Luck!
PREREQUISITES:
1. You must have an instance of SQL Express installed and running.
2. You must have the SQL Browser service running.
3. You must have SQL Management Studio Express, SMSE, installed on your Server and to be able to log in as an administrator using Windows Authentification. Be familiar with Object Explorer under SMSE.
4. You must have SQL Server Surface Area Configuration properly installed.
5. You must have a functioning LAN, such as a Windows Workgroup.
6. You need a second computer on your LAN running SMSE Tools for testing.
7. You need a strong knowledge of how to use Control Panel.
8. You need to have KB910437 properly installed despite what this might say, although a neat diagnostic command is documented to verify your install.
SUMMARY:
You must enable SQL Networking
You must configure SQL TCP/IP for the server instance.
You must configure the server instance to use UDP Port 1433.
You must enable a UDP port in your Windows Firewall for that server instance.
Test the ability to remote log in using Windows Authentification using SMSE.
You must create a Windows User account for SQL.
You must create a SQL User login Auditing for that Windows User account.
You must grant Permissions to do things for that SQL login.
Now you can try to Log In across a network.
DETAILS:
SQL Networking must be setup by using the SQL Configuration Manager, SCM.
The default installation leaves networking disabled.
Select and use the TCP/IP protocol.
Re-Start the SQL Server service.
Using the SQL Server Surface Area Configuration Manager you must enable TCP/IP.
Select €œServices and Connections€?.
Choose your server instance and then select €œRemote Connections€?.
Choose €œLocal and Remote€?, then €œUsing TCP/IP Only€?.
Re-Start the SQL Server service.
The server needs a means to talk to the outside world. Use SCM.
Setup your IP address by right clicking on the TCP/IP protocol
Choose €œProperties€?.
On the €œProtocol€? tab leave the default settings, (Yes, 30000, Yes, No).
Select the €œIP Address€? tab.
Configure €œIP1€?, (Yes, Yes, enter your IP address, 0, blank).
Configure €œIP All. Leave the default alone.
Enter €œ1433€? on the second line.
Re-Start the SQL Server service.
The server needs to unlock the door to the outside world.
Open Control Panel and select Windows Firewall.
Click the €œExceptions€? tab and click on €œAdd Port€¦€?.
For €œName€?, enter the name of the server instance.
For €œPort Number€?, the same port as Step 3, 1433.
Test to see if Windows log in works before enabling SQL Authentification.
Using the SMSE, select the €œConnect€? icon in Object Explorer.
Accept all defaults and see if it works.
The server needs Windows user accounts setup.
Set up a generic user account for SQL remote users.
I suggest setting up an account for administrators to use.
I suggest setting up an account for general users to use.
SQL needs to add Windows users to SQL Logins.
Convert a windows user login to a SQL login manually or automatically.
The user needs to be assigned tasks that he is permitted to perform.
Grant the user limited access, or just enough.
Assign generic logins to groups, and then assign permissions to the groups.
Use the pre-defined groups. By assigning users to groups.
Test to see if SQL Authentification works locally, then remotely.
Using the SMSE, select the €œConnect€? icon in Object Explorer.
Hello,
I'm using a Windows XP Home laptop to connect to a network of one of my customers. The administrator of the customer has given me a username and password for a VPN connection. I've got the VPN connection working and I can ping the SQL Express server.
This server is using Windows Authentication. For the users of my VB application we have added a group to the Active Directory and added this group as a user to the SQL Express Server. This works and the users can access the database from within the application. The SQL Express Server allows remote connections and the browser service is also running.
I would like to use the SQL management Studio Express on my laptop to access the remote SQL Express server and manage the database files. To do this I first connect to the remote LAN using VPN and add the address of the SQL EXpress server in the field 'Server name' of the 'Connect to server' screen. The authentication field is set to Windows Authentication. However the username is greyed out and states the login for the SQL Express server on my laptop: laptopusername. How can I correct this?
I don't know whether the username of the VPN connection is in the Active Directory. Should this be the case and should this user also be added to the login/user of the SQL Express server? And how do I get the Management Studio to connect to the remote server? Could XP Home be the bottleneck as it cannot logon to a domain?
Anyone any ideas?
Hi
I hope this is the right place for this question.
I'm using SQL 2005 Express on my local machine, I can connect and do all I need to.
But when I transfered my database to my remote server I cannot connect (I changed the connection string to suit).
<add name="ClubSiteDB" connectionString="Data Source=xx.xxx.xx.xx,1786;Network Library=DBMSSOCN;Initial Catalog=xxx;User ID=xxx;Password=xxx;" providerName="System.Data.SqlClient"/>
I have checked the connection string passsword etc, and all are correct.
I have tried SQL Server Management Studio, aspnet_regsql.exe etc and all give the following error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.)or
System.Web.HttpException: Unable to connect to SQL Server database. ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
I have used the surface config to enable TCP/IP and named pipes.
Any Ideas?
Thanks
Since today (after installing the latest Windows Updates !on my local machine!) I cannot login to a SQLExpress instance remotely; stating that it cannot find the server/instance.
The weird thing is: it only happens when I want to login to the non-default instance (sqlexpress 2005) (<IP><instance>).
When i'm using the default instance (msde 2000 or sqlexpress 2005 on another machine) (<IP>) it seems to work fine.
Does this have something to do with the windows updates, or is it just a coincedence?
Thanks in advance,
Remco Ros
I've been trying to configure remote connections to my sql server express to no avail.
First here are some constants to clear some things up:
- OS: Windows XP Pro
- SQL Express version: April CTP release
- Windows Firewall: disabled (to avoid any problems there)
- Network type: two computers connected a router.
- Router firewall: Enabled (I may be wrong but the router firewall only blocks external traffic, so I left it on.)
First, I configured my SQL server to allow remote connections in the SQL Surface Area Configuration. (Set it to both TCP/IP and named pipes)
Second, I enabled and configured sql server browser.
Third, I enabled TCP/IP and named pipes in the 'Protocols for SQL Express' option of the SQL Server Configuration Manager.
According to http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
I have done everything I need to (including edit the registry to enable the SQL Server Browser service) and the error I continue to get is:
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"
So I tinkered and had no success in messing with anything that would fix it. Although, ***when I browsed for network servers on different machine, the server instance DID show up in the list***. So I find it odd that it can find the instance when browsing, but fails to 'find' it when making a connection.
So I didn't stop there, I decided to try the non-sql server browser method of remotely connecting: specifying the IP.
I went back to the blog of instructions referenced above and re-did the steps, this time specifying a TCP Port for the server instance and then after specifying the port on the remote computer connection string, and attempting to connect, I get this error:
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)"
I've done all I know how, read all the possible blogs I can, and nothing's come up. If anyone can shed some light on me, I'd pay you 1 billion pretend dollars. Any help would be appreciated. Thank you!
im using sql server 2005 express for my vb.net projects but i can't connect to it using SQL Server Management Studio Express or through my vb.net code. I got a error message: An error has occourred while estabishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. I already enabled remote connections as suggested by this site http://www.programmingado.net/a-395/SQL-Server-2005-Express-and-remote-connection.aspx. Made sure that SQL Server and SQL Browser services are running. But I still cant connect.
I am tring to access the SQL 2005 Express which installed in remote machine. Front end app is on Visual Studio 2005. Try to connect SQL Express using the application Layer which is installed on the computer where SQL Express is installed. Could not fetch data from the SQL Express. What could be the problem?
With Regards,
ADK
i have a Vb application on an client pc that has to connect with a sql databse file on the server.
the connection string is :
connectionString="Data Source=<servername>SQLEXPRESS,1433;Initial Catalog=TBSD.mdf; User Id=sa;Password=sa;integrated security=false;" />
</connectionStrings>
if i run the application i get the error message : "login failed for user 'sa'.
If i try to connect remotely to sql server express with sql server managment studio express i can connect without any problems.
is this a security problem ?
Hi all,
I'm just wondering if there is documentation anywhere to help me with installation of SQL 2005 Express on a remote computer. I've set up IIS 6.0 and Windows Server 2003 Web Edition on another computer and am planning to use that for a development server.
Currently I've already installed VWD Express (local computer) and SQL 2005 Express, as well as SQL Query Manager (remote computer). But I seem to be having problems with VWD being able to create databases when i edit the code remotely.
For example when I right-click on "Data Connections" in the "Database Explorer" to create a new database it won't let me. The only way I can do this is to add a connection to a database which I have previously created. And even then there are still problems.
If I set up the database by adding a connection I cannot seem to create stored procedures. The error message I keep getting is "This feature is not supported in Visual Developer".
Is this due to wrong settings whilst installing SQL Express? Or am I just not configuring it right?
Any help on this issue would be greatly appreciated.
Thanks.
I've just bought a Virtual Private Server Account because I want to host a number of different ASP.NET sites, each backed by their own SQL database. I've downloaded SQLEXPRE.EXE and SQLServer2005_SSMEE-x64.msi to the server and installed the database engine and Management Studio Express on the VPS.
My problem is that I cannot access the SQLEXPRESS on my server from my local machine. The Management Studio Express cannot get logged in. I've used "Surface Area Configuration Manager" to allow "Local and remote connections" using TCP/IP only. I've used SQL Server Configuration Manager" to enable the TCP/IP protocol. After making these changes I've stopped and started the SQL server - and even rebooted the machine. I've created a login "Remote User" for this access. I've added sqlservr.exe as an exception to the firewall.
What else do I need to do? Is there a simpleton's guide to completing this task?
I have read all of the posts regarding this subject as well as 3"Dummies" guides and I keep having the same problems. I have a verysimple multi-user application that has to hit a database. Wecuerrently have this system deployed and it is working fine on adomain based network. We are scaling back and the network we will beusing is now a workgroup not a domain.It should be simple. I have XP boxes (clients) trying to hit the SQLServer Express database on a Windows Server 2003 machine. It is aclosed network so security is not an issue. I am trying to make thisthing wide open. All I want is for the user to be logged in on hisclient machine, run the application, and access/update the databasewithout having to re-authenticate to the SQL server. I want windowsto handle all of the authentication between the XP machines and theServer 2003 machine.Any suggestions would be greatly appreciated.
View 1 Replies View RelatedHi all, I'm having a little trouble connecting to a SQLExpress instance on a remote domain using SQL Server Management Studio Express.I've read that by default the program is set up locally only, so have edited the Surface Area Configuration. It only gives me the option to edit 'Services and Connections' on the localhost, but have edited the Remote Connections to use TCP/IP and Named Pipes. In the Management Studio, I enter the server name, and login credentials. On the Connection Properties tab I changed the network protocol to TCP/IP though everytime I attempt to connect I get the following error message: Any help would be greatly appreciated. Rich
View 4 Replies View Related
I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.
Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?
When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP AddressSQLExpress) as the server/host but I am getting the following errors from enterprise manager:
Just the (IP Address) as the server/host:
Invalid Connection.
ConnectionOpen( Invalid Instance())
(IP AddressSQLEXPRESS) as the server/host:
Sql Server does not exist or access denied. ConnectOpen(Connect()).
Any idea why I can€™t register/mount the instance remotely in Enterprise Manager
but I can in Sql Server Management Studio Express?
Thanks,
Greg
Problem: I upgraded a SQL Server Express instance to SQL Server Enterprise, but I'm unable to connect to the SQL server from any remote machine. Only local connections work -- and I've verified that Remote Connections are allowed in the SQL Surface Confg. utility.
Scenario: Server1 has an SQL Enterprise edition installed as a default installation. SharePoint Server 2007 was installed later, and during that install a SQL Express edition instance was installed which is part of the standard SharePoint install. That Express instance contains all the SharePoint content databases.
So Server1 has SQL instances:
Server1 <default install running Enterprise>
Server1OFFICESERVER <previously running SQL Express, now upgraded to Enterprise>
After upgrading Server1OFFICESERVER to Enterprise, everything seemed to work fine (i.e. SharePoint works fine). However when I try to connect remotely to Server1OFFICESERVER I can't. I've verified through the SQL Surface configuration tool that remote connections are allowed. I've rebooted the server as well. I've tried connecting remotely using various PCs and various applications (e.g. SQL Server Mgmt Studio, Visual Studio, etc.).
Any other ideas to try?
Hi, I hope you can help.I have configured a Windows 2003 web server and SQL 2005 Server (on same box) to successfully allow remote connections and to allow access via SQL Server Management Studio Express 2005.The problem I have is that I want to restrict access to the databases on the server via the Management Studio to specific databases e.g. 1 database user "sees" only 1 database.I can configure it so that the user's remote access permissions do not allow access to other databases but they can still "see" the database listed in the Management Studio explorer.I can also configure it so that the users cannot see all the databases (by disabling View All Databases on SQL Server), but this means that they cannot not see their own database which they have permissions for.Is it impossible to have the desired behaviour of only displaying the database which the remote user accessing has permissions for and hiding all other databases?I have MSN'd,Googled and Yahoo'd this one to no avail :(Many thanksFergus
View 6 Replies View RelatedI have DTS woking with the full features as in enterprise within SQL express. :)
View 2 Replies View RelatedAnd now i'm looking for what in SQL Server 2000 used to be:
Management->
SQL Server Agent->
jobs Can anyone help me find where i can add a job in SQL Express please?
Thanks
How can I devise best further to my query's and tables (without my users must stop with these data to consult)?
View 12 Replies View RelatedHi,
I am new to working with Database using .net C#. i will really appreciate if someone can point me to a link where i can find best practices of working with sql express database with my c# web service applications.
preferably i would like to have answers for:
- to have one db or to have one for testing and one real db?
- db security
- use windows authentication or db user authentication
etc.
Hi all,
I have a site which used a SQL Express database. On my development machine, it works perfectly. As soon as I move it to the production machine, it doesn't work at all. I am pretty confused by what is going on and I really don't want to install Visual Studio on my production machine just to debug it. I am hoping someone might have an idea what could be happening.
Oh, and I have tried setting Everyone to Full Control on the App_Data directory just to test. Still breaks. Below is my web.config connection string:
<connectionStrings> <add name="database_sqlexpress" connectionString="Data Source=.SQLEXPRESS; AttachDbFilename=|DataDirectory|MyDatabase.mdf; integrated security=true; user instance=true"/></connectionStrings>
When I click Download, it show NOT FOUND
What happened ?
I installed the SQL Server Express Advances w/ Reporting Services, but it doesn't appear to be working. When I bring the URL up in my web browser all I get is this:
transam/ReportServer$SQLExpress - /
Microsoft SQL Server Reporting Services Version 9.00.2047.00
Any tips on where to begin looking for what is wrong?
Robert
I'm having a 3.0 GHz machine with 512MB Ram. however when i tried to run sql server 2005. this is the result of the System Configuration Check
- WMI Service Requirement (Success)
Messages
* WMI Service Requirement
* Check Passed
- MSXML Requirement (Success)
Messages
* MSXML Requirement
* Check Passed
- Operating System Minimum Level Requirement (Success)
Messages
* Operating System Minimum Level Requirement
* Check Passed
- Operating System Service Pack Level Requirement. (Success)
Messages
* Operating System Service Pack Level Requirement.
* Check Passed
- SQL Server Edition Operating System Compatibility (Warning)
Messages
* SQL Server Edition Operating System Compatibility
* Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
- Minimum Hardware Requirement (Warning)
Messages
* Minimum Hardware Requirement
* The current system does not meet the minimum hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.
- IIS Feature Requirement (Warning)
Messages
* IIS Feature Requirement
* Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
- Pending Reboot Requirement (Success)
Messages
* Pending Reboot Requirement
* Check Passed
- Performance Monitor Counter Requirement (Success)
Messages
* Performance Monitor Counter Requirement
* Check Passed
- Default Installation Path Permission Requirement (Success)
Messages
* Default Installation Path Permission Requirement
* Check Passed
- Internet Explorer Requirement (Success)
Messages
* Internet Explorer Requirement
* Check Passed
- COM Plus Catalog Requirement (Success)
Messages
* COM Plus Catalog Requirement
* Check Passed
- ASP.Net Version Registration Requirement (Success)
Messages
* ASP.Net Version Registration Requirement
* Check Passed
- Minimum MDAC Version Requirement (Success)
Messages
* Minimum MDAC Version Requirement
* Check Passed
furthermore i get error 26 when trying to create new sql server database. and while doing the SQL server surface area configuration i got this message.:
SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)
------------------------------
Program Location:
at Microsoft.SqlSac.MainPanel.FormFeatures..ctor(String machineName, Form callingForm)
HOpefully somebody out there will help me...or is this problem only appearing in sql server 2005 and would it be a better decision to install SQL server 2000...or if someone can help me rectify this problem i'll be really thankful.
Hello,
I have SQL Server Express working however I don't see any tools to create a database and tables.
I am trying to create a database to store stock quotes that I will input from a c# program.
What tool should I use to design the database?
Thank you!
Toben
Sub Page_Load(sender As Object, e As EventArgs) 'declarations Dim conLath As SqlConnection Dim cmdLath As SqlCommand Dim rdrLath As SqlDataReader conLath = New SqlConnection("server=SERVERNAME;uid=USERNAME;pwd=PASSWORD; " & "database=DATABASE NAME") conLath.Open cmdLath = New SqlCommand ( "select * from Emails",conLath) rdrLath = cmdLath.ExecuteReader() gridLath.DataSource = rdrLath gridLath.DataBind() rdrLath.Close cmdLath.Dispose() conLath.Close End Sub
Can i connect to SQL on another server ? Becasue when i am trying to do so , i getting error ! I can connect to sql on my server but if i want to connect to another server i getting error ... help pleas ?
hi
I had a view in which I did something like this
isnull(fld,val) as 'alias'
when I assign a value to this in the client (vb 6.0) it works ok in sql2000 but fails in 2005.
When I change the query to fld as 'alias' then it works ok in sql 2005 .
why ?? I still have sql 2000 (8.0) compatability.
Also some queries which are pretty badly written run on sql 2000 but dont run at all in sql 2005 ???
any clues or answers ?? it is some configuration issue ?
Thanks in advance.
Hi,
It might be a silly question but really took my head. I have a http server and wanted to install SQL server there, so that my client in US can access it. I just wanna know is there anything specific settings while or after installation I need to do so that they can access it and can configure in their Enterprise Manager.
Is it okay if I simply install SQL SErver 2000 in my http server and give the IP address of the server with the port number so that they can go to Client Network Utility and add my server. Later they can come to Enterprise Manager and connect to that?
Please advice me how it is to be done.
Thanks in advance
Rahul
Has anyone experienced any limitaions or concerns for managing SQL 2K remotely using remote desktop, pleased advise.
Thanks
If I let the pages (ASP) running on the third party server access my database (MS SQL) remotely, what should I do with my database server? I was told to open a port. If it is true, what is the number of the port I should open?
Thanks in advance