Creation of SOAP(HTTP) SSL endpoint fails with error 0x80070494

Creation of SOAP(HTTP) SSL endpoint fails with error 0x80070494

  • Comments 8

Say you want to create an SSL endpoint for SOAP such as the following

CREATE ENDPOINT SOAP_ssl_endpoint 
   STATE = STARTED
   AS HTTP (
   SITE = 'localhost', 
   PATH = '/MySoapPath', 
   AUTHENTICATION = (INTEGRATED ), 
   PORTS = ( SSL ),
   SSL_PORT=443
)
FOR SOAP (
   …………
);

And the creation fails with the error message

Msg 7807, Level 16, State 1, Line 1
An error ('0x80070494') occurred while attempting to register the endpoint 'SOAP_ssl_endpoint'

The windows error code 0x494 (1172 or ERROR_NO_TRACKING_SERVICE) usually implies that a service dependency failed. SSL endpoints require the windows "HTTP SSL" service to be enabled. The "HTTP SSL" service doesn’t have to be started. Creation of an SSL endpoint will automatically start the "HTTP SSL" service.

If you see the 0x80070494 error, try to start the "HTTP SSL" service (net start "HTTP SSL"). If the service fails to start, check the service manager for any services that "HTTP SSL" is dependent on and try to start those services to isolate the cause of failure. Normally the "HTTP SSL" service has a dependency on the "HTTP" service. But when IIS is installed on the machine, it creates a dependency from "HTTP SSL" to the "IIS Admin Service" The "IIS Admin Service" is more likely to be the cause of failure than the "HTTP" service.

Anuradha Rawal, SQL Server Protocols

Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights

 

Leave a Comment
  • Please add 4 and 2 and type the answer here:
  • Post
  • Do you have any idea on how to get a SQL 2005 SOAP endpoint created on Vista 5308?
    Is there a tool that will reserve URL namespaces with http.sys? Or should SQL Server be able to register itself?

    Msg 7850, Level 16, State 1, Line 1
    The user 'sa' does not have permission to register endpoint 'sql_endpoint' on the specified URL.  Please ensure the URL refers to a namespace that is reserved for listening by SQL.
    Msg 7807, Level 16, State 1, Line 1
    An error ('0x80070005') occurred while attempting to register the endpoint 'sql_endpoint'.

    Any info would be greatly appreciated.
  • Hi Perry,

    SQL 2005 exposes functionality to reserve a namespace using sp_reserve_namespace stored procedure.  See:

    http://msdn2.microsoft.com/en-us/library/ms190614.aspx

    So you have to log into SQL using the local administrator account and then use the sp_reserve_namespace stored proc to pre-reserve the namespace.  Then a non-local admin account can create URLs under the namespace.

    Let me know if this works for you.
  • Quisiera saber porque al crear un ENDPOINT en mi SQL-SERVER 2003 no lo reconoce y me vota error,  
    gracias por su repuesta,
    PD. he creado un procedimiento almacenado
    este es el codigo que empleo
    USE MASTER
    go
    CREATE PROCEDURE prueba
    (@msg nvarchar(256))
    AS BEGIN
       select @msg as 'message'
    END
    go
    CREATE ENDPOINT prueba_endpoint
     AS
       AUTHENTICATON = ( INTEGRATED ),
       PATH = '/sql/demo',
       PORTS = ( CLEAR ),
       STATE = STARTED
    FOR SOAP (
     METHOD
       'http://tempuri.org/'.'prueba'
       (NAME = master.dbo.prueba)
     WITH
       BATCHES = ENABLED,
       WSDL = DEFAULT
     )
    go
  • LIZET,

    To confirm, when you mentioned that you are using SQL Server 2003, I assume you mean SQL Server 2005 running on Windows Server 2003.  Also, I assume that you are actually trying to create an endpoint on the CLEAR channel and NOT the SSL channel, but you are still getting the same 0x80070494 error.

    BTW, it looks like you are using a beta version of SQL 2005 as the syntax in your example looks pretty old.

    I would recommend upgrading your installation to the SQL 2005 RTM build.  The CREATE ENDPOINT syntax for the RTM build will be something like:
    CREATE ENDPOINT prueba_endpoint
      STATE = STARTED
    AS HTTP (
      AUTHENTICATION = ( INTEGRATED ),
      PATH = '/sql/demo',
      PORTS = ( CLEAR )
    )
    FOR SOAP (
    WEBMETHOD
      'http://tempuri.org/'.'prueba'
      (NAME = 'master.dbo.prueba'),
      BATCHES = ENABLED,
      WSDL = DEFAULT
    )
    go

    If you are still getting the same error code, please post back.

    HTH,
    Jimmy
  • Help, I am getting this error as stated above and When i try to pre-reserve the namespace i get an error that says the account does not have permission.   Where can i located the stored procedure.  i used the sys admin login and local admin, i is not working.

  • Hi Angela,

    I like confirm with you which error code you are getting:

    - 0x80070494

    - 0x80070005

    If you are getting 0x80070494, please confirm that you've enabled the "HTTP" and/or "HTTP SSL" service.

    If you are getting 0x80070005, please mention which OS you are running the SQL Server on.

    The stored procedure used to pre-reserve the URL is mentioned above in Matt Neerincx post.

    Jimmy [MSFT]

  • No puedo iniciar cecion me marca el error 0x80070005 y la verdad no se que hacer y les agradeceria mucho me puedan ayudar

  • I am trying to create an endpoint and am getting the 0x80070005 error message.  I am running SQL Server 2005 Developer Edition (9.0 RTM) on Windows Small Business Server 2003 (SP2).  The instance I am working with is setup for Windows Authentication only and I am logged on as the domain administrator.  I have tried everything I found on this page with no success, I still get this error.

    HTTP, HTTP SSL and IIS Admin are all running and set to Automatic.  I am using code in the 70-431 MSPress Self-paced training kit and it is failing.  I have even pared the code down to the following after running sp_reserve_http_namespace and specifying a namespace.

    CREATE ENDPOINT sql_endpoint

    STATE = STARTED

    AS HTTP(

    PATH = '/sql',

    AUTHENTICATION = (INTEGRATED),

    PORTS = (SSL)

    )

    FOR SOAP(

    WEBMETHOD 'BillofMaterials'

    (NAME = 'AdventureWorks.dbo.uspGetBillOfMaterials'),

    WSDL = DEFAULT

    )

    I have even created an A record in DNS to point to a separate IP address that I am reserving just for SQL Server to use.  Any ideas?

Page 1 of 1 (8 items)