SQL Server 2000 :The Process Could Not Deliver The Snapshot To The Subscriber.

Jul 9, 2007

Hi Sql Gurus.

Please help me i'm in troublle now.

I have Two databases,that same schemas and same tables. that both servers are different location. but data must be update and input from both sites.that data must be same both.

so i've planed to replication data both servers,then i must chose merge replication right?

so i'm set

server1 (assumed server1 as main) are Distributor/Publisher

and

server2 just Subscriber only

that i can configuration successfully.

then i'm chose push replication from server1 but it's not work.

this is error message that show



The process could not deliver the snapshot to the Subscriber.



please advise me what's wrong and how to fix problem?

Thank you.

View 5 Replies


ADVERTISEMENT

The Process Could Not Deliver The Snapshot To The Subscriber, Using WebSynchronisation 2 Server Setup

Jan 29, 2007



I am Having trouble trying to set up SQL Server Replication Utilising Web Synchronisation Where the
IIS(Web Server) is on a separate machine to the SQL Server(Publisher). I am using MSDE as the SQL Server Box, however even when I used SQLServer2000, or SQLServer2005 I have had no joy with the 2 separate Servers setup.

If I have the one server then I have no problems (i.e. One Server Setup)
Server A: Windows 2000,
with MSDE installed
enabled for Merge replication,
and has a Publication set up.
IIS Web Page Setup for Synchronisation

My SQL Server 2005 Mobile device syncs via the web page on ServerA Fine, no problems at all.


The Trouble is when I am trying to utilise SQL Server Replication as follows. (i.e. 2 Server Setup)

