Showing posts with label message. Show all posts
Showing posts with label message. Show all posts

Monday, March 26, 2012

Merge Replication using Web Sync - Proxy Auto config problem

Hi

I am trying to setup merge replication using web sync. I keep on getting the message: The Proxy Auto-configuration URL was not found. Yes I have read all the postings telling me to check my internet explorer settings concerning proxy server and auto-detection - I am not using a proxy - auto detection is unchecked.

Does anyone have another clue?

Thanks

Alex

2006-08-16 15:31:09.375 Connecting to Subscriber 'CRAW'
2006-08-16 15:31:09.437 Connecting to Subscriber 'CRAW'
2006-08-16 15:31:09.453 The upload message to be sent to Publisher 'CRAW' is being generated
2006-08-16 15:31:09.453 The merge process is using Exchange ID '20E2BF4F-8812-431F-8BF8-94A44B80C16E' for this web synchronization session.
2006-08-16 15:31:09.500 The Proxy Auto-configuration URL was not found.

After having no clue where to go on I decided to try it again setting it up using RMO.

Worked without even mentioning the proxy auto config

Imports Microsoft.SqlServer.Replication

Imports Microsoft.SqlServer.Management.Common

Public Class Replication

Private subscriberName As String

Private publisherName As String

Private windowsLogin As String

Private windowsPWD As String

Private publicationName As String

Private publicationDbName As String

Private subscriptionDbName As String

Private Hostname As String

Sub New(ByVal EntityID As Guid, ByVal SubscriberHost As String, ByVal PublisherHost As String, ByVal Login As String, ByVal PWD As String, ByVal Publication As String, ByVal PublicationDB As String, ByVal SubscriptionDB As String)

subscriberName = SubscriberHost

publisherName = PublisherHost

'the guid of the entity is passed as hostname to be used for filtering

Hostname = EntityID.ToString.ToUpper

windowsLogin = Login

windowsPWD = PWD

publicationName = Publication

subscriptionDbName = SubscriptionDB

publicationDbName = PublicationDB

End Sub

Sub SetupWebPull()

Dim webSyncUrl As String = "https://myhost/websync/replisapi.dll"

'Create connections to the Publisher and Subscriber.

Dim subscriberConn As ServerConnection = New ServerConnection(subscriberName)

Dim publisherConn As ServerConnection = New ServerConnection(publisherName)

' Create the objects that we need.

Dim publication As MergePublication

Dim subscription As MergePullSubscription

Try

' Connect to the Subscriber.

subscriberConn.Connect()

' Ensure that the publication exists and that

' it supports pull subscriptions and Web synchronization.

publication = New MergePublication()

publication.Name = publicationName

publication.DatabaseName = publicationDbName

publication.ConnectionContext = publisherConn

If publication.LoadProperties() Then

If (publication.Attributes And PublicationAttributes.AllowPull) = 0 Then

publication.Attributes = publication.Attributes _

Or PublicationAttributes.AllowPull

End If

If (publication.Attributes And PublicationAttributes.AllowWebSynchronization) = 0 Then

publication.Attributes = publication.Attributes _

Or PublicationAttributes.AllowWebSynchronization

End If

' Define the pull subscription.

subscription = New MergePullSubscription()

subscription.ConnectionContext = subscriberConn

subscription.PublisherName = publisherName

subscription.PublicationName = publicationName

subscription.PublicationDBName = publicationDbName

subscription.DatabaseName = subscriptionDbName

subscription.HostName = hostname

subscription.CreateSyncAgentByDefault = True

' Specify the Windows login credentials for the Merge Agent job.

subscription.SynchronizationAgentProcessSecurity.Login = windowsLogin

subscription.SynchronizationAgentProcessSecurity.Password = windowsPWD

' Enable Web synchronization.

subscription.UseWebSynchronization = True

subscription.InternetUrl = webSyncUrl

' Specify the same Windows credentials to use when connecting to the

' Web server using HTTPS Basic Authentication.

subscription.InternetSecurityMode = AuthenticationMethod.BasicAuthentication

subscription.InternetLogin = windowsLogin

subscription.InternetPassword = windowsPWD

' Create the pull subscription at the Subscriber.

subscription.Create()

Dim registered As Boolean = False

' Verify that the subscription is not already registered.

