I´m getting the error in merge replication:

The remote server is not defined as a subscription server.
(Source: (Data source); Error number: 14010)

The replication jobs are running from serveral months ago

Thanks for any help

I have the need to replicate the transactions from 4 independent servers.
Each server logs transactions and needs to lookup the transaction history of
each of the other 3 servers. I have two servers each in 2 data centers.
The reason for having 4 servers is that in the event of a problem we can
lose a server or a data center and the others can continue processing. The
total volume of transactions across all 4 servers is less than 2 thousand
per minute.

I'm thinking of using service broker to replicate the transactions to each
of the other 3 servers. I can live with a 5 second latency and expect it to
be much less. I feel a simple SB application would do the replication and
gives me more flexibility in terms of recovery when things go wrong. The
alternative is a 4 way merge replication of a table. My biggest concern
with replication is recovery when things go wrong, and controlling the error
handling during maintenance reboots of individual servers.

I've got a merge replication set up with the publisher running SQL Server
2005 Standard SP2 and the subscribers running SQL Server 2005 Express SP2.
Around 10 of the subscribers are working fine, but one is getting these
errors when running the synchronization (copied from the Replication Monitor
on the publisher):

----------------------------------------
Error messages:

The Merge Agent failed to apply replication metadata. When troubleshooting,
increase the -OutputVerboseLevel setting and restart the agent, or check for
and resolve other errors generated by the database engine. (Source:
MSSQL_REPL, Error number: MSSQL_REPL-2147200968)
Get help: http://help/MSSQL_REPL-2147200968

Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done. (Source: MSSQLServer, Error number: 0)
Get help: http://help/0

The process was successfully stopped. (Source: MSSQL_REPL, Error number:
MSSQL_REPL-2147200997)
Get help: http://help/MSSQL_REPL-2147200997
--------------------

Hi All
i just installed sql server 64 bit sp2, with a hotfix.
When i right click on 'local publications', nothing is going on. ssms freeze
for 15 sec and nothing.
Any clue?

I had a merge replication subscriber where I had to recreate a push
subscription but it wouldn't create, saying the subscription already
existed. I ran sp_dropmergesubscription on the publisher and then ran
sp_helpmergesubscription and verified there was no record for that
subscriber in the output. I recreated the subscription and now
(although it is synchronizing), replication monitor shows duplicate
entries for that subscriber. Running 'select * from
msmerge_subscriptions on the distributor' or sp_helpmergesubscription
only shows 1 entry. Has anyone seen this and know how to fix it?

I need to remove a linked server and I am getting an error code 20854
indicating the publisher cannot drop the server because it is used as a
subscriber. Is there a reference document anyone knows of that can explain
the proper process for removing linked servers. I have tried to do this with
the servers down and with them running and get the same message. We are
doing database replication between two remote cities and want to start from
scratch again and need to delete the database and the links between them.

Error:

Drop failed for LinkedServer 'STLPW01'. (Microsoft.SqlServer.Express.Smo)

Cannot drop server 'STLPW01' because it is used as a Subscriber to remote
Publisher 'CHIPW01' in replication. (Microsoft SQL Server, Error: 20584)

Thank you in advance for nay help you can offer....GB

Here's the scenario....
I have a one-off database script that after completion results in the
production of some large transaction log backups for log shipping on SQL
Server 2005. In order that these backups do not take forever to copy from
primary to secondary, I wondered if it is possible to compress them (I
believe this functionality is provided in SQL Server 2008). Anyone know if
the following is safe to do and will work?

Disable copy and restore jobs
Zip up the large transaction log backup file, rename the .zip file to the
original name
Run the copy job to copy the [zipped] file over to secondary (as it has the
right name - is this sufficient or does the copy job attempt to look inside
the file?)
On the secondary, rename the tran log file to .zip, unzip it
Run the restore job on the unzipped file to restore it to the secondary.

Thanks.

Can someone help?

I had setup transactional replication and it was working great, but I had to
remove it due to some issues with the application/schema. Unfortunately, I
did not use the Wizard to remove the publisher/distributor and now when I try
to reconfigure replication I get this error message: The specified @name
(‘Replication Warning’) Transactional replication latency already exists.
Changed DB context to master error: 14261

Any fix for this without interrupting the prod server?

HELP!

I had setup transactional replication and it was working great, but I had to
remove it due to some issues with the application/schema. Unfortunately, I
did not use the Wizard to remove the publisher/distributor and now when I try
to reconfigure replication it bombs out on me when configuring the
distributor. I get this error message: The specified @name (‘Replication
Warning’) Transactional replication latency already exists. Changed DB
context to master error: 14261

Any fix for this without interrupting the prod server?

I have an application and I need to do an insert into the database but part
of the data is an image stored in the compact database. As long as I'm
inserting text data everyting is fine, however when I add the binary data to
my sql statement it ends up looking like the following:

"INSERT INTO eWorksheetSignatureDump (TechWOID, SignatureImage, Name)
VALUES(843264, System.Byte[], 'John Smith')"

Is there any way to keep the binary data from getting converted to
"System.Byte[ ]" as this seems to be where the error occurs.