Basically I am using the Same ServerA as in the one Server setup I had above. All I have done is I am now using a Separate IIS Server for the Web Synchronisation ServerB
I have run the "Configure Web Synchronisation Wizard"(ConnWiz30.exe) on my web page on ServerB. And I am using Anonymous Access Authentication With Windows NT Authentication on my Web Server(ServerB),
the Anonymous User is a Domain user, and is the Same Domain User I used in the One Server setup which I had working (so this IIS Anonymous Domain user should have all permissions required on the ServerA (SQL Publisher) both Windows permissions and SQL Server Permissions.


Server A: Windows 2000,
with MSDE installed
enabled for Merge replication,
and has a Publication set up.

Server B: Windows XP, IIS Web Server(Web page enabled for Web Synchronisation)

I have a Mobile device as a subscriber, which is using Web Synchronisation on ServerB(Web Server), to sync with the ServerA (MSDE Box).
The error I am receiving is "A Call to SQL Server Reconciler has Failed" Try to resynchronise, "The Process Could Not deliver the Snapshot to the Subscriber"


A little extra info:
-I can remotely connect from my Web server(ServerB) to the SQL Box ServerA via a TCP/IP ODBC connection so remote connections does not seem to be an issue.

-If on My Mobile device if I try to Add a Subscription & Synchronise the replication using the
AddSubscription(AddOption.ExistingDatabase), it works fine. (Obviously the subscription database does exist before the synchronisation)

If I try to Add a Subscription & Synchronise the replication using the
AddSubscription(AddOption.CreateDatabase), I get the error as mentioned.

Is there something I have missed? Any help you can provide is much appreciated.

Thanks.

View 4 Replies View Related

Process Could Note Deliver Updates (s) At The Publisher

Feb 19, 2007

I have created a publisher with row filtering using merge replication .I configured 5-6 subscribers for it.It was working fine for 2 months.But now for two subscribers its showing an error Process could not deliver update (s) at the publisher



Ive checked the job history..its showing



Merge process encountered an unexpected network error. The connection to tublisher 'Publishername' is no longer available



can any one help me?



thanks and regards

Dhanya







View 3 Replies View Related

Fail To Deliver SSRS Report To A Share Folder In WINDOWS 2000 Server

Apr 29, 2008

SQL server 20005 SP2 is install in my WIN XP machine. I implement a SSRS report and try to deliver the report to a share folder in window 2000 server.

I create and set permissions on a shared folder as per the information in http://msdn2.microsoft.com/en-us/library/ms345228.aspx. The account that I use in subscription is local admin account in the target machine.

I have try path \<servername>c$XXX and \<servername>XXX. Both is not ok.

I find following error message in the log file of reporting service.

ReportingServicesService!library!d!04/29/2008-00:03:40:: e ERROR: Throwing Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: A logon error occurred when attempting to access the file share. The user account or password is not valid., A logon error occurred when attempting to access the file share. The user account or password is not valid.;
Info: Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: A logon error occurred when attempting to access the file share. The user account or password is not valid. ---> System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.GetImpersonationToken(String userName, String domain, String userPwd)
--- End of inner exception stack trace ---



If I try to deliver same report to a share folder in WIN XP in the same way. It is ok.

View 7 Replies View Related

Moving Snapshot From Distributor To Subscriber...

Aug 22, 2007

Hi all

Can the Snapshot be copied from the distributor to the subscriber and then from the subscriber using the copied snapshot, create a subscription to the publisher?

Urgent help would be greatly appreciated

WARNING: Running on cold coffee!

View 3 Replies View Related

Problem After Applying Snapshot Publication To Subscriber

Jul 13, 2006

Hello all,

I have a unusual problem with a snapshot publication that I am having a hard time troubleshooting. The servers in question are all SQL 05 Enterprise. Here is the scenario:

Staging Server - This server acts as the publisher of the snapshot
Production Server - This server is the subscriber of the staging snapshot
Cascade Servers - These servers receive transactional updates from the production server

The staging server applies the snapshot to production successfully. From there the production server has a transactional publication which the subscribers are the cascade servers.

This model worked for a long time where we would generate the snapshot apply it to production and the updates would be sent to the cascade servers. All of a sudden there is a problem with the transactional publication from production -> cascade. There are 7-10 tables that do not receive the updates and all data in the problematic tables is truncated. The other remaining tables in the subscription receive the updates as needed. Looking at replication monitor and all other logs shows that the transactions are being replicated, but yet the 7-10 problematic tables do not contain any data. The only solution I have found for this is to recreate the entire replication model from scratch.

Any advice on how to handle this scenario? Is my model for using a transactional publication to cascade changes to a subset of servers incorrect?

View 1 Replies View Related

Error While Merging Snapshot Containing A CLR Assembly Schema At The Subscriber

Sep 26, 2007



Hi ,

I urgently need a solution for this. I have configured merge replication between a webhoster and a local machine
and it is working perfectly but when I am adding an article (table) which has a CLR assembly associated with it,
the merge replication is failing saying it cannot apply the schema of the CLR assembly at the client. I think Microsoft
supposedly says in it's documentation that merge replication supports CLR assemblies. I have recreated the snapshot
after selecting the table (article) and I have reinitialised the subscription also but it is just not working. It is the simplest
of replication with just one publisher and one subscriber.

Thanks,
Andy

View 2 Replies View Related

Subscriber Alternate Snapshot Location And Web Sync - 2005 Express

Dec 7, 2005

Hi,

View 6 Replies View Related

Error While Propagating Initial Snapshot To Subscriber (Merge Replication)

Jun 27, 2006

Hi all.

I get the following error when trying to run a pull subscription from the subscriber:

The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
---------------------------------------------------------------------------------------------------------------
The process could not connect to FTP site 'ftp://ESOFTSERVER.NO-IP.INFO' using port 21.
(Source: ESOFT (Agent); Error number: 0)
---------------------------------------------------------------------------------------------------------------
The connection with the server was reset
(Source: (OS); Error number: 12031)
---------------------------------------------------------------------------------------------------------------


I've tried everything I could to solve this problem, but I can't get it working.

Thanks for any advise.

Fabio Reynoso

View 5 Replies View Related

The Process Could Not Connect To Subscriber

May 25, 2008

I have a sql server 2005 database that I have set as the publisher and an sql express database that I have set as the subscriber.

I set it that the 2005 db should push to the sql express db.

when i look at the replication monitor I get an error

The process could not connect to subscriber name/sqlexpress

what can I do to get this working?
I really am trying to just replicate 1 table every minute from the sql 2005 db to the sql express
Please advise?

View 9 Replies View Related

The Process Could Not Enumerate Changes At The 'Subscriber'

Apr 5, 2007

Hi,

I have a problem with merge replication on SQL 2000.



-Publisher is Standard edition, subsriber MSDE

-Both SP4

-It always fails at same table.

- CHECKDB shows no errors

- It worked OK for a quite long period...



-Replication fails with this mesage ('verbose ouput'):



The merge process encountered an unexpected network error. The connection to Subscriber 'SV-LESNOSAOP' is no longer available.
Percent Complete: 0
.
Repl Agent Status: 6
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147200999
Message: The process could not enumerate changes at the 'Subscriber'.
Repl Agent Status: 3
Percent Complete: 0
CategoryQLSERVER
Source: SV-LESNOSAOP
Number: 0
Message: Invalid time format
Repl Agent Status: 3
Percent Complete: 0
CategoryQLSERVER
Source: SV-LESNOSAOP
Number: 0
Message: The merge process timed out while executing a query. Reconfigure the QueryTimeout parameter and retry the operation.
Repl Agent Status: 3
Percent Complete: 0
Category:NULL
Source: Merge Process
Number: -2147199469
Message: The merge process encountered an unexpected network error. The connection to Subscriber 'SV-LESNOSAOP' is no longer available.



Some tables in article are merged succesfully so I don't believe it's a network error.



Anyway I will try to recreate the subscription, but there is a problem that subcriber has more data than publisher, so i have to manualy trasfer (DTS) the data to publisher before the new snapshot is applied.
If this also fails i guess i can assume there is a connectivity problem.



Any comments or suggestions are welcome...

Janez













View 4 Replies View Related

The Merge Process Could Not Enumerate Changes At The 'Subscriber'.

Apr 19, 2006

I have two SQL 2005 Standard servers using merge replication, and out of the blue started getting failure notices regarding "The merge process could not enumerate changes at the 'Subscriber'." I turned on verbose logging and noticed the following section:

2006-04-19 12:53:33.227 Category:NULL
Source: Merge Replication Provider
Number: -2147200999
Message: The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
2006-04-19 12:53:33.227 The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent.
2006-04-19 12:53:33.227 The merge process was unable to update last synchronization information at the Publisher.


Using Profiler on both sides, I don't see anything out the ordinary during the replication process until there are two calls in a row to the stored procedure sp_MSadd_merge_history90, where the second one is storing the error message listed above.

Any ideas?

Thanks,

Scott Davis

View 8 Replies View Related

Merge Process Could Not Enumerate Changes At The Subscriber

Apr 27, 2007

Hi,



I've seen quite a few posts about this error message but so far no answers. I'm merge replicating between SQL Server 2005 SP2 and SQL Server 2005 Mobile. Everything seems to run really well until at some point I get the above error message while running the replication from the device. It seems to happen just after I've made a schema change on the server e.g. the latest one was adding some new columns (which allow nulls) to replicated tables.



I've switched on verbose logging and I get the following:



2007/04/27 13:57:06 Hr=00000000 Compression Level set to 1
2007/04/27 13:57:06 Hr=00000000 Count of active RSCBs = 0
2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 846
2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 1442
2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 846
2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 C:Program FilesMicrosoft SQL Server 2005 Mobile Editionserverctmobilesql30.7AABD0FB7460_010309C7-9030-4CF9-7D60-A64608CD62F7 0
2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="WINSERVER" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CompacTimesheet_Staging" Publication="CompacTimesheet_Staging" ProfileName="DEFAULT" SubscriberServer="CTimeMobile - 7aabd0fb7460" SubscriberDatabasePath="Program FilesCompac TimesheetDataCompacTimesheetMobile.sdf" Distributor="WINSERVER" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="452"/>
2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SYNC Hr=80045019 The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. -2147200999
2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SYNC Hr=80045645 The process was successfully stopped. -2147199419
2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0



The error message doesn't seem very helpful. Is there another way to find out what is causing the problem? I've tried reinitializing all subscriptions and generating a new snapshot but it makes no difference. The only way I've found to fix this is to delete the database on the subscriber and synchronise again (losing all subscriber data since the last sync).



Regards,



Greg

View 3 Replies View Related

Subscriber To A SQL Server 2000 Replication

Oct 31, 2006

Hi ..

I know that SQL Server Express 2005 can subscribet to SQL Server 2000 publications. However, it seems that SQL server 2000 cannot perform a push to SQL Express.

Can anyone refer me to any online help or documentation on how a proper replication can be done between SQL 2005 Exress and SQL 2000??

Thanks

View 1 Replies View Related

URGENT! Error: The Process Could Make A Generation At The 'Subscriber'

Sep 30, 2004

Any help at this stage is welcome!

Due to collation-discrepancies the publisher and subscriber databases have been recreated.
When however I attempt to restart the publishing...SQL gives the message

"The process could not make a generation at the 'Subscriber"

There is enough space on the harddisk of either subscriber or publisher 3Gbyte+
UserRights are ok and I reinitialized the publication.

Everything seems ok and yet I get the error mentionned above.

Can anyone give me some help with this?
Thank you!! :)
VincentJS

