create endpoint with anonymous authentication (yukon)

Hello, All!
The question to MSFT. Can you answer once and for all, will the sql server
2005 support anonymous authentication for endpoints? I have two BOLs, where
claims the different. This one:
AS HTTP (
PATH = 'url'
, AUTHENTICATION =( { BASIC | DIGEST | INTEGRATED } [,...n])
, PORTS = ({CLEAR | SSL} [,... n])
[ SITE = {'*' | '+' | 'webSite' },]
[, CLEAR_PORT = clearPort ]
[, SSL_PORT = SSLPort ]
[, AUTH_REALM = { 'realm' | NONE } ]
[, DEFAULT_LOGON_DOMAIN = {'domain' | NONE } ]
[, RESTRICT_IP = { NONE | ALL } ]
[, COMPRESSION = { ENABLED | DISABLED } ]
[, EXCEPT_IP = ( { <4-part-ip> | <4-part-ip>:<mask> } [,...n] )
)
and this
AS HTTP (
PATH = 'url'
, PORTS = ({CLEAR | SSL} [,... n])
[ SITE = {'*' | '+' | 'webSite' },]
[, CLEAR_PORT = clearPort ]
[, SSL_PORT = SSLPort ]
, AUTHENTICATION =({ANONYMOUS | BASIC | DIGEST | INTEGRATED} [,...n])
[, AUTH_REALM = { 'realm' | NONE } ]
[, DEFAULT_LOGON_DOMAIN = {'domain' | NONE } ]
[, RESTRICT_IP = { NONE | ALL } ]
[, COMPRESSION = { ENABLED | DISABLED } ]
[, ADD EXCEPT_IP = ( { <4-part-ip> | <4-part-ip>:<mask> } [,...n] )
[, DROP EXCEPT_IP = ( {<4-part-ip> | <4-part-ip>:<mask> } [,...n] )
)
Who is right?
With best regards, Alex Shirshov.
We will NOT be supporting ANONYMOUS authentication. I will file a bug to
correct BOL if there is indeed a reference to it.
We do not support ANONYMOUS in Beta2 as well.
Srik
"Alex Shirshov" <nomail@.mail.ru> wrote in message
news:eD$Jp6qsEHA.2560@.TK2MSFTNGP14.phx.gbl...
> Hello, All!
> The question to MSFT. Can you answer once and for all, will the sql server
> 2005 support anonymous authentication for endpoints? I have two BOLs,
> where
> claims the different. This one:
> AS HTTP (
> PATH = 'url'
> , AUTHENTICATION =( { BASIC | DIGEST | INTEGRATED } [,...n])
> , PORTS = ({CLEAR | SSL} [,... n])
> [ SITE = {'*' | '+' | 'webSite' },]
> [, CLEAR_PORT = clearPort ]
> [, SSL_PORT = SSLPort ]
> [, AUTH_REALM = { 'realm' | NONE } ]
> [, DEFAULT_LOGON_DOMAIN = {'domain' | NONE } ]
> [, RESTRICT_IP = { NONE | ALL } ]
> [, COMPRESSION = { ENABLED | DISABLED } ]
> [, EXCEPT_IP = ( { <4-part-ip> | <4-part-ip>:<mask> } [,...n] )
> )
> and this
> AS HTTP (
> PATH = 'url'
> , PORTS = ({CLEAR | SSL} [,... n])
> [ SITE = {'*' | '+' | 'webSite' },]
> [, CLEAR_PORT = clearPort ]
> [, SSL_PORT = SSLPort ]
> , AUTHENTICATION =({ANONYMOUS | BASIC | DIGEST | INTEGRATED} [,...n])
> [, AUTH_REALM = { 'realm' | NONE } ]
> [, DEFAULT_LOGON_DOMAIN = {'domain' | NONE } ]
> [, RESTRICT_IP = { NONE | ALL } ]
> [, COMPRESSION = { ENABLED | DISABLED } ]
> [, ADD EXCEPT_IP = ( { <4-part-ip> | <4-part-ip>:<mask> } [,...n] )
> [, DROP EXCEPT_IP = ( {<4-part-ip> | <4-part-ip>:<mask> } [,...n] )
> )
> Who is right?
> With best regards, Alex Shirshov.
>
|||Hello, Srik!
You wrote on Fri, 15 Oct 2004 15:47:28 -0700:
[Sorry, skipped]
Ok. Thank you. BTW, I have a beta 2 build 790 and it does support anonymous.
If the sql server will not support anonymous authentication, than how can I
connect to it without special settings on client? At first, I have to have a
public key of the certificate. But is ok, and really sad think, what I must
have windows account on server machine and must pass the credentials through
http. I don't understand, what the windows authentication need for? Is this
http.sys special requirement?
With best regards, Alex Shirshov.
|||Er... You say that "and it does support anonymous."
It shouldn't. If it does, then it is a bug. Can you email me the row from
the sys.endpoints and sys.soap_endpoints tables for an endpoint where anon
access is working?
Thanks!
Joel
"Alex Shirshov" wrote:

> Hello, Srik!
> You wrote on Fri, 15 Oct 2004 15:47:28 -0700:
> [Sorry, skipped]
> Ok. Thank you. BTW, I have a beta 2 build 790 and it does support anonymous.
> If the sql server will not support anonymous authentication, than how can I
> connect to it without special settings on client? At first, I have to have a
> public key of the certificate. But is ok, and really sad think, what I must
> have windows account on server machine and must pass the credentials through
> http. I don't understand, what the windows authentication need for? Is this
> http.sys special requirement?
> With best regards, Alex Shirshov.
>
>
|||Hello, Joel!
You wrote on Wed, 20 Oct 2004 13:39:11 -0700:
JS> It shouldn't. If it does, then it is a bug. Can you email me the row
JS> from the sys.endpoints and sys.soap_endpoints tables for an endpoint
JS> where anon access is working?
I try to send the screen shot to JoelSoderberg <at>
discussions.microsoft.com, but get an error. For newsgroup the picture is
too large.
Here is restricted output
[sql]
select cast(name as varchar(28)) name,is_anonymous_enabled from
sys.http_endpoints
select @.@.version
/*
alter endpoint secure
as http(
path='/sql/secure',
ports=(ssl),
AUTHENTICATION=(anonymous)
)
*/
[/sq]
name is_anonymous_enabled
-- --
hello_world_endpoint 0
secure 1
HelloFromYukon 0
_1 0
(4 row(s) affected)
----
Microsoft SQL Server Yukon - 9.00.790 (Intel X86)
Apr 12 2004 18:41:04 2000.090.0790.00
Copyright (c) 1988-2003 Microsoft Corporation
"Yukon" Beta 2 on Windows NT 5.2 (Build 3790: )
(1 row(s) affected)
[Sorry, skipped]
With best regards, Alex Shirshov.

CREATE ENDPOINT to Expose a single DB instance

I have been looking at this statement for allowing access from a remote location to a specific database on my SQL Server (2005) from a client application.

Is it possible to do this using this method? I see lots of examples using this to expose Web Services of DB objects, however I need the client application to be able to authenticate to and access all objects in the database. If so, could some one provide a simple example of the arguments to use? For example, which protocol arguments are valid for this? I would like to use SQL Server Authentication. Is this possible?

Regards,

-Troy

I think the answer is to create a new instance of SQL Server on a non-standard port and move the DB to that instance. At least that is what I've chosen to do. If anyone knows of a better way, let me know.

create endpoint fails with error 0x800704be

I am trying to create an endpoint with the code below and get the following error

An error ('0x800704be') occurred while attempting to register the endpoint 'getFormsEP'.

Anyone any ideas on what this error means?

Please help if you can.

Regards, Major (that is my Christian name ;-)

Code

create endpoint getFormsEP
state = started
as http
(
site='ictdwt10mt',
path='/EndPoints',
authentication=(integrated),
ports=(clear),
clear_port=84
)
for soap
(
webmethod 'getForms'
(
name='EForms21.dbo.getForms',
schema=standard,
format=rowsets_only
),
wsdl=default,
login_type=windows,
database='EForms21',
schema=none
)

Additionl information.

I have now setup a server with .NET 3.0 and a development PC with .NET 3.0. I have applied the lastest OS fixes to both.

I have installed SQL 2005 Service Pack 2 on the server.

I am still getting this error.

Anyone from MS watching?

Please help if you can.

Regards, Major.

|||

Hi Major,

You need to set the namespace in order for this endpoint to bind because it serves as the final location or address of the bound endpoint.

Hope this helps,

John Gordon (MSFT)

<edit>

Sorry about that, I misunderstood the requirements. I will continue to look into this for you but Matt is probably going to beat me to a solution to your problem. I hope we get this fixed for you soon.

|||Hi Major,

What operating system are you running on?

Error code: (HRESULT) 0x800704be (2147943614) - The format of the specified network name is invalid. Or the constant error code is ERROR_INVALID_NETNAME.

Note I wasn’t able to replicate it by putting all sorts of invalid names as the site name when creating the endpoint.

This will come up when SQL tries to register the endpoint using httpaddurl API and it means the network name you specified in the site='zzz' tag is not valid from http.sys perspective. Try running ipconfig /all and verifying the site name you are using is correct.

CREATE ENDPOINT (Transact-SQL)

I'm new to SQL Server 2005. I was attempting to run the SQL described in the
help file section called 'CREATE ENDPOINT (Transact-SQL) '. Here is that
SQL:
CREATE ENDPOINT sql_endpoint
STATE = STARTED
AS HTTP(
PATH = '/sql',
AUTHENTICATION = (INTEGRATED ),
PORTS = ( CLEAR ),
SITE = 'B37KGVK71Z\DEVSQLSVR'
)
FOR SOAP (
WEBMETHOD 'GetSqlInfo'
(name='master.dbo.xp_msver',
SCHEMA=STANDARD ),
WEBMETHOD 'DayAsNumber'
(name='master.sys.fn_MSdayasnumber'),
WSDL = DEFAULT,
SCHEMA = STANDARD,
DATABASE = 'master',
NAMESPACE = 'http://tempUri.org/'
);
GO
The result I am getting is as follows:
Msg 7807, Level 16, State 1, Line 1
An error ('0x80070057') occurred while attempting to register the endpoint
'sql_endpoint'.
Can someone tell me how to find out what error 0x80070057 is, and/or suggest
how to resolve this problem?
It's the semi-generic "parameter is incorrect" error. It
looks like it's from what you have specified for SITE. Try
specifying the site as server name only - B37KGVK71Z
-Sue
On Mon, 3 Apr 2006 10:15:02 -0700, Ken
<Ken@.discussions.microsoft.com> wrote:

>I'm new to SQL Server 2005. I was attempting to run the SQL described in the
>help file section called 'CREATE ENDPOINT (Transact-SQL) '. Here is that
>SQL:
>--
>CREATE ENDPOINT sql_endpoint
>STATE = STARTED
>AS HTTP(
> PATH = '/sql',
> AUTHENTICATION = (INTEGRATED ),
> PORTS = ( CLEAR ),
> SITE = 'B37KGVK71Z\DEVSQLSVR'
> )
>FOR SOAP (
> WEBMETHOD 'GetSqlInfo'
> (name='master.dbo.xp_msver',
> SCHEMA=STANDARD ),
> WEBMETHOD 'DayAsNumber'
> (name='master.sys.fn_MSdayasnumber'),
> WSDL = DEFAULT,
> SCHEMA = STANDARD,
> DATABASE = 'master',
> NAMESPACE = 'http://tempUri.org/'
> );
>GO
>---
>The result I am getting is as follows:
>Msg 7807, Level 16, State 1, Line 1
>An error ('0x80070057') occurred while attempting to register the endpoint
>'sql_endpoint'.
>---
>Can someone tell me how to find out what error 0x80070057 is, and/or suggest
>how to resolve this problem?
|||Sue,
Ok. That worked. Now if it's a SOAP endpoint I should be able to get to it
in a browser? Or is this SOAP but not IIS?
What I need is : How do I test it works without writing a .NET application?
Ken
"Sue Hoegemeier" wrote:

> It's the semi-generic "parameter is incorrect" error. It
> looks like it's from what you have specified for SITE. Try
> specifying the site as server name only - B37KGVK71Z
> -Sue
> On Mon, 3 Apr 2006 10:15:02 -0700, Ken
> <Ken@.discussions.microsoft.com> wrote:
>
>
|||No...you can't just point your browser at it and have it do
something. It's an HTTP SOAP endpoint - HTTP is the
communication protocol. If you want to mess with Web
Services and this functionality without writing code, try
the sample application available with SQL Server 2005. Check
books online for the information on the sample app:
Sample Applications for Sending Native XML Web Services
Requests.
All of the code and the client apps (C# or VB.Net) are
included with the sample. Steps on how to set it up are in
books online.
-Sue
SQL Server MVP
On Tue, 4 Apr 2006 14:36:03 -0700, Ken
<Ken@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Ok. That worked. Now if it's a SOAP endpoint I should be able to get to it
>in a browser? Or is this SOAP but not IIS?
>What I need is : How do I test it works without writing a .NET application?
>Ken
>---
>"Sue Hoegemeier" wrote:
|||Sue,
Thank you for your help. I tried what you suggested. But there still seems
to be a problem. To illustrate the problem I am having, I first removed
sql_endpoint, and then reconstructed it so I could make sure I was not
missing steps.
The problem is that after I create the endpoint it appears to not be
registered in the HTTP.sys - so can you follow the steps below and advise me.
I used the instructions posted at
"http://msdn2.microsoft.com/en-us/library/ms188682(SQL.90).aspx - Reserving
URL Namespaces by Using Http.sys" to try to confirm the endpoint.
Can you please look at the steps I followed below and advise me.
---
Step 1. I droped sql_endpoint.
IF EXISTS (SELECT * FROM sys.endpoints e WHERE e.name = N'sql_endpoint')
DROP ENDPOINT [sql_endpoint]
Step2: I made sure I was sysadmin.
Step3: I recreated sql_endpoint as follows , and got the message "Command(s)
completed successfully." -
CREATE ENDPOINT sql_endpoint
STATE = STARTED
AS HTTP (
PATH = '/sql/AdvWorks',
AUTHENTICATION B37KGVK71Z= (INTEGRATED ),
PORTS = ( CLEAR ),
SITE = 'B37KGVK71Z'
)
FOR SOAP (
WEBMETHOD 'GetSqlInfo'
(name='master.dbo.xp_msver',
SCHEMA=STANDARD ),
WEBMETHOD 'DayAsNumber'
(name='master.sys.fn_MSdayasnumber'),
WSDL = DEFAULT,
SCHEMA = STANDARD,
DATABASE = 'master',
NAMESPACE = 'http://planet.Xorthal.local/'
);
GO
Step 4: I followed the advice of site
"http://msdn2.microsoft.com/en-us/library/ms188682(SQL.90).aspx" and used the
utility "httpcfg.exe" to verify that the url was reserved. The command I
entered and the response I got (no data) is shown below - which appears to
say the endpoint creation did.
c:> httpcfg query urlacl
c:>
Step 5: I observed that the response that should have appeared was
something like
URL: http://B37KGVK71Z:80/sql/AdvWorks
ACL: ...
__________________________________________________
"Sue Hoegemeier" wrote:

> No...you can't just point your browser at it and have it do
> something. It's an HTTP SOAP endpoint - HTTP is the
> communication protocol. If you want to mess with Web
> Services and this functionality without writing code, try
> the sample application available with SQL Server 2005. Check
> books online for the information on the sample app:
> Sample Applications for Sending Native XML Web Services
> Requests.
> All of the code and the client apps (C# or VB.Net) are
> included with the sample. Steps on how to set it up are in
> books online.
> -Sue
> SQL Server MVP
> On Tue, 4 Apr 2006 14:36:03 -0700, Ken
> <Ken@.discussions.microsoft.com> wrote:
>
>

CREATE ENDPOINT (Transact-SQL)

hello all i am new here,

my question is how i can activate http in sql server 2005

i want to run a helpdesk application but i cant make a new database.

it has something to do with create endpoint, i have no knowlege off sql server 2005 its not my field

can someone help me please?

It seems like you may have 2 separate problems. One is creating a new database and the other is creating an endpoint. If the root problem of the "helpdesk application" is creating the new database, I suggest posting a new forum posting with the error you get when you try to create the database. That will help people understand what the problem is and be able to suggest solutions.

Regarding creating an endpoint, I assume you are already able to connect to SQL Server. You will need SQL administrator or equivalent permissions to create the endpoints. For additional information regarding creating endpoints, please refer to Books Online "CREATE ENDPOINT" topic (http://msdn2.microsoft.com/en-us/library/ms181591.aspx).

If you have problems creating the endpoint outside of the "helpdesk application" (ie. using SQL Management Studio), please post the error you get from the server.

Jimmy|||

thank you jimmy,

i have found a workaround by installing a different sqlserver

thanks anyway

paul