Error 14053 and Push Replication

SQL Server Enterprise Manager encountered errors creating push subscriptions
for the following Subscribers:
[Subscriber Server Name]: Error 14053: Cannot load the DLL replincrementlsn
extended procedure, or one of the DLLs it references. Reason: 126(error not
found).
The subscription could not be updated at this time.
The subscription could not be created.
The publisher and distributor are running SQL Server 2000 SP3a, the
subscriber is RTM (no SP applied expect for the criticial release update).
The subscriber has a new server just released into production, hence why no
SP yet.
The publisher and subscriber are on non trusting domains, but on the
internal network.
I have checked the SP log file (C:\Windows\) and have been advised that both
sp_replincrementlsn and sp_replincrementlsn_internal exist in the master
table on both servers. I also reattempted to install SP3a on the publisher
server to no avail.
All work has been carried out in Ent Mgr.
I thank anyone in advance for their assistance, as I am totally lost for
ideas.
Betty,
can you run this on the distributor, just to confirm that the stored
procedure was created correctly:
sp_helptext sp_replincrementlsn
Please check that xprepl.dll is in your sql bin directory (eg C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
Please check the sql server error log for any issues recorded there.
Have a look at sqlsp.log file from the c:\windows directory this might shed
some light on any failed actions during the sp installation
If any of this returns something interesting then please post it up,
otherwise I'd reinstall sp3a.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I ran the steps you requested on our distribution server (which is also the
publication server)
- sp_helptext sp_replincrementlsn returned no issue, the sp does exist, but
only in the master table.
- xprepl.dll DOES exist in the BINN directory of the SQL Server
- The SQL Server reports no error, and even reports that it is using
xprepl.dll for replication
- SQLsp.log appears to contain no critical errors (the only error of sort is
the one that indicates that some data files could not be modified - the
reason being that those databases are in the offline state.
- I am still yet to reinstall SP3a, awaiting for authorisation from the
server controller, but previous attempts have not worked.
Anyother ideas?
Thanks,
Betty.
"Paul Ibison" wrote:

> Betty,
> can you run this on the distributor, just to confirm that the stored
> procedure was created correctly:
> sp_helptext sp_replincrementlsn
> Please check that xprepl.dll is in your sql bin directory (eg C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> Please check the sql server error log for any issues recorded there.
> Have a look at sqlsp.log file from the c:\windows directory this might shed
> some light on any failed actions during the sp installation
> If any of this returns something interesting then please post it up,
> otherwise I'd reinstall sp3a.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||With this type of installation error, I'd apply the
service pack, reinstall completely and ring PSS in this
order assuming the error is repeated at each step.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
one interesting thing is that the SP3Readme.htm states that this error can
be safely ignored.
Regards,
Betty.
"Paul Ibison" wrote:

> With this type of installation error, I'd apply the
> service pack, reinstall completely and ring PSS in this
> order assuming the error is repeated at each step.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
after applying SP3 it appears that the replication works, it states, that it
said the replication was created successfully.
I think what happens, is if you attempt to create your first publication,
distributor, or subscriber, after SP3 has been applied, you need to reapply
SP3 to update the replication system files.
Thank you for your assitance,
Betty.

Error "merge process could not initialize publisher XXX"

Hello All-
We have a SQL Server 2000 Merge publication with about 10 push clients
running MSDE.
There are 2 subscribers that appear to be failing when connecting to the
publisher. The publisher & distributor are on the same host. If we look
at the Replication Monitor, the 'duration' column for these 2 clients have
a very small "Duration" value, usually under 1 minute. Other clients on
the same network are up for hours or days.
We have the agent schedule to start when SQL Server starts & also to start
every 1 minute. So, it appears these 2 subscribers are continuously failing
on connect.
In order to get more info, I changed the command line parameters ( in edit
job steps) to output details. The details are at the bottom of this message.
The details say another merge agent for this replication subscriber is
already running. I'm not sure what action to take on this error.
Any ideas?
Thanks,
bruce

[5/6/2004 8:25:56 AM]BASKINGRIDGE.CDB: set nocount on declare @.dbname
sysname select @.dbname = db_name() declare @.collation nvarchar(255) select
@.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Percent Complete: 1
Connecting to Publisher 'BASKINGRIDGE'
The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
Percent Complete: 0
The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147198719
Message: The merge process could not initialize the Publisher
'BASKINGRIDGE:CDB'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call master..sp_MScheck_agent_instance
(N'BASKINGRIDGE-CDB-CDB-BABYLON-24', 4)}
Percent Complete: 0
Category:SQLSERVER
Source: BASKINGRIDGE
Number: 21036
Message: Another merge agent for the subscription(s) is running.
Disconnecting from Publisher 'BASKINGRIDGE'
Disconnecting from Distributor 'BASKINGRIDGE'
start task manager and verify that you have one merge.exe process in taskman
for each merge agent currently running on your system. If not, try to
selectively kill the rougue merge agent, and then start the new one.
"rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
news:dTqmc.59231$Nn4.13413268@.twister.nyc.rr.com.. .
> Hello All-
> We have a SQL Server 2000 Merge publication with about 10 push clients
> running MSDE.
> There are 2 subscribers that appear to be failing when connecting to the
> publisher. The publisher & distributor are on the same host. If we look
> at the Replication Monitor, the 'duration' column for these 2 clients
have
> a very small "Duration" value, usually under 1 minute. Other clients on
> the same network are up for hours or days.
> We have the agent schedule to start when SQL Server starts & also to start
> every 1 minute. So, it appears these 2 subscribers are continuously
failing
> on connect.
> In order to get more info, I changed the command line parameters ( in edit
> job steps) to output details. The details are at the bottom of this
message.
> The details say another merge agent for this replication subscriber is
> already running. I'm not sure what action to take on this error.
> Any ideas?
> Thanks,
> bruce
>
> ----
> [5/6/2004 8:25:56 AM]BASKINGRIDGE.CDB: set nocount on declare @.dbname
> sysname select @.dbname = db_name() declare @.collation nvarchar(255) select
> @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
> N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
> 'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
> collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
> Percent Complete: 1
> Connecting to Publisher 'BASKINGRIDGE'
> The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
> Percent Complete: 0
> The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147198719
> Message: The merge process could not initialize the Publisher
> 'BASKINGRIDGE:CDB'.
> Percent Complete: 0
> Category:COMMAND
> Source: Failed Command
> Number: 0
> Message: {call master..sp_MScheck_agent_instance
> (N'BASKINGRIDGE-CDB-CDB-BABYLON-24', 4)}
> Percent Complete: 0
> Category:SQLSERVER
> Source: BASKINGRIDGE
> Number: 21036
> Message: Another merge agent for the subscription(s) is running.
> Disconnecting from Publisher 'BASKINGRIDGE'
> Disconnecting from Distributor 'BASKINGRIDGE'
>
>

Erro 14040: The server "ServerB" is already a Subscriber

Hello.
I'm trying to create a Push subscription from ServerA to ServerB and am
getting the above message. I am using Enterprise Manager to do this.
ServerB already subscribes to a publication from ServerC.
I noticed that the error occurs on the first step of the "Completing the
Push Subscription Wizard", the one labelled "Enabling this server as a
subscriber" (for ServerB). Makes sense since ServerB would have already been
enabled because of the existing subscription to the publication on ServerC.
Is there a way to tell EM not to enable ServerB for subscriptions, or can
ServerB only subscribe to only one other server?
I'm running SQL 2000 SP3a.
Thanks in advance,
Mike
can you do this query and post the results back here?
select sub, srvname from sysservers where srvname='serverb'
Also check to see if ServerB is an enabled Subscriber. If so, uncheck/check
the check box and see if you get an error message.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mike" <MichaelLopez@.inds.com> wrote in message
news:%233Tf5GbaEHA.2408@.tk2msftngp13.phx.gbl...
> Hello.
> I'm trying to create a Push subscription from ServerA to ServerB and am
> getting the above message. I am using Enterprise Manager to do this.
> ServerB already subscribes to a publication from ServerC.
> I noticed that the error occurs on the first step of the "Completing the
> Push Subscription Wizard", the one labelled "Enabling this server as a
> subscriber" (for ServerB). Makes sense since ServerB would have already
been
> enabled because of the existing subscription to the publication on
ServerC.
> Is there a way to tell EM not to enable ServerB for subscriptions, or can
> ServerB only subscribe to only one other server?
> I'm running SQL 2000 SP3a.
> Thanks in advance,
> Mike
>