View 2 Replies View Related

Snapshot Creation Process Failed

Aug 3, 2007

Hi everyone!

I'm finalizing our merge replication apps but we encountered some problem with the setup. We need to create a parameterized filter publication of 30+ articles. Most of the articles/tables contains large amount of existing data. One of them contains more than 20 millions records. during the creation of snapshot, the snapshot agent runs for a while and it will hang the process. The whole system cant seem to response anymore.

I tried on the other 25 articles with less data, everything was fine. is 20 million too much for snapshot?

Can anyone help me on this?

Thanks

Ben

View 1 Replies View Related

Unable To Create Subscriber On A 2000 Server From A 2005 Server Publisher

Dec 1, 2006

Hi,

I'm trying to set up a transactional replication from SQl Server 2005 to SQl server 2000. The Distributor and the publisher are on our server and the subscription is supposed to be on a SQL 2000 server on a different location. Before upgrading to 2005 I didn't have problems - the replication from 2000 to 2000 was working perfectly.

After I succesfully created the distributor and the publication the first problem that I encountered was that when I tried to create the subscription it was giving me an error that I cannot use an IP to acces the server. I realized to fix that issue by creating an Alias in the SQL Server Configuration Manager for the server where I wanted to create the subscription (a push subscription).

Now when I try to add the subscriber it gives me another message "Execute permission denied on object 'sp_MS_replication_installed', database 'master', owner 'dbo'" - so I cannot create the subscriber.