For Each existing As MergeSubscription In publication.EnumSubscriptions()

If existing.SubscriberName = subscriberName Then

registered = True

End If

Next

If Not registered Then

' Register the local subscription with the Publisher.

publication.MakePullSubscriptionWellKnown(subscriberName, subscriptionDbName, SubscriptionSyncType.Automatic, MergeSubscriberType.Local, 0)

End If

Else

' Do something here if the publication does not exist.

Throw New ApplicationException(String.Format("The publication '{0}' does not exist on {1}.", publicationName, publisherName))

End If

Catch ex As Exception

' Implement the appropriate error handling here.

Throw New ApplicationException(String.Format("The subscription to {0} could not be created.", publicationName), ex)

Finally

subscriberConn.Disconnect()

publisherConn.Disconnect()

End Try

End Sub

Sub PullMergeReplication()

' Create a connection to the Subscriber.

Dim conn As ServerConnection = New ServerConnection(subscriberName)

Dim subscription As MergePullSubscription

Try

' Connect to the Subscriber.

conn.Connect()

' Define subscription properties.

subscription = New MergePullSubscription()

subscription.ConnectionContext = conn

subscription.DatabaseName = subscriptionDbName

subscription.PublisherName = publisherName

subscription.PublicationDBName = publicationDbName

subscription.PublicationName = publicationName

' If the pull subscription and the job exists, start the agent job.

If subscription.LoadProperties() And Not subscription.AgentJobId Is Nothing Then

subscription.SynchronizeWithJob()

Else

' Do something here if the subscription does not exist.

Throw New ApplicationException(String.Format("A subscription to '{0}' does not exists on {1}", publicationName, subscriberName))

End If

Catch ex As Exception

' Do appropriate error handling here.

Throw New ApplicationException("The subscription could not be synchronized.", ex)

Finally

conn.Disconnect()

End Try

End Sub

End Class

|||?

I ran into a similar problem. It could be related to certificates. How did you generate your certificate?


--
Hilary Cotter

