Error 14258 while creating a publication

Hi all,
I am trying to create a merge-publication (SQL 2000 SP4).
Unfortunately, it is not working because the wizard pops up with error
14258: Cannot perform this operation while SQL Server Agent is
starting. Try again later.
Checked both services, they seem correct. Both are using (the same)
domain-user with sufficient privs to access the SQLServer box. They
both run fine (all in the green) and there are no errors in the logs.
SQL itself runs fine and I can access all data from any computer in the
network.
Just to be sure, I've stopped and restarted both services but the same
error comes back again. I've checked all settings but as far as I can
see, the box is configured properly.
Any ideas?
Thx,
FS
Check out this MS article:
http://support.microsoft.com/?id=303287
John Steen
"Ferry" wrote:

> Hi all,
> I am trying to create a merge-publication (SQL 2000 SP4).
> Unfortunately, it is not working because the wizard pops up with error
> 14258: Cannot perform this operation while SQL Server Agent is
> starting. Try again later.
> Checked both services, they seem correct. Both are using (the same)
> domain-user with sufficient privs to access the SQLServer box. They
> both run fine (all in the green) and there are no errors in the logs.
> SQL itself runs fine and I can access all data from any computer in the
> network.
> Just to be sure, I've stopped and restarted both services but the same
> error comes back again. I've checked all settings but as far as I can
> see, the box is configured properly.
> Any ideas?
> Thx,
> FS
>
>
|||Hmm, I guess I was too fast... Solved the problem already by googling a
bit further. As a thank you for reading I will share the solution :-)
When having MSDTC switched on _and_ using NT-fibres in the SQL
configuration, you can encounter this error. Switching the NT-fibres
off (and stopping and starting the services again) resolved the
problem. MSKB article, aaaaargh, how could I missed it in the first
place...
From Ferry :
> Hi all,
> I am trying to create a merge-publication (SQL 2000 SP4). Unfortunately, it
> is not working because the wizard pops up with error 14258: Cannot perform
> this operation while SQL Server Agent is starting. Try again later.
>

Error 14058: The subscription already exists

Hi,
I've got the error in the Subject when I tried to delete and recreate
manually a pull subscription to a publication.
How can I delete defenitely the subscription from that database?
Thank you.
get your publication name and issue the following command in your
subscription database:
sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
'publisher_db' ,[ @.publication = 'publication'
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
> Hi,
> I've got the error in the Subject when I tried to delete and recreate
> manually a pull subscription to a publication.
> How can I delete defenitely the subscription from that database?
> Thank you.
|||Hi Hilary,
thanks for your answer, but your code still gives the message that the
subscription doesn't exist... I'm also sure that I've written correctly all
the parameter, namely the publisher name, publisher db and the publication
name.
Do you think that there is another problem?
"Hilary Cotter" wrote:

> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>
|||Hi Hilary,
now I solved the problem: I had to delete the pull subscription manually
from the Publisher database.
I have another question: when I started the syncronitation, I got the
following error:
"The process could not connect to Disctributor 'MYDISTRIBUTOR'. Login failed
for user'
How can I discover which USER NAME failed the login?
"Hilary Cotter" wrote:

> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>

Error 14046: Could not drop article.

Error 14046: Could not drop article. A subscription exists on it.
I get the above error when I try to drop a publication in SQL2k. I do not
show any subscriptions for this publication anywhere. How can I find the
subscription that is blocking me from dropping this publication?
Nevermind, I got it.
In distribution..MSsubscriptions, I found the "rogue" entry, causing this
error. I deleted it, and was then able to successfully delete the
publication.
"JAdams" wrote:

> Error 14046: Could not drop article. A subscription exists on it.
> I get the above error when I try to drop a publication in SQL2k. I do not
> show any subscriptions for this publication anywhere. How can I find the
> subscription that is blocking me from dropping this publication?

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