The user that I use to create the subscriber on the 2000 server is dbo for the subscriber database but it doesn't have rights on the master database. Also I realized that on the 2000 server I still have the old subscription but I cannot delete it - for the same reason - no access on the master database. Before upgrading to 2005 I had the exact same rights on the 2000 server.

Any help would be appreciated.

Thanks.

View 4 Replies View Related

Can SQL Server 2000 Publisher Work Normally With SQL Server 2005 Subscriber ?

Nov 8, 2005

or is there any resource about it?

View 3 Replies View Related

MS SQL Server 2000 Snapshot Agent

Aug 16, 2006

Hello Sir,

Now I'm choosing Trasactional publication as my publication type. I now can successfully replicate the data from publisher to subscriber without any error.

But now my question is what is the usage of snapshot agent? When I go to Replication Monitor > Agents > Snapshot Agents > Start Agent but failed.

I need to check with you whether the way I start the snapshot agent was not correct? What is the effect if I drop snapshot agent during the replication and DBUpdate are running?

Please kindly help me .

Thank You.

View 13 Replies View Related

Snapshot Replication And Schema Change On Sql Server 2000

Aug 10, 2006

can a sql server 2000 snapshot replication

solution handle a schema change.



as far as i know i can't drop a table involved in replication

View 4 Replies View Related

How To Skip Snapshot In Transaction Replication (from SQL Server 2005 To 2000)

Jun 13, 2006

We have two SQL Server 2005 production DB at remote sites. Due to network bandwidth issue, we need to replicate these DBs (publishers and distributers) to central corporate SQL 2000 DB (subscriber for backup and possible reporting (and in rare case as a failover server).

We would start out with backup from SQL 2000 db restored on remote SQL 2005 DBs. When we have DB issue on remote 2005 DB, we want to restore it from central corp. 2000 DB backup. Since two DBs are replicating to central DB, we DO NOT want combined db back up data on restored remote 2005 db. We can restore the db and delete unwanted data before we turn on replication from this restored server. So, this is not a problem.

The real problem is how to avoid snapshot replication (during initialization) when we create a transaction replication on this restored server to avoid over writing data on the central subcriber sql 2000 DB???

HELP!!



View 5 Replies View Related

SQL Server 2000 Merge Replication Process

Jun 22, 2004

Hi,
I am trying to replicate a production database server,on sql server 2000 at a particular geographic location to a new failover database server on sql server 2000 in a different geographic location via internet. The intention here is to use the failover database during times when the production server is down or busy and the synchronization needs to be sceduled for every 10 min.
It will be of huge help if any expert could give the detailed process involved and any precautions that need to be taken. I also need to keep inmind to use the ever/odd sequence number generator during the replication implementation.
Also, Whether to use row-level or column-level tracking?

thanks
SV

View 2 Replies View Related

Controlling Process Priority In SQL Server 2000 - Possible..?

Jun 25, 2007

A similar question has been asked in a different thread, but didn't get a conclusive answer. Is there a way to set process priority on a specific process (alternatively - processes started by a specific user), similar to what the Task Manager allows in Windows?

I need to archive some data from an OLTP database. Unfortunately, some of the tables are growing rather large, and copying the data, and especially removing it based on record age, is a resource-intensive operation. My database must be available 24/7, and I can't have queries timing out, or I start losing business real fast. I was thinking of firing off the archive script and setting the process priority on it to something lower than normal, so it won't interfere with my OLTP processes.

Maybe someone can suggest a better solution?

View 2 Replies View Related

Interrupt Processing Of A Large Insert Process In SQL Server 2000.

Jul 20, 2005

I'm running a resource-intensive stored procedure, which reads a filewith about 50,000 lines with a BULK INSERT into a temp table, thengoes through it and inserts a record for each line into another table.While this procedure is running, SQL server stops accepting any otherrequests coming from the website.Question:Is there a way to make SQL server "listen", or emulate an "interrupt"to other requests while in the middle of a long intensive process?I really appreciate your replies.Thank you,Oleg.

View 5 Replies View Related

Using SSIS Packages To Process SQL Server 2000 OLAP Objects

Nov 16, 2006

Can a SSIS server, i.e. staging server be used to create packages that update SQL Server 2000 Analysis services objects on another server running SQL server 2000 OLAP? 

It appears that the OLAP connection manager ion SSIS supports only connections (and thus updates) to 2005 OLAP objects.  I work for a company that has a huge investment in a 3rd party DW that uses Analysis Services 2000.  the DW tool vendor will not support an upgrade to SSAS 2005.  We wish to extend the DW from other data sources.  My thought was to use a staging server with SSIS, used solely as the ETL tool for all new development (thus no more DTS development), and to update the sql server 2000 operational data store on another box. 

I can find no documentation on how to process sql server 2000 analysis services objects from within an SSIS package.   Any ideas?

 

 

View 4 Replies View Related

32-bit SQL 2000 Publisher And SQL 2005 64-bit SQL Distributor And Subscriber

May 16, 2006

For transactional replication, are there any issues and is it even possible to have 32-bit SQL 2000 publisher and SQL 2005 64-bit distributor and subscriber? Thanks

View 1 Replies View Related

SQL 2000 As Publisher And SQL Express 2005 As Subscriber?

Jan 21, 2006

I want to have transactional replication setup with SQL 2000 as a publisher and SQL Express 2005 as a subscriber? Where can I get some documentation around that?

Basically, the problem I am stuck with is that while registering the subscriber in SQL2000, SQL2000 cannot recognize my SQL Express 2005 instance as a subscriber. I have tried both SQL Ent. Mgr. and sp_addsubscription.

Please help.

Thanks,

Rupak Ganguly

View 1 Replies View Related

SQL 2000 (publisher &&amp; Distributor) &&<&&> SQL 2005 (subscriber) - Is It Possible

Jul 30, 2006

We have a SQL 2000 Server (publisher & distributor) with around 15 databases being replicated (all using merge replication).

My question is the following:

Is it possible to perform Merge replication from a SQL 2000 (acting as the publisher & distributor) to a SQL 2005 server acting as the Subscriber)?

If anyone has a link to any instructions somewhere that would be great.

Thanks

View 3 Replies View Related

SQL Replication: 2005 (Publisher) And A 2000 (Subscriber)???

Sep 25, 2006

Hi,

I was wondering if it is possible to setup replication between a 2005 SQL Publisher and a 2000 SQL Subscriber? Is there any special setup steps I need?

Thanks so much,

David

View 3 Replies View Related

How Do I Configure SQL Server 2005 Reporting Services To Deliver Subscription E-mails To Addresses External To My Windows Domain

Jun 10, 2007

Can anyone help me with a problem I have with SSRS 2005? How do I configure SQL Server 2005 Reporting Services to deliver subscription e-mails to addresses external to my windows domain?

I've been having trouble configuring the Report Server e-mail delivery component to send subscription e-mails to addresses outside the domain on which the report server is hosted.

For e.g. since my local windows domain is named "smartsystems.com", I have found that the Report Manager does not have any problems sending subscription mails to "eawagu@smartsystems.com" but throws up an error whenever I include "eawagu@yahoo.com" in the recipients' list.

Any insights?

View 1 Replies View Related

Transactional Replication From SQL 2000 Sp4 Publisher/distributor To SQL 2005 Sp2 Subscriber

Jun 26, 2007

Hello,



Are there any requirements that dictate the SQL Server version for the distribution agent for a SQL 2000 publisher with a transactional push subscription to a SQL 2005 subscriber?



Thanks in advance,



John

View 3 Replies View Related

Error While Changing Custom Resolver Between 2005 Publisher And 2000 Subscriber

Sep 25, 2007

Hi all,

here is the context of our problem:

- Publisher :

version SQL Server 2005 SP2
table in SQL Server 2000 (80) compatibility level
publication in SQL Server 2000 compatibility level
- Distributor : SQL Server 2005 SP2
- Subscriber : SQL Server 2000 SP4 + hotfixes (version 8.00.2187)

There is only one article in our publication (a simple table with a GUID and a nvarchar(50) columns), and we have left the default resolver.

1 - The first synchronization of the subscription is successfully completed, and it is the same for the different updates/inserts/deletes or conflicts.

2 - Then we change the Resolver of our article by our own COM-Based Custom Resolver (developped in C# 2.0). This resolver only change the default behaviour: the subscriber always win (this is for a test, in the future we will have a complex business logic). All the synchronizations works fine and do what we want in the conflicts.

3 - We rollback the resolver to the default one... and here is the problem!
The synchonizations stop to work correctly. For all of them we've got the same error:



Code SnippetReplprov.dll , 2007/09/25 14:26:07.591, 4000, 16890, S1, ERROR: ErrNo = 0x80045017, ErrSrc = <null>, ErrType = 8, ErrStr = The schema script '
declare @cmd nvarchar(1000)
set @cmd='exec sys.sp_MSchangearticleresolver @article_resolver=@ar, @resolver_clsid=@rc, @artid=@ai, @resolver_info=@ri'
exec dbo.sp_executesql @cmd, N'@ar> nvarchar(255),@rc nvarchar(40),@ai uniqueidentifie..." mailto:N?@ar">N'@armailto:N'@ar">N'@ar</A< A>> nvarchar(255),@rc nvarchar(40),@ai uniqueidentifie...




It is no more possible to synchronize this subscription... Any remark will be helpfull cause we did not find anything on the net concerning this error.

Thanks a lot!

View 3 Replies View Related

Initializing Transactional Replication Without A Snapshot In SQL 2000

Nov 10, 2006

SQL Server 2005 Books Online provides an article entitled, "Initializing a Transactional Subscription without a Snapshot". Is it possible in SQL Server 2000 to initialize transactional replication without a snapshot?

So far, I have been unable to find a similar procedure mentioned in the SQL 2000 Books Online. I was able to follow the 2005 procedure using SQL 2000 until I got to the step that says to enable the "Allow initialization from backup files" option on the "Subscription Options" tab of the "Publication Properties" dialog. But that option does not appear in the SQL 2000 version of the specified dialog box.

Any ideas?

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved