SQL Server Performance

Error with Web Synchronization

Discussion in 'SQL Server 2005 Replication' started by vyasdev2005, Apr 2, 2009.

  1. vyasdev2005 New Member

    I have Windows Server 2003 Enterprise OS, SQL 2005 Developer installled, And I am getting error with Web Synchronization with merge replication, I am stating here what i have done so till this time- Configure a Publication with merge replication and pull subscription , Distributor & Publisher are on same machine, after Create a user Under Sysadmin Role, Create user for Publishing Database with db_owner schema, assign all permission to it,Running snapshot agent under SQL SERVER agent account, And for Web Synchronization I create account with DYNDNS.com and Create MyServer.dyndns.biz hostname with my static IP, And At publisher I assign address MyServer MyServer.dyndns.biz, configure web Synchronization at publisher as per Microsoft Site.- At IIS I create a virtual directory under Default Web Site,named TestPublication,Create new user,IIS_user for IIS_WPG Group, Create new Application pool and Configure its identity with New Creted IIs_user,and set new application pool at my virtual directory application pool setting.At Default web site properties, I assign my static IP at WebSite Identification, At directory security tab,I enable anonymous access with "PINAAK-3IUSR_PINAAK-3", select Basic authantication, Dafult domain as dyndns.biz, realm as MyServer.dyndns.biz, I create SSL trial with Thawte,but my IIS detected that there is not sufficient information available, and if i use self assigned cerificate with selfssl, At subcriber my IP cant be resolved, - I create subcriber with pull subcription,give https://MyServer.dyndns.biz/TestPublication/replisapi.dll address, running its agent under SQL server agent account.I try web synchronization two times, first with https://***.**.**.***(My static IP)/TestPublication/replisapi.dll address, and configure all its related items as this address, create self ssl for that with static IP as its common name, At subcriber i get diagnosis window successful, and at authantication I gave MyServernameAdministrator. But at second time login it ask again my UserName, Password.Here the problem is, at subcriber when i click View Subscrption status,"Specified File not found",error occured. At second time I try with address https://MyServer.dyndns.biz/TestPublication/replisapi.dll, and this time also dignosis window is successful, but it ask me UserName, Password if i enter dignosis mode again. Here the problem is error "The Proxy Auto-configuration URL was not found.", comes.
  2. vyasdev2005 New Member

    Here is the event log***************************************************************This log comes to Subcriber job history, when address is https://MyServer.dyndns.biz/TestPublication/replisapi.dll-----------------------------------------------------------------------------------------------------------a> Date4/1/2009 8:29:27 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID1ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step NameRun agent.Duration00:00:00Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0MessageThe replication agent has been successfully started. See the Replication Monitor for more information.b> Date4/1/2009 8:29:27 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID1ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step NameRun agent.Duration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0Message-XCancelEventHandle 000004142009-04-01 14:59:27.671 Connecting to Subscriber 'PINAAK-1PINAAK1'2009-04-01 14:59:27.812 Connecting to Subscriber 'PINAAK-1PINAAK1'2009-04-01 14:59:27.843 The upload message to be sent to Publisher 'PINAAK-3PINAAK3' is being generated2009-04-01 14:59:27.843 The merge process is using Exchange ID '3148BDDD-384E-4F63-9EC6-A596612FDCE5' for this web synchronization session.2009-04-01 14:59:30.421 The Proxy Auto-configuration URL was not found.2009-04-01 14:59:30.421 Category:NULLSource: Merge ProcessNumber: -2147209324Message: The Proxy Auto-configuration URL was not found.2009-04-01 14:59:30.421 Category:NULLSource: Merge Process(Web Sync Client)Number: -2147023888Message: The Merge Agent could not connect to the URL 'https://pinaak3.dyndns.biz/TestPublication/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.c> Date4/1/2009 8:29:27 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID1ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step NameRun agent.Duration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0MessageExecuted as user: Pinaak-1Administrator. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. The step failed.d >Date4/1/2009 8:29:27 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID0ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step Name(Job outcome)Duration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0MessageThe job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).-------------------------------------------------------------------------------------------------------------This log comes to Subcriber job history, when address is https://MyServer.dyndns.biz/TestPublication/replisapi.dll-------------------------------------------------------------------------------------------------------------a>Date4/1/2009 8:46:49 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID1ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step NameRun agent.Duration00:00:00Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0MessageThe replication agent has been successfully started. See the Replication Monitor for more information.b> Date4/1/2009 8:46:49 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID1ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step NameRun agent.Duration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0Message-XCancelEventHandle 000004402009-04-01 15:16:49.562 Connecting to Subscriber 'PINAAK-1PINAAK1'2009-04-01 15:16:49.687 Connecting to Subscriber 'PINAAK-1PINAAK1'2009-04-01 15:16:49.734 The upload message to be sent to Publisher 'PINAAK-3PINAAK3' is being generated2009-04-01 15:16:49.765 The merge process is using Exchange ID '525DD6A9-1A59-4D2B-9DD4-4DE48BA5FDBC' for this web synchronization session.2009-04-01 15:16:52.125 The Proxy Auto-configuration URL was not found.2009-04-01 15:16:52.125 Category:NULLSource: Merge ProcessNumber: -2147209324Message: The Proxy Auto-configuration URL was not found.2009-04-01 15:16:52.125 Category:NULLSource: Merge Process(Web Sync Client)Number: -2147023888Message: The Merge Agent could not connect to the URL 'https://219.64.82.212/TestPublication/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.c > Date4/1/2009 8:46:49 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID1ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step NameRun agent.Duration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0MessageExecuted as user: Pinaak-1Administrator. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. The step failed.d> Date4/1/2009 8:46:49 PMLogJob History (PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0)Step ID0ServerPINAAK-1PINAAK1Job NamePINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0Step Name(Job outcome)Duration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0MessageThe job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).+++++++++++++++++++++++++++++++++++++++++Here is th log at System Event Log--------------------------------------------------------------------------------------------------------------Event log:SQL Server Scheduled Job 'PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0' (0x3710058FCC349B479E94B09297DF0AF4) - Status: Failed - Invoked on: 2009-04-01 20:35:30 - Message: The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).22>> DCOM was unable to communicate with the computer PINAAK-3 using any of the configured protocols.The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate.33>>SQL Server Scheduled Job 'PINAAK-3PINAAK3-PubTest-TestPub-PINAAK-1PINAAK1-WebSynch- 0' (0x3710058FCC349B479E94B09297DF0AF4) - Status: Failed - Invoked on: 2009-04-01 20:31:40 - Message: The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).Here Pinaak-3 is Publisher server, Pinaak-1 is subcriber server.
  3. satya Moderator

    Welcome to the forums.
    I believe the main issue could occur if you didn't install/used trusted certificate root CA certification on the client box.
    Since Web sync is based on SSL and web sync starts in the backgroud, if trusted certificate of root CA is not installed
    on the client, it may prompt a dialog in the background and cause this error.Proxy issue occurs if the Merge agent is not using same settings as IE of Proxy serve within your enterprise network.
    Also it could be a security issues, such as privileges for the account used on SQLAgent within the IE security policies.
  4. vyasdev2005 New Member

    Thank for Reply,
    I have Installed thawte trusted root certificate at both server and client side, So how to do same setting for Merge Agent As IE Proxy Setting, However I am not using any proxy, I am testing it on dedicated internet connections. If the problem with SQLAgent and IE Security Policy, How to set it?
    Thanks in advance...

Share This Page