+ Reply to Thread
Results 1 to 3 of 3

Error: 17832, Severity: 20, State: 8.

  1. Error: 17832, Severity: 20, State: 8.

    All servers are Win 2003 & SQL 2005

    I have a SQL Server that has many publications (30) & subscriptions
    (+/- 75). There are is a publication that has several (4)
    subscriptions & 2 of them work fine & the other 2 report the message
    below in the SQL Server Log

    Error: 17832, Severity: 20, State: 8.
    The login packet used to open the connection is structurally invalid;
    the connection has been closed. Please contact the vendor of the
    client library. [
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    there are no errors in the SQL Server Agent Log, but when the
    subscription runs, the following error is reported in the distribution
    agent

    The process could not connect to Subscriber 'SQLSERVERxx'.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    I can Telnet on port 1433 to/from the publisher & subscriber.
    I can ping the publisher from the subscriber & subscriber from the
    publisher.
    I can map & delete a share to/from publisher & subscriber.
    I can create another publication/subscription to different a database
    on the same server.
    I have deleted all publication/subscriptions for this database & ran
    sp_removedbreplication on both publisher & subscriber, with the same
    result.
    I have rebooted all routers & cleared log tables on all routers.
    I cannot believe this is a network or hardware issue because it is
    limited to only a couple databases & subscribers.
    Other publication/subscriptions to the same server that is having
    problems on other databases are working fine.

    AHIA,
    Larry.....

  2. Re: Error: 17832, Severity: 20, State: 8.

    Note: if I change the user name that it connects to the subscriber
    from impersonate to 'SA', it works fine. It currently uses a domain
    account that works on all other subscriptions.

  3. Replication error

    DESCRIPTION: Replication-Replication Distribution Subsystem 10-283 scheduled for retry. Query timeout expired i am getting this error. p[lease help me.


    Thanks,
    sunney



    LPR-3rd wrote:

    Note: if I change the user name that it connects to the subscriberfrom
    11-Feb-10

    Note: if I change the user name that it connects to the subscriber
    from impersonate to 'SA', it works fine. It currently uses a domain
    account that works on all other subscriptions.

    Previous Posts In This Thread:

    On Thursday, February 11, 2010 4:41 PM
    LPR-3rd wrote:

    Error: 17832, Severity: 20, State: 8.
    All servers are Win 2003 & SQL 2005

    I have a SQL Server that has many publications (30) & subscriptions
    (+/- 75). There are is a publication that has several (4)
    subscriptions & 2 of them work fine & the other 2 report the message
    below in the SQL Server Log

    Error: 17832, Severity: 20, State: 8.
    The login packet used to open the connection is structurally invalid;
    the connection has been closed. Please contact the vendor of the
    client library. [
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    there are no errors in the SQL Server Agent Log, but when the
    subscription runs, the following error is reported in the distribution
    agent

    The process could not connect to Subscriber 'SQLSERVERxx'.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    I can Telnet on port 1433 to/from the publisher & subscriber.
    I can ping the publisher from the subscriber & subscriber from the
    publisher.
    I can map & delete a share to/from publisher & subscriber.
    I can create another publication/subscription to different a database
    on the same server.
    I have deleted all publication/subscriptions for this database & ran
    sp_removedbreplication on both publisher & subscriber, with the same
    result.
    I have rebooted all routers & cleared log tables on all routers.
    I cannot believe this is a network or hardware issue because it is
    limited to only a couple databases & subscribers.
    Other publication/subscriptions to the same server that is having
    problems on other databases are working fine.

    AHIA,
    Larry.....

    On Thursday, February 11, 2010 4:46 PM
    LPR-3rd wrote:

    Note: if I change the user name that it connects to the subscriberfrom
    Note: if I change the user name that it connects to the subscriber
    from impersonate to 'SA', it works fine. It currently uses a domain
    account that works on all other subscriptions.


    Submitted via EggHeadCafe - Software Developer Portal of Choice
    C# And The Little Iterator That Could
    http://www.eggheadcafe.com/tutorials...e-iterato.aspx

+ Reply to Thread