RE: Replication error, PLEASE HELP

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

I have not checked the database yet but it is not so likely the couse becouse
the same error that occured on the first server now has occured on one server
more.

The process could not query row metadata at the 'Publisher'.
(Source: Merge Replication Provider (Agent); Error number: -2147200996)
---------------------------------------------------------------------------------------------------------------
Communication link failure
(Source: SLRESSQL001 (Data source); Error number: 0)
---------------------------------------------------------------------------------------------------------------
The merge process encountered an unexpected network error. The connection to
Publisher 'SLRESSQL001' is no longer available.
(Source: Merge Process (Agent); Error number: -2147199469)


Any more suggestions. Offcourse I can do a check if you still think that is
a problem. But there in a production enviroment and I don´t want to disturb
to much if not necesary

"Regina" wrote:

OK, thanks. We have SQL Server 2000 installed. Does that make it difficult.

"CG" wrote:

seems like your .mdf file might have been corrupted.
you would need to run database check.
if it shows error the best option would be to restore database although it
depends on what database environment you have.


"Regina" wrote:

Hi
We have a problem with our replication job, it faild at midnigt this night.
The error says.


The description for EventID (208) in Source( SQLSERVERAGENT) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display message from a remote computer. You may be able
to use the /AUXSOURCR = flag to retrive this description ...


In the replication monitor the error says

The merge process could not perform retention-based meta data cleanup in
database 'bilbo'.
(Source: Merge Replication Provider (Agent); Error number: -2147199467)
---------------------------------------------------------------------------------------------------------------
I/O error (torn page) detected during read at offset 0x00000b947ae000 in
file 'G:\MSSQL\Data\UserDB\bilbo_Data.MDF'.
(Source: SLRESSQL001 (Data source); Error number: 823)
---------------------------------------------------------------------------------------------------------------
This error occured a couple of times then following error come and is still
comming
The process could not query row metadata at the 'Publisher'.
(Source: Merge Replication Provider (Agent); Error number: -2147200996)
---------------------------------------------------------------------------------------------------------------
Communication link failure
(Source: SLRESSQL001 (Data source); Error number: 0)
---------------------------------------------------------------------------------------------------------------
The merge process encountered an unexpected network error. The connection to
Publisher 'SLRESSQL001' is no longer available.
(Source: Merge Process (Agent); Error number: -2147199469)
---------------------------------------------------------------------------------------------------------------

PLEASE HELP US
Regina
.

Relevant Pages

  • Re: Inserts so slow using _Connection.Execute
    ... works but sooo slow. ... I connect to the first server / database using _Recordset and ... You might want to take a look at SQL Server's BCP API. ...
    (borland.public.delphi.database.ado)
  • Re: ESE97 184 - 1019 error
    ... first server with better hardware/drives and move the mailboxes back. ... Is it possible to create a new database on the existing drive and then ...
    (microsoft.public.exchange.admin)
  • Re: Portal creation failed.
    ... Unable to find entry for Portal Site in sites hosted by database at ... My production enviroment is a medium server farm: ... are useless and if the database corrupts I will lose my entire portal. ...
    (microsoft.public.sharepoint.portalserver)