Cannot Connect Remotely To HTTP EndPoint
Feb 1, 2007
Dear all,
I appologise that incarnations of this topic have been posted several times on this forum, however I cannot find a scenario that is the same as my own so I've resorted to starting a new thread.
I can successfully create and connect remotely to an HTTP EndPoint on my Windows 2003 machine using Integrated security, the administrator username and password via my static IP address.
I have read that Windows XP SP2 supports HTTP EndPoints, and it would be much more convenient for me to be able to create EndPoints in XP, and connect remotely.
I have created the endpoint like so...
CREATE ENDPOINT sql_tvr10
STATE = STARTED
AS HTTP(
PATH = '/sql/tvr10', AUTHENTICATION = (INTEGRATED),
PORTS = (CLEAR))
FOR SOAP (
WEBMETHOD 'StoredProcedure1'
(name='master.dbo.StoredProcedure1'),
WSDL = DEFAULT,
BATCHES = ENABLED,
DATABASE = 'master',
NAMESPACE = 'http://194.106.11.11/' )
In visual studio I can retrive a list of services running at http://localhost/sql/tvr10?WSDL absolutely fine. However, in Visual Studio on the remote machine, I cannot connect to http://194.106.11.11/sql/tvr10?WSDL - it prompts me for a username and password, however I cannot select the username - it is set to "Athlon64Guest" (Athlon64 is my server computer name). I have no passwords on any of my windows accounts (except administrator), and I have no database passwords set.
Could someone please tell me how I should go about accessing the HTTP EndPoint?
Just so it is clear, I am running a small LAN with no domain, just a workgroup. I need the client application to be able to connect via http regardless of which network it is on. I am using VS2005 and SQL Server 2005 Dev Ed.
Many thanks in advance,
Simon
View 12 Replies
ADVERTISEMENT
Apr 24, 2008
Hello,
I created a HTTP-Endpoint on SQL Server 2005. Now I try to call this web service from a c# client but using SQL-Server authentication (i.e. my user is a sql server user but not a windows user). But it doesn't work.
I can connect to the service using a windows user and NTLM authentication. But for some reasons Iwould much prefer if I could use SQL-Server authentication. Is it possible?
Here is how I created the endpoint:
Code Snippet
CREATE ENDPOINT myService
STATE = STARTED
AS HTTP(
PATH = '/services',
AUTHENTICATION = (INTEGRATED ),
PORTS = ( SSL ),
SITE = '*'
)
FOR SOAP (
WEBMETHOD 'GetStuff'
(name='MyDB.dbo.FKT_getStuff',
SCHEMA=STANDARD ),
WSDL = DEFAULT,
LOGIN_TYPE = MIXED,
SCHEMA = STANDARD,
DATABASE = 'MyDB',
NAMESPACE = 'Services'
);
GO
Thanks!
Jerma
View 5 Replies
View Related
Jan 31, 2007
I am just about ready to tear my hair out on this one, at this point you guys are my last resort! Wouldn't it be nice if I could go to bed and have an answer for me in the morning....
I've had a working HTTP endpoint using Basic Authentication over SSL for months in our development environment, but now I'm moving our application to a production server and I'd like to be able to use Digest Authentication in the clear instead so the processor doesn't waste cycles on the SSL decryption. I've spent hours fiddling with my endpoint to no avail.
This is the closest message relating to what I'm doing that I've been able to find: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1131251&SiteID=1
In my case, the SQL Server is joined to a domain that is entirely Windows Server 2003 - no Windows 2000, so support for Digest Authentication is a non-issue. I'm also explicitly doing a GRANT CONNECT on my endpoint to the domain user I'm using. Here is the top of my CREATE ENDPOINT DDL:
CREATE ENDPOINT [Kudos]
STATE=STARTED
AS HTTP (PATH=N'/Kudos',
PORTS = (CLEAR),
AUTHENTICATION = (DIGEST,NTLM),
SITE=N'echobase.kudosnow.com'
DEFAULT_LOGON_DOMAIN = N'kudosnow',
AUTH_REALM = N'kudosnow'',
CLEAR_PORT = 80,
COMPRESSION=DISABLED)
FOR SOAP (
I am debugging using wfetch 1.3... I can get this to work using NTLM Authentication; sending a GET to my endpoint with the ?wsdlsimple querystring parameter returns my WSDL just fine.
But Digest just doesn't want to work! If I remove NTLM from my AUTHENTICATION directive and try using Digest with wfetch or from my (PHP) web service consumer I get an HTTP 401 no matter what I do. I've tried fiddling with the DEFAULT_LOGON_DOMAIN, AUTH_REALM, and anything else I can think of.
The errors I am sporadically finding in the SQL Server error log are:
HTTP authentication failed. [CLIENT: 192.168.245.238] from source Logon
Followed by:
Error: 26026, Severity: 14, State: 1. from source Logon
I can't find any detail about the second error.
........
Just occurred to me that I've also been trying to view my WSDL directly in IE, and this is what's causing the SQL error to be logged, not wfetch - that's why it appeared sporadically.
So, wfetch isn't causing an 'HTTP authentication failed' error, but Internet Explorer is... maybe Digest Authentication isn't implemented correctly in wfetch?
Regardless... I'm still not able to authenticate from IE or from my client, but this may shed some more light on the issue.
Does anyone have any ideas?
View 4 Replies
View Related
Oct 23, 2007
I have the need to have a client application connect to a remote database server for retrieval of large datasets (~13000 rows at time) and am trying to leverage existing technologies to build my solution.
To test the difference in retrieval times I created 2 test apps - testA and testB. I created an HTTP endpoint in SQL Server (2005) that exposes one web method corresponding to a sproc that executes one select query and configured testA to execute query and bind the results to a data grid. I exposed my SQL Server so that I could connect directly to the SQL Server using a connection string and configured testB to execute the same SQL statement in an ad-hoc fashion, binding the results to a data grid.
On average, the HTTP endpoint would take ~ 34 seconds to return the 13,000 row data set whereas the direct connection returned that same result set in 4 seconds or less.
I have a bunch of questions:
* Why would I be seeing such a dramatic difference in the retrieval times?
* How is SQL Server communicating when there is a direct connection?
* What are the immediate disadvantages to connecting directly to the remote SQL Server?
* If I were to consider allowing my client application to communicate directly with the SQL Server, is there any way to secure the communication without VPN?
* In addition, is it even possible to create a SQL login that has all of these requirements?
** select and update only
** cannot view schema (cannot connect to the SQL Server using SQL Server Management Studio)
** cannot view any system tables
** cannot retrieve any information about the schema of the database whatsoever
I guess I'm wondering if there is a way to overcome the obvious serialization overhead that comes with the HTTP endpoint to get the speed of the direct connection while being secure at the same time. Is that being greedy? :P
Anyhow, what are your opinions? I'm very interested to hear experiences and/or advice.
Thanks,
Paul
View 1 Replies
View Related
May 31, 2007
Hi,
I'd like to know how can I setup the SSL so I can secure my HTTP Endpoint.
I saw in the documentation that some settings such as SSL_PORT and PORTS should be set to SSL port number and SSL but I did not find out anywhere where they explain how to enable SSL.
Do we enable SSL the same way we enable it or SQL Server 2005 or does that have to be done through the MMC - Certificates.
I don't have any IIS server running on this server, so I was wondering if IIS is a requirement to generate and import the certificate.
I appreciate your help and comments.
Bruce.
View 3 Replies
View Related
Jun 27, 2006
Hi All,
I met some problems when I walk through a example for Native Http SOAP in SQL Server 2005 for Developers. after I create the HTTP EndPoint in the Management Studio using following code:
USE AdventureWorks
GO
CREATE PROCEDURE EmployeePhoneList
AS
SELECT C.LastName, C.FirstName, C.Phone
FROM Person.Contact AS C
INNER JOIN HumanResources.Employee AS E
ON C.ContactID = E.ContactID
ORDER BY C.LastName, C.FirstName
GO
DROP ENDPOINT HRService;
GO
CREATE ENDPOINT HRService
STATE = STARTED
AS HTTP
(
PATH='/HumanResources',
AUTHENTICATION=(INTEGRATED),
PORTS=(CLEAR)
)
FOR SOAP
(
WEBMETHOD 'EmployeePhoneList'(name='AdventureWorks.dbo.EmployeePhoneList'),
DATABASE='AdventureWorks',
WSDL=DEFAULT
)
then I can see the web service is indeed created by using following cmnd,
SELECT *
FROM sys.endpoints
SELECT *
FROM sys.soap_endpoints;
SELECT *
FROM sys.endpoint_webmethods;
but when I want to use the web service in the VS2005, I can't find it and add the web reference. Any help will be greatly appreciated. and could you please tell me how to check web services in the local computer? Thanks.
Chris
View 8 Replies
View Related
Mar 19, 2006
Hello, I have problems consuming webservice, I was following this page.
http://codebetter.com/blogs/raymond.lewallen/archive/2005/06/23/65089.aspx
but in the intelisense the method returns an array of objects[], So I have a problem with this line.
localhost.GetEmployees sd = new localhost.GetEmployees();
sd.Credentials = System.Net.CredentialCache.DefaultCredentials;
DataSet ds = (DataSet)(sd.EmployeeList());------> IT CANT CONVERT.
GridView1.DataSource = ds.Tables[0];
GridView1.DataBind();
Error 1 Cannot convert type 'object[]' to 'System.Data.DataSet' c:inetpubwwwrootatlas1Default.aspx.cs 18 22 http://localhost/atlas1/
View 10 Replies
View Related
Jan 21, 2008
Hi
I am testing using Web Services from SQL Server 2005 and am having problems with IE Authentication when I try to retreive the WSDL.
The basic scenario is:
I create the Web Service and initially can view the WSDL using Http:ServernamePath?wsdl and also can consume the Web Service in a DotNet app. However after a period of 2 hours or more the the WSDl starts asking for authentication but I cannot determine what authentication or rights are required
In an earlier post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1175161&SiteID=1 Jimmy Wu mentions
"IE prompted me for my user credentials and after entering the information I was able to retrieve the WSDL doc".
What are the user credentials required and how do you set permissions to avoid these. This forum post is the only place I have seen where any mention is made of some additional credentials being needed.
Regards
nadreck
View 2 Replies
View Related
May 23, 2005
I am having trouble getting access to HTTP Endpoints working correctly.
View 1 Replies
View Related
Jan 16, 2007
I need to enable digest authorization on an HTTP endpoint, because the integration tools for some java code that needs to connect to it does not support NTLM or kerberos - only digest and basic. I setup a test endpoint in order to test only digest authorization (as opposed to the final endpoint which needs both digest and integrated), but I can't even get that to work - when I point my browser to it to see the wsdl it pops up with the login box, but the login always fails.
I have the feeling I'm missing some very minor piece that will just make the whole thing work. Below are some log entries as well as the script to create the test endpoint I'm hitting. Any ideas are very welcome, I've banged my head on this one for far too long.
SQL Server error logs shows a "Error: 26026, Severity: 14, State: 1" entry followed by a "HTTP authentication failed" entry.
Event Log Security entry on the server:
Logon Failure:
Reason: An error occurred during logon
User Name: MyUserName
Domain: mydomain
Logon Type: 3
Logon Process: WDIGEST
Authentication Package: WDigest
Workstation Name: -
Status code: 0xC000006D
Substatus code: 0xC00000FE
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -
Test endpoint script:
CREATE ENDPOINT [DigestTest]
STATE=STARTED
AS HTTP (PATH=N'/DigestTest', PORTS = (CLEAR), AUTHENTICATION = (DIGEST), SITE=N'SRV001',
CLEAR_PORT = 80, AUTH_REALM=N'mydomain', COMPRESSION=DISABLED)
FOR SOAP (
WEBMETHOD 'SimpleTest'( NAME=N'[TestDB].[dbo].[spSimpleTest]'
, SCHEMA=DEFAULT
, FORMAT=ALL_RESULTS),
BATCHES=DISABLED, WSDL=N'[master].[sys].[sp_http_generate_wsdl_defaultcomplexorsimple]',
SESSIONS=DISABLED, SESSION_TIMEOUT=60, DATABASE=N'TestDB', NAMESPACE=N'http://mydomain.com/',
SCHEMA=STANDARD, CHARACTER_SET=XML)
View 6 Replies
View Related
Jul 19, 2007
Hi,
I've created the following endpoint on a local database as follows,
CREATE ENDPOINT Wrox_EndPoint
STATE = STARTED
AS HTTP
(
SITE = 'localhost',
PATH = '/Wrox',
AUTHENTICATION = (INTEGRATED),
PORTS = ( CLEAR ),
CLEAR_PORT = 81
)
FOR SOAP
(
WebMethod 'GetProductCountByProductModelID'
(
NAME = 'adventureworks.dbo.ProductByProductModelID',
SCHEMA = STANDARD
),
WebMethod 'GetProductModels'
(
NAME = 'adventureworks.dbo.GetProductModels',
SCHEMA = STANDARD
),
WSDL = DEFAULT,
BATCHES = ENABLED,
DATABASE = 'AdventureWorks'
)
When I try to add a web reference in visualstudio to http://localhost/wrox?WSDL I get a 404 error.
I checked the web service is created in sys.http_endpoints
I've also run the following to grant permissions
USE MASTER
GO
GRANT CONNECT ON ENDPOINT::Wrox_EndPoint TO [myDomainpaulm]
GO
Any ideas where I'm going wrong?
Many thanks Paul
View 3 Replies
View Related
Feb 12, 2007
I created a HelloWorld like example using InforPath 2007 and endpoint with SQL Server 2005. Very simple example.
I created a stored procedure that took in one parameter, a datetime field. This parameter is then inserted into a db table that has two columns, an id column and a datetime column.
I took the store procedure just discribed to create an endpoint. Cool. The WSDL is showing, I'm feeling good.
I go to InfoPath and make it so that submit a datetime to the webmethod associated with the endpoint. The data table shows one more row has been added and it is the datetime I sent from InfoPath. YEA!! I go to the Event View and see that I have an error message. The message is HTTP authenticaiton failed. [CLIENT: 10.8.2.26]. Bummer!!
This does not make sense to me. I am able to update the targeted database table but I get an exception. I do not like exceptions nor warnings without an explanation. Does anyone have an idea why this is happening?
The endpoint code looks like: <code snippet>
CREATE ENDPOINT [GeraldTesting_endpoint]
AUTHORIZATION
STATE=STARTED
AS HTTP (PATH=N'/testEndPoint',
PORTS = (CLEAR),
AUTHENTICATION = (INTEGRATED),
SITE=N'*',
CLEAR_PORT = 8080,
COMPRESSION=DISABLED)
FOR SOAP (
WEBMETHOD 'testEndPoint'
( NAME=N'[geraldstest].[dbo].[Gerald_Test_Proc]'
, SCHEMA=STANDARD,
FORMAT=ALL_RESULTS),
BATCHES=ENABLED, WSDL=N'[master].[sys].[sp_http_generate_wsdl_defaultcomplexorsimple]',
SESSIONS=DISABLED, SESSION_TIMEOUT=60,
DATABASE=N'geraldstest', NAMESPACE=N'http://tempuri.org', SCHEMA=STANDARD, CHARACTER_SET=XML)
</code snippet>
I had to give up for the project I am currently working because of time constraints. But in the future, for out-of-the-box functionality for proof-of-concept/prototyping, I would like to use endpoints.
View 3 Replies
View Related
Jun 8, 2007
If I have SQL 2005 Standard installed on a server and I log on locally to that server. Can I connect to other machines through Management Studio-->Object Explorer that have SQLCE installed and manage the CE DB?
I think you can only connect to either local .sdf files or ones located on a device attached by USB to the local machine, but I have had some difficulty finding a definitive statement on that.
Thanks
View 1 Replies
View Related
Dec 29, 2003
Hi
I just installed MSDE over my Windows 2003 box and facing an small problem.
I installed it with SQL security mode and also set a password for user "sa".
Everything looks just fine using "osql" as it uses local address.
But I can't connect to my server from another computer using VS.NET Server Explorer.
It seems as MSDE is set to reject connections from outside by default.
My question is how to enable it so I can connect using my "sa" account.
Appreciate your help in advance.
View 3 Replies
View Related
Dec 30, 2005
I just reinstalled SQL Server and after reattaching my databases, I can't connect remotely. If I use "localhost" in my connection string it works fine, but I can't register my remote Enterprise Manager this way.
View 1 Replies
View Related
Mar 16, 2008
Hi everyone,
I'm trying to connect to my instance of SQL server 2000 remotely. I know how to do this with SQL server 2005. but since i do not have SQL server 2000 installed on my local machine.. (xp box) I would love to know how i can connect to my remote server?
Is this at all possible without SQL Server 2000 installed ? i have tried to download the personal edition / developer but I couldnt find it
If anyone knows where i can find the developer edition or if there is a trick to get SQL server 2005 to work with my SQL 2000 server it would be greatly appreciated.
thanks
View 1 Replies
View Related
Aug 11, 2007
I have both the develper and sql express installed on my laptop computer. I also have Sql Express installed on my desktop computer( Did have develper installed but removed thinking the problem was in the install). I can connect via Management console from my Desktop to laptop with out any problems. I see databases etc. I can not connect from my laptop to desktop. I get a login error. From what I can tell, the servers are configed the same on both machines. I checked Firewall settings on both machines, even turned them both off with no results. Every time I try to connect from laptop I get Log in error, and I get "Failure Audit" eror under component services.
Event Type: Failure Audit
Event Source: MSSQL$SQLEXPRESS
Event Category: (4)
Event ID: 18456
Date: 11-Aug-07
Time: 07:24:50
User: LARRY-GATLINGuest
Computer: LARRY-GATLIN
Description:
Login failed for user 'LARRY-GATLINGuest'. [CLIENT: 192.168.1.102]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 18 00 00 00 4c 00 41 00 ....L.A.
0010: 52 00 52 00 59 00 2d 00 R.R.Y.-.
0018: 47 00 41 00 54 00 4c 00 G.A.T.L.
0020: 49 00 4e 00 5c 00 53 00 I.N..S.
0028: 51 00 4c 00 45 00 58 00 Q.L.E.X.
0030: 50 00 52 00 45 00 53 00 P.R.E.S.
0038: 53 00 00 00 07 00 00 00 S.......
0040: 6d 00 61 00 73 00 74 00 m.a.s.t.
0048: 65 00 72 00 00 00 e.r...
I am at a loss as to what is wrong. I am migrating my Database apps to Sql from Access and need to access remotely and locally, as well as do Replication. Any ideas?
Thanks
Larry Gatlin
View 12 Replies
View Related
May 18, 2005
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 Related
Sep 19, 2007
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.
View 6 Replies
View Related
Dec 15, 2006
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?
View 2 Replies
View Related
Apr 15, 2007
TITLE: Connect to Server
------------------------------
Cannot connect to iiiidddbbb.
------------------------------
ADDITIONAL INFORMATION:
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)
------------------------------
What's blocking my remote connection to SQL 2005 on Windows 2003? I am using Vista Ulttima and the above message comes up after I clicked connect. However I have no problem to connect to same database from same location using XP. Can someone help?
View 4 Replies
View Related
Aug 10, 2006
I had a big problem on connecting sqlserver remotely from other machines on the network .....
From any computer in the network i wanna to register the instance of the sqlserver from the enterprise manager ..... the server instance doesn't appear within the available sqlserver list (the servername which equal to my machine is the only one that appear) ..... when i manualy write the servernamealias manually and i choose the connection type and then i write sqlserver username and password and then finish he give a message to me that access denied or sql server doesn't exist ... !!
by the way from the local machine i registered the local instance of sqlserver successfully and successfully i access the Databases .....
To be noted:
I previously uninstalled this alias and i then i reinstalled it again with the same name and i attached the previously exists Databes.
in the same time i installed on the same machine sqlserver 2005 connectivity clients not the server itself.
View 5 Replies
View Related
Jan 18, 2008
Hi,
I am trying to remotely connect to a SQL 2005 Instance on a cluster. I see the following error:
No retry on exception 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have enabled TCP/IP , Named Pipes on the node. I have turned off IPSec on the clients as well. I am using the following connection string : "Integrated Security=SSPI;server=servernameinstancename;Pooling=false;database=TrialDB"
Is there something I am missing?
Any pointers will be appreiciated.
thanks.
View 2 Replies
View Related
Oct 5, 2007
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.
View 4 Replies
View Related
Mar 18, 2007
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?
View 1 Replies
View Related
Jun 22, 2007
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 Related
Nov 9, 2006
Hi all,
WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.
I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.
FROM THE SERVER :
osql -E -S MYSERVERWSUS works fine but
osql -E -S 127.0.0.1WSUS doesn't work, i get the famous error
[DBNETLIB]Serveur SQL spécifié non trouvé.
[DBNETLIB]ConnectionOpen (Connect()).
If i user "osql -L" command, my instance doesn't appear in the list
FROM A CLIENT COMPUTER
osql -E -S MYSERVERWSUS and
osql -E -S MY_SERVER_IPWSUS don't work, i get the same error
I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran
select @@version from osql and got result
Microsoft SQL Server 2000 - 8.00.881 (Intel X86)
8.00.881 is not referenced in ms support as a patched version number !!!!!
Can anyone help me please ?
View 1 Replies
View Related
Jun 27, 2006
Hi all,
I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"
I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).
I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").
Thank you
Ioannis
View 6 Replies
View Related
Jun 30, 2007
All,
My ISP does not allow me to remotely connect to my hosted SQL Server DB--how can I use SQLDataSource and other data bound controls in development?
Here are my specs:
IDE: Visual Web Developer Express 2005
Database: MS SQL Server
ASP Version: ASP.NET 2.0
The SQL Server is hosted centrally at the ISP; basically I have been given the connection string parameters.
My question is this:
Do I use two web.config files (one for when I develop locally and one for when I deploy remotely)? If so, how? Will the SQLDataSource control find the connection string defined in web.config on the remote server? I don't want to have to write all of the database code and it would be a big loss of one of the major benefits of using ASP.NET 2.0 if I do.
Any help will be greatly appreciated,
Leslie
View 4 Replies
View Related
Oct 31, 2007
Hi 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
Jan 18, 2005
Someone please help me before I loose all of my hair :mad: !!!
I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).
I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.
Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.
So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!
View 2 Replies
View Related
Mar 4, 2007
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?
View 4 Replies
View Related
Sep 21, 2015
I have an SQL Server 2012 with SSIS installed on Windows Server 2008 R2 Core. I'd like to connect remotley to SSIS but I receive the following error. 'The RPC server is unavailable.'
View 2 Replies
View Related