|||it is a problem with CA certificate;
on subscriber:
1. log on as user from which you try to run sync application
(if it is a windows service log on as service account)
2. install CA certificate ("Automatically select certificate store...")
3. test web page in IE (https://site_location/replisapi.dll)
4. In "Internet Options" -> "Connections" -> "Lan Settings" uncheck "Automatically detect settings"
5. run sync app.
6. enjoysql

Merge Replication using Web Sync - Proxy Auto config problem

Hi

I am trying to setup merge replication using web sync. I keep on getting the message: The Proxy Auto-configuration URL was not found. Yes I have read all the postings telling me to check my internet explorer settings concerning proxy server and auto-detection - I am not using a proxy - auto detection is unchecked.

Does anyone have another clue?

Thanks

Alex

2006-08-16 15:31:09.375 Connecting to Subscriber 'CRAW'
2006-08-16 15:31:09.437 Connecting to Subscriber 'CRAW'
2006-08-16 15:31:09.453 The upload message to be sent to Publisher 'CRAW' is being generated
2006-08-16 15:31:09.453 The merge process is using Exchange ID '20E2BF4F-8812-431F-8BF8-94A44B80C16E' for this web synchronization session.
2006-08-16 15:31:09.500 The Proxy Auto-configuration URL was not found.

After having no clue where to go on I decided to try it again setting it up using RMO.

Worked without even mentioning the proxy auto config

Imports Microsoft.SqlServer.Replication

Imports Microsoft.SqlServer.Management.Common

Public Class Replication

Private subscriberName As String

Private publisherName As String

Private windowsLogin As String

Private windowsPWD As String

Private publicationName As String

Private publicationDbName As String

Private subscriptionDbName As String

Private Hostname As String

Sub New(ByVal EntityID As Guid, ByVal SubscriberHost As String, ByVal PublisherHost As String, ByVal Login As String, ByVal PWD As String, ByVal Publication As String, ByVal PublicationDB As String, ByVal SubscriptionDB As String)

subscriberName = SubscriberHost

publisherName = PublisherHost

'the guid of the entity is passed as hostname to be used for filtering

Hostname = EntityID.ToString.ToUpper

windowsLogin = Login

windowsPWD = PWD

publicationName = Publication

subscriptionDbName = SubscriptionDB

publicationDbName = PublicationDB

End Sub

Sub SetupWebPull()

Dim webSyncUrl As String = "https://myhost/websync/replisapi.dll"

'Create connections to the Publisher and Subscriber.

Dim subscriberConn As ServerConnection = New ServerConnection(subscriberName)

Dim publisherConn As ServerConnection = New ServerConnection(publisherName)

' Create the objects that we need.

Dim publication As MergePublication

Dim subscription As MergePullSubscription

Try

' Connect to the Subscriber.

subscriberConn.Connect()

' Ensure that the publication exists and that

' it supports pull subscriptions and Web synchronization.

publication = New MergePublication()

publication.Name = publicationName

publication.DatabaseName = publicationDbName

publication.ConnectionContext = publisherConn

If publication.LoadProperties() Then

If (publication.Attributes And PublicationAttributes.AllowPull) = 0 Then

publication.Attributes = publication.Attributes _

Or PublicationAttributes.AllowPull

End If

If (publication.Attributes And PublicationAttributes.AllowWebSynchronization) = 0 Then

publication.Attributes = publication.Attributes _

Or PublicationAttributes.AllowWebSynchronization

End If

' Define the pull subscription.

subscription = New MergePullSubscription()

subscription.ConnectionContext = subscriberConn

subscription.PublisherName = publisherName

subscription.PublicationName = publicationName

subscription.PublicationDBName = publicationDbName

subscription.DatabaseName = subscriptionDbName

subscription.HostName = hostname

subscription.CreateSyncAgentByDefault = True

' Specify the Windows login credentials for the Merge Agent job.

subscription.SynchronizationAgentProcessSecurity.Login = windowsLogin

subscription.SynchronizationAgentProcessSecurity.Password = windowsPWD

' Enable Web synchronization.

subscription.UseWebSynchronization = True

subscription.InternetUrl = webSyncUrl

' Specify the same Windows credentials to use when connecting to the

' Web server using HTTPS Basic Authentication.

subscription.InternetSecurityMode = AuthenticationMethod.BasicAuthentication

subscription.InternetLogin = windowsLogin

subscription.InternetPassword = windowsPWD

' Create the pull subscription at the Subscriber.

subscription.Create()

Dim registered As Boolean = False

' Verify that the subscription is not already registered.

For Each existing As MergeSubscription In publication.EnumSubscriptions()

If existing.SubscriberName = subscriberName Then

registered = True

End If

Next

If Not registered Then

' Register the local subscription with the Publisher.

publication.MakePullSubscriptionWellKnown(subscriberName, subscriptionDbName, SubscriptionSyncType.Automatic, MergeSubscriberType.Local, 0)

End If

Else

' Do something here if the publication does not exist.

Throw New ApplicationException(String.Format("The publication '{0}' does not exist on {1}.", publicationName, publisherName))

End If

Catch ex As Exception

' Implement the appropriate error handling here.

Throw New ApplicationException(String.Format("The subscription to {0} could not be created.", publicationName), ex)

Finally

subscriberConn.Disconnect()

publisherConn.Disconnect()

End Try

End Sub

Sub PullMergeReplication()

' Create a connection to the Subscriber.

Dim conn As ServerConnection = New ServerConnection(subscriberName)

Dim subscription As MergePullSubscription

Try

' Connect to the Subscriber.

conn.Connect()

' Define subscription properties.

subscription = New MergePullSubscription()

subscription.ConnectionContext = conn

subscription.DatabaseName = subscriptionDbName

subscription.PublisherName = publisherName

subscription.PublicationDBName = publicationDbName

subscription.PublicationName = publicationName

' If the pull subscription and the job exists, start the agent job.

If subscription.LoadProperties() And Not subscription.AgentJobId Is Nothing Then

subscription.SynchronizeWithJob()

Else

' Do something here if the subscription does not exist.

Throw New ApplicationException(String.Format("A subscription to '{0}' does not exists on {1}", publicationName, subscriberName))

End If

Catch ex As Exception

' Do appropriate error handling here.

Throw New ApplicationException("The subscription could not be synchronized.", ex)

Finally

conn.Disconnect()

End Try

End Sub

End Class

|||?

I ran into a similar problem. It could be related to certificates. How did you generate your certificate?


--
Hilary Cotter

|||it is a problem with CA certificate;
on subscriber:
1. log on as user from which you try to run sync application
(if it is a windows service log on as service account)
2. install CA certificate ("Automatically select certificate store...")
3. test web page in IE (https://site_location/replisapi.dll)
4. In "Internet Options" -> "Connections" -> "Lan Settings" uncheck "Automatically detect settings"
5. run sync app.
6. enjoy

Friday, March 23, 2012

Merge Replication Schema Sync Problems

I am using a merge publication set to synchronize schema changes. Why am I getting the following message when I try to sync after having added columns in the publication database using ALTER TABLE statements?

The schema definition of the destination table ... in the subscription database does not match the schema definition of the source table in the publication database. Reinitialize the subscription without a snapshot after ensuring that the schema definition of the destination table is the same as the source table.

Also, why doesn't reinitializing the subscription with @.upload_first = false not fix the problem?

I have encountered this problem with both merge replication and with transactional replication

When you add columns at the publisher they do not always get published correctly. You can check in the GUI for the properties of the article and will sometimes see that the new columns are not checked.

I have found that it is necessary to either use the GUI or TSQL to explicitly add the missing columns to the publication. If you have tried to merge resync before doing this then I think that you will need to reinitialise your subscriptions

In my experience this behaviour seems to happen frequently with transactional replication, but only occasionally with merge replication

reinit with upload first won't fix the problem if the merge is attempting to synchronize and enumerate data changes with different schemas on the publisher and subscriber

aero1

Wednesday, March 21, 2012

Merge Replication Problem (Urgent)

Dear All,
I have an error message when I'm trying to synchronize from SQL Server
Ce to SQL Server 2000.
The error message is
"The process could not deliver the snapshot to the subscriber"
I already know that I need to verify that the IIS user your SQL Server
CE Server Agent is running under has READ permissions to this folder.
But I don't know how to verify that?
You can see my sqlserverce authentication and IIS configuration on the
attachement.
Pls give me some ideas to solve it out?
Thanks
Robert Lie
Have a look at
http://msdn.microsoft.com/library/de...bleconnect.asp
"Robert Lie" wrote:

> Dear All,
> I have an error message when I'm trying to synchronize from SQL Server
> Ce to SQL Server 2000.
> The error message is
> "The process could not deliver the snapshot to the subscriber"
> I already know that I need to verify that the IIS user your SQL Server
> CE Server Agent is running under has READ permissions to this folder.
> But I don't know how to verify that?
> You can see my sqlserverce authentication and IIS configuration on the
> attachement.
> Pls give me some ideas to solve it out?
> Thanks
> Robert Lie
>
>
>
>
|||You need to use an alternate snapshot share which you have specified in your
vd creation wizard. I would use anonymous authentication in your code.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:u%23dxwxhoFHA.2904@.tk2msftngp13.phx.gbl...
> Dear All,
> I have an error message when I'm trying to synchronize from SQL Server
> Ce to SQL Server 2000.
> The error message is
> "The process could not deliver the snapshot to the subscriber"
> I already know that I need to verify that the IIS user your SQL Server
> CE Server Agent is running under has READ permissions to this folder.
> But I don't know how to verify that?
> You can see my sqlserverce authentication and IIS configuration on the
> attachement.
> Pls give me some ideas to solve it out?
> Thanks
> Robert Lie
>
>
>
>


sql

Monday, March 12, 2012

Merge replication issues

We are getting a conflict error message "cannot synchronize, row was updated
outside of replication".
We cannot figure out what is causing this.
Can having different foreign key constraints at a publisher and subscriber
level cause problems with merge replication?
Sorry for the lack of information, but hopefully someone can help!
I have not seen that error message, but based upon my own limited
experiences, I can assure you that different constraints could certainly
create issues.
"llihp" <phill_dutton@.hotmail.com> wrote in message
news:428cb301_1@.x-privat.org...
> We are getting a conflict error message "cannot synchronize, row was
> updated
> outside of replication".
> We cannot figure out what is causing this.
> Can having different foreign key constraints at a publisher and subscriber
> level cause problems with merge replication?
> Sorry for the lack of information, but hopefully someone can help!
>
|||perhaps the row was updated by a process which did not trigger the triggers,
i.e. bcp, dts.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"llihp" <phill_dutton@.hotmail.com> wrote in message
news:428cb301_1@.x-privat.org...
> We are getting a conflict error message "cannot synchronize, row was
updated
> outside of replication".
> We cannot figure out what is causing this.
> Can having different foreign key constraints at a publisher and subscriber
> level cause problems with merge replication?
> Sorry for the lack of information, but hopefully someone can help!
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eYHGHAPXFHA.2348@.TK2MSFTNGP14.phx.gbl...
> perhaps the row was updated by a process which did not trigger the
triggers,
> i.e. bcp, dts.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
I'm not sure what bcp is(?), but we aren't using any DTS packages within the
application.
Basically we are running a VB application at the sites, and this is
manipulating all the data within the database which is then susposed to be
sent back to the central server. We are having no issues with inserted rows
being replicated, it is only updates which are proving problematic.
|||Hi,
I am also getting the same error. I have multiple publishers with a central
subscriber ( using merge property -exchangetype 2). Please let me know if
there is any answere to it.
One stange thing that I have noticed is following:
I have Publications on Same Articles at 4 sites . Some articles have 4
insert, 4 update and 4 delete triggers but some articles get only 1 trigger
for update, 1 for delete and 1 for insert. Why is this so?
"llihp" wrote:

> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eYHGHAPXFHA.2348@.TK2MSFTNGP14.phx.gbl...
> triggers,
> I'm not sure what bcp is(?), but we aren't using any DTS packages within the
> application.
> Basically we are running a VB application at the sites, and this is
> manipulating all the data within the database which is then susposed to be
> sent back to the central server. We are having no issues with inserted rows
> being replicated, it is only updates which are proving problematic.
>
>
|||Are all the triggers replication related? There should only be one trigger.
You might need to regenerate and resend your snapshot.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vikas Kohli" <VikasKohli@.discussions.microsoft.com> wrote in message
news:C682F2C2-AFAD-42FC-90C1-F81B1BE12928@.microsoft.com...
> Hi,
> I am also getting the same error. I have multiple publishers with a
central
> subscriber ( using merge property -exchangetype 2). Please let me know if
> there is any answere to it.
> One stange thing that I have noticed is following:
> I have Publications on Same Articles at 4 sites . Some articles have 4
> insert, 4 update and 4 delete triggers but some articles get only 1
trigger[vbcol=seagreen]
> for update, 1 for delete and 1 for insert. Why is this so?
> "llihp" wrote:
the[vbcol=seagreen]
be[vbcol=seagreen]
rows[vbcol=seagreen]

Friday, March 9, 2012

Merge Replication failure message

I'm getting the error message below when trying to synchronise a sql compact database to a sql server 2005 db. Can anyone suggest a reason for this?

RDA works fine, permissions look ok. I've run process monitor and can see the IN/OUT files being created, no ACCESS DENIED messages etc. help!

New Subscription Wizard

- Beginning Synchronization (Success)

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed. Try again.
HRESULT 0x80045901 (29045)

The merge process could not initialize the message file from Subscriber 'D:\Inetpub\wwwroot\Sync\30.59FA6BD9893A_9BFA53BB-1D7C-4E84-967A-799C6FEBFCE3.IN:D:\Inetpub\wwwroot\Sync\30.59FA6BD9893A_9BFA53BB-1D7C-4E84-967A-799C6FEBFCE3.OUT'.
HRESULT 0x80045901 (0)

The operation could not be completed.

- Finalizing Synchronization (Stopped)

- Saving Subscription Properties (Stopped)

Bill, the SQL Server Reconciler is unfortunately one of the less stable parts (IMHO) of merge replication and there seems to be a number of things that can go wrong with it (and the errors are still not that useful). This said, there are a couple of things I would look for. Firstly, are you partitioning your data with filters - each partition will create its own snapshot which takes time, during which repeated syncs will fail - you might want to try a simple publication first. The other thing I would look at is the snapshot agent status (right-click your publication and select View Snapshot Agent Status. From this dialog you can kick off and monitor the creation of snapshots.

Hope this helps

|||Hi Nick,
Thanks for response. I'm not using any filters, so the "simple" :) merge is not working. Also checked the agent status but its just showing me the same error message.

I've looked on google groups since and there are few people who had the same issues in previous versions of CE. Looks like the error code is a "general security failure". So I'm going to over this area once again but i'm not hopeful.
bill.|||Question: Can you access the sync url (eg http://<server>/<virtualdir>/sqlcesa30.dll)? This should return the text string "SQL Server Mobile Server Agent 3.0"|||Accessing the dll works fine.

Will come back to this and try again on a clean machine but I'll have to leave this for now. Thanks for your help.|||

HI Nick, I hope you can help me with my errors....

Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA-USER" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA-USER') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

I have no idea how to solve all this and hope that you can advice me on this...

Your help are sincerely appreciated, thk you..

|||It seems that the account used for SQL Server access does not have the required permissions. Please test with a sa/administrator account to determine that this might be the problem.|||Hi Erik thanks for the reply,
I had the SQL server 2005 reinstall followed by I had this new error HResult 0x80004005 (29061).

Can I just check with do you know how to solve this error:

SQLCeException was unhandled
HResult 2147217865
Native error 0|||

Information about this error is available at: http://msdn2.microsoft.com/en-us/library/ms172357.aspx

Your SQL Server name/credentials are not working:

Failure to connect to SQL Server with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the computer running SQL Server, or the password is incorrect.

|||THks for the information, I am a newbie to SQL do you have any idea how to solve this part?

Many thanks, appreciated it

Merge Replication failure message

I'm getting the error message below when trying to synchronise a sql compact database to a sql server 2005 db. Can anyone suggest a reason for this?

RDA works fine, permissions look ok. I've run process monitor and can see the IN/OUT files being created, no ACCESS DENIED messages etc. help!

New Subscription Wizard

- Beginning Synchronization (Success)

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed. Try again.
HRESULT 0x80045901 (29045)

The merge process could not initialize the message file from Subscriber 'D:\Inetpub\wwwroot\Sync\30.59FA6BD9893A_9BFA53BB-1D7C-4E84-967A-799C6FEBFCE3.IN:D:\Inetpub\wwwroot\Sync\30.59FA6BD9893A_9BFA53BB-1D7C-4E84-967A-799C6FEBFCE3.OUT'.
HRESULT 0x80045901 (0)

The operation could not be completed.

- Finalizing Synchronization (Stopped)

- Saving Subscription Properties (Stopped)

Bill, the SQL Server Reconciler is unfortunately one of the less stable parts (IMHO) of merge replication and there seems to be a number of things that can go wrong with it (and the errors are still not that useful). This said, there are a couple of things I would look for. Firstly, are you partitioning your data with filters - each partition will create its own snapshot which takes time, during which repeated syncs will fail - you might want to try a simple publication first. The other thing I would look at is the snapshot agent status (right-click your publication and select View Snapshot Agent Status. From this dialog you can kick off and monitor the creation of snapshots.

Hope this helps

|||Hi Nick,
Thanks for response. I'm not using any filters, so the "simple" :) merge is not working. Also checked the agent status but its just showing me the same error message.

I've looked on google groups since and there are few people who had the same issues in previous versions of CE. Looks like the error code is a "general security failure". So I'm going to over this area once again but i'm not hopeful.
bill.|||Question: Can you access the sync url (eg http://<server>/<virtualdir>/sqlcesa30.dll)? This should return the text string "SQL Server Mobile Server Agent 3.0"|||Accessing the dll works fine.

Will come back to this and try again on a clean machine but I'll have to leave this for now. Thanks for your help.|||

HI Nick, I hope you can help me with my errors....

Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA-USER" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA-USER') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

I have no idea how to solve all this and hope that you can advice me on this...

Your help are sincerely appreciated, thk you..

|||It seems that the account used for SQL Server access does not have the required permissions. Please test with a sa/administrator account to determine that this might be the problem.|||Hi Erik thanks for the reply,
I had the SQL server 2005 reinstall followed by I had this new error HResult 0x80004005 (29061).

Can I just check with do you know how to solve this error:

SQLCeException was unhandled
HResult 2147217865
Native error 0|||

Information about this error is available at: http://msdn2.microsoft.com/en-us/library/ms172357.aspx

Your SQL Server name/credentials are not working:

Failure to connect to SQL Server with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the computer running SQL Server, or the password is incorrect.

|||THks for the information, I am a newbie to SQL do you have any idea how to solve this part?

Many thanks, appreciated it

Merge replication fails with odd message

Hi Guys,

I've got a merge replication set up between boxes. They're on separate sites both behind an ADSL Nat modem router. The publisher connects to the subscriber via a port forward / Nat translation at the router. This replication set up has been running for some months now. This morning I got this failure message from the merge agent on the publisher.

"the specified remote server name may not be the network name of the remote server or the remote server is unreachable due to network problems. The step failed"

Currently the Enterprise Mgr at the publisher can see the subscriber as can query analyzer running on the publisher.

The host name of the subscriber is the same name used in the server registration at the publisher. The registration uses a Client Network Utility alias to resolve the name.

If I run a ping command at the publisher using the subscribers name I get replies (the resolution of that name is done via a hosts file entry)

Both machines are Win2k Server boxes running SQL Server 2000 Standard.

Any ideas why the agent can't see the subscriber despite the fact its usual communications channel is working just fine?I've still no idea why I was getting this behaviour but I've reinitialised the subscriptions now and the problem's 'gone'.

Wednesday, March 7, 2012

merge replication error - could not find stored procedure ''.

Hi
I have a client which has a merge subscription - anonymous ftp
When synchronising we see the following error message at the publisher:
Error Message:
The merge process could not retrieve column information for table
'dbo.Transfer'.
(Source: Merge Replication Provider (Agent); Error number: -2147201016)
------
Could not find stored procedure ''.
(Source: LOUISEPC (Data source); Error number: 2812)
------
What does this mean ?
Thanks
Bruce
does this help?
http://support.microsoft.com/default...b;en-us;308743
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bruce Baker" <bruceb@.ardex.com.au> wrote in message
news:%23DHMBbVrFHA.1168@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have a client which has a merge subscription - anonymous ftp
> When synchronising we see the following error message at the publisher:
> Error Message:
> The merge process could not retrieve column information for table
> 'dbo.Transfer'.
> (Source: Merge Replication Provider (Agent); Error number: -2147201016)
> ----
--
> Could not find stored procedure ''.
> (Source: LOUISEPC (Data source); Error number: 2812)
> ----
--
>
> What does this mean ?
> Thanks
> Bruce
>
>
|||Not really - it was working - for some reason the procs for the table are
missing from the sysmergearticles table.
Any bright ideas on repopulating that table ? Wonder what else is bung....
Thanks
Bruce
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%233tiAZprFHA.1252@.TK2MSFTNGP09.phx.gbl...
> does this help?
> http://support.microsoft.com/default...b;en-us;308743
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Bruce Baker" <bruceb@.ardex.com.au> wrote in message
> news:%23DHMBbVrFHA.1168@.TK2MSFTNGP10.phx.gbl...
> --
> --
>
|||You can manually populate these tables with the correct procs. It will be
somewhat difficult to figure out what these procs names should be. You will
have to open these procs to find out which underlying tables they populate
and go from there.
You are best in the long run to drop the subscribers, and then re deploy
them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bruce Baker" <bruceb@.newsgroups.nospam> wrote in message
news:OiBu4NurFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Not really - it was working - for some reason the procs for the table are
> missing from the sysmergearticles table.
> Any bright ideas on repopulating that table ? Wonder what else is
bung....[vbcol=seagreen]
> Thanks
> Bruce
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%233tiAZprFHA.1252@.TK2MSFTNGP09.phx.gbl...
-[vbcol=seagreen]
-
>

Saturday, February 25, 2012

Merge Replication between MSDE2000 and SQL 2005

Hi, I want to ask about SQL Merge replication between 40 MSDE2000 as
Publishers and SQL 2005 as Subscriber.
I received an error message while configuring the replication saying "For
Merge publications, The version of the subscriber must not exceed the version
of the publisher"
Is there a way to do the configuration without upgrading the MSDE2000 to
MSDE Express or downgrading from SQL 2005 to SQL 2000?
Thanks in advance,
Rodney El Hajj
Systems Engineer
Lebanese Canadian Bank
Using your current hardware, you could possibly change the topology to have
the SQL 2005 machine as the publisher and the MSDE boxes as subscribers.
Sometimes, when the data is partitioned, there is little distinction between
publisher and subscriber in merge replication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Tx for your quick answer, but I need one way replication, from remote sites
to Head Office. At the end of day, I need to merge data from all sites in one
database.
We used to have an SQL 2000 Server at the Head Office and MSDE 2000 on all
sites, the merge replication was working without problems. Then, we moved to
another hardware and installed SQL 2005 instead of 2000, since then we are
facing problems with the replication configuration.
BR,
"Paul Ibison" wrote:

> Using your current hardware, you could possibly change the topology to have
> the SQL 2005 machine as the publisher and the MSDE boxes as subscribers.
> Sometimes, when the data is partitioned, there is little distinction between
> publisher and subscriber in merge replication.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
|||One-way replication presumably means that you want the data to flow in one
direction but this can be achieved from subscriber to publisher as well as
the other way around. The central publisher can
be a central repository of the data, as unintuitive as this sounds
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Hi Again,
I tried to do the replication from subscriber to publisher (The Publisher is
centralized) but didn't succeed.
Can you provide me with a step by step merge replication procedure. Maybe
I'm missing some settings.
Thanks in advance.
"Paul Ibison" wrote:

> One-way replication presumably means that you want the data to flow in one
> direction but this can be achieved from subscriber to publisher as well as
> the other way around. The central publisher can
> be a central repository of the data, as unintuitive as this sounds
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
>

Merge replication and spids left behind

I posted this message under the comp.databases.ms-sqlserver group and
someone mentioned I should post it here:
We are using Merge replication with clients from remote offices (SQL
2000, sp3). Recently, I have had a problem with users who are
replicating, and they shut down their laptops. The connection never
dies, and I end up with major blocking issues related to the
"orphaned" spid. The tables that are blocked are used to filter data
on each client. Since the orphaned spid is blocking, backups will run
forever, and have to be killed, and a SQL management job that
inserts/updates data in these tables has to be killed.
If I kill the spid, it shows a rollback at 0% and the status never
changes. The user has disconnected, and there is really nothing to
roll back. How can I get rid of this spid with out restarting SQL
server, or rebooting my server?
Any help would be greatly appreciated.
Thanks,
Amy M
I wish I could help you Amy. I have run into similar problems like this (but
not with replication), and I would have to power off my server to fix it. I
was unable to shut down the server using the shutdown command.
I suggest you open a support incident with PSS on this one.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Amy M" <amarshall@.rhtc.net> wrote in message
news:119d3885.0408120229.3e585a78@.posting.google.c om...
> I posted this message under the comp.databases.ms-sqlserver group and
> someone mentioned I should post it here:
> We are using Merge replication with clients from remote offices (SQL
> 2000, sp3). Recently, I have had a problem with users who are
> replicating, and they shut down their laptops. The connection never
> dies, and I end up with major blocking issues related to the
> "orphaned" spid. The tables that are blocked are used to filter data
> on each client. Since the orphaned spid is blocking, backups will run
> forever, and have to be killed, and a SQL management job that
> inserts/updates data in these tables has to be killed.
> If I kill the spid, it shows a rollback at 0% and the status never
> changes. The user has disconnected, and there is really nothing to
> roll back. How can I get rid of this spid with out restarting SQL
> server, or rebooting my server?
> Any help would be greatly appreciated.
> Thanks,
> Amy M

Monday, February 20, 2012

merge replication agent error

Hello,
i have problem with merge replication agent. the agent stops with error message
"Der Prozess konnte die ?nderungen auf 'Subscriber' nicht aufz?hlen."
"The process could not enumerate changes at the 'Subscriber'."
Repl Agent Status: 2
Percent Complete: 0
Category:NULL
Source: Mergereplikationsprovider
Number: -2147200999
Has anyone an idea, what's the reason for this?
the merge replication process has been setup successfully in this database szenario and worked without errors. after adding a additional table to the replication schema and new setup of merge replication, the described error occurs.
Thank you for Your comments,
regards
RenéHelbig
Rene,
this is a generic , high-level error message simply indicating that the
merge agent ran into a problem moving changes from the subscriber to the
publisher. It can be caused by several different problems, and is not
necessarily a bug.
To get more info, you could enable logging on the merge agent (-output
c:\somefile.log -outputverboselevel 3) - see
http://support.microsoft.com/?id=312292.
Alternatively, most of these merge errors are solved by simply restarting
the merge agent.
HTH,
Paul Ibison