Re: Merge Replication Problems after upgrade to SQL Express

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Tim,

thanks again. I found out that I need to specify QueryTimeout as DWORD
within HKLM\Software\Microsoft\Microsoft SQL
Server\90\Replication\Subscription\<Server>:<Publication>:<Database>. If I
specify 120 there for QueryTimeout synchronization work again and Profiler
shows an execution time of 62241 for sp_MScleanupPullForReinit.

Microsoft should specify a better error message there - that would have
saved me a lot of time.

Greetings,
Thomas

"Tim" wrote:

In my experience the error actually referred to a timeout during the
already mentioned sp_MSCleanupForPullReinit. The stored proc tries to
drop all the tables, stored procs, triggers etc within the timeout
period specified in WSM (default 30 seconds). It would be worth
profiling the client to see at what point the error occurs i.e. is it
exactly 30 seconds (or whatever your timeout is set to) after the
stored proc starts.

On Feb 11, 11:01 am, ThoHot00 <ThoHo...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Hi Hilary,

I applied the hotfix on the server and client now, restarted both machines
and the error is still there.

Greetings,
Thomas

"Hilary Cotter" wrote:
Does this help?

http://support.microsoft.com/default.aspx/kb/916002

--
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

"ThoHot00" <ThoHo...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E2A022F6-C84D-43CF-936C-C4648ECA142E@xxxxxxxxxxxxxxxx
Hello,

I have the following scenario. An application using SQL Server Standard
Edition 2000 SP3 on the server side and clients using MSDE 2000A (SP3a)
on
the client machine. Since the client is offline quite often merge
replication
is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and
distributor
upgrade (on the same box) worked fine and all clients could still
synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems
start
:-(

1) After the upgrade the entry within the Synchronization Manager is gone
(we can overcome this by using sp_MSregistersubscription or by manually
disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine. But if I
try
to reinitialize the clients I get the following error:

Error messages:
The merge process could not clean up the subscription to
'tstvmw23':'Product:'Product'. (Source: MSSQL_REPL, Error number:
MSSQL_REPL-2147200965)
Get help:http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid
transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help:http://help/3989

Remark the test system I use is a nearly empty db (only with full schema
and
a few lookup tables) with 15MB. The same error occures if I drop the
subscription before the upgrade and recreate it afterwards. The only way
to
get rid of this error is to drop the database and then recreate the
subscription.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz



.

Relevant Pages

  • Re: File Object Lock with WDK
    ... if the threads were to use different file handles then they can do I/O simultaneously even without FILE_FLAG_OVERLAPPED. ... would want to protect driver wide resources but allow parallel reads and ... If your application wants to have parallel reads and writes on the same file handle, it needs to specify FILE_FLAG_OVERLAPPED. ... > Currently the synchronization scope is Queue level, ...
    (microsoft.public.development.device.drivers)
  • Re: Getting the Groups a User belongs to ( in a service)
    ... > TokenGroups property led me in the right direction. ... > token of the client user. ... If you specify a username and password, ... This is by far the fastest way to get all of the relevant SIDs. ...
    (microsoft.public.dotnet.security)
  • Re: Auto Sync Client Time with Server
    ... Should work automaticly if the client is well integrated in the AD-Structure ... Windows 2000 Time Services ... 2000 for the 'loose time synchronization' required by Kerberos. ... requests time synchronization with the domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Secifying RPC ip address of client
    ... >> the client side in terms of an RPC call? ... Server side", I don't agree that this is the same situation. ... If it has to specify remote addresses, ... it is important to have control over the source address being ...
    (microsoft.public.win32.programmer.networks)
  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... the end-user that runs the client will need to run the application ... Framework installed on the client machine, but not any SQL Server). ... 20 tables in different relations with eachother in the database, ... > just use it as the back end - then do the synchronization there. ...
    (microsoft.public.dotnet.framework.adonet)