Results 1 to 5 of 5

Thread: Need help with parameterized filter error (merge replication)

  1. #1
    Join Date
    May 2009
    Posts
    3

    Need help with parameterized filter error (merge replication)

    Hi,

    I'm trying to add partitioning to my database (~250k rows) using 1 parameterized filter on a root table ("region") and several join filters off that table. The param. filter compares the subscriber's HOST_NAME() to the RegionID.

    When I use a HOST_NAME for a small region with little/no data, the subscription can be created successfully using the New Subscription Wizard in SQL Server Management Studio. However when using a HOST_NAME of a large region, the subscription wizard fails with the following error:

    - Downloading Table (blah) (Error)
    Messages
    * An error has occurred on the computer running IIS. Try restarting the IIS server.
    HRESULT 0x80070057 (28022)

    * The operation could not be completed.

    The table on which the error occurs ("blah" above) is always the same, however if I try to re-arrange the join filters for the "blah" table, the error still occurs.

    In the database there is a small amount of redundancy in that some tables are linked to the head "region" table via multiple 'paths', however there are NO circular relationships, and all relationships have integrity enforced.

    How do I tackle this problem, and how can I find out more information about the specific error I am receiving?

    Thanks in advance!

  2. #2
    Join Date
    Sep 2002
    Posts
    5,938
    Replicate via IIS? Checked authentication in IIS?

  3. #3
    Join Date
    May 2009
    Posts
    3
    Quote Originally Posted by rmiao View Post
    Replicate via IIS? Checked authentication in IIS?
    Yes replication is via IIS. Subscribers at the moment are logging in anonymously.

  4. #4
    Join Date
    Sep 2002
    Posts
    5,938
    Maybe permission related issue.

  5. #5
    Join Date
    May 2009
    Posts
    3
    Solved the problem; was nothing to do with permissions / authentication. SQL Server simply couldn't handle join filters coming off other join filters... flattened my filter set so that I only have join filters coming off parameterized filters, and it works perfectly now.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •