Puzzled by Config files

I created a package, created an XML Config file, created a deployment utility and then deployed to server. I scheduled it with agent and I get this error (changed the package name in the error to IMPORT to make it more readable):

Description: The configuration file name "C:\Documents and Settings\chris\My Documents\Visual Studio 2005\Projects\IMPORT\IMPORT\IMPORT.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2006-07-12 13:11:39.96 Code: 0x80012059 Source: IMPORT Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Progress: 2006-07-12 13:11:40.56 Source: Import Data Validating: 0% complete End Progress Progress: 2006-07-12 13:11:40.56 Source:... Process Exit Code 1. The step failed.

So basically its trying to point to a config file on my dev workstation. When I created the deploy utility it created a config file in the Deployment directory with the Manifest and the package. I installed from the deployment directory. When installing it asked where I wanted to install and I left it the default of "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\IMPORT" and if I look in that folder the IMPORT.dtsconfig is there.

Ideas of where I went wrong? I want to make sure I understand the whole configuration file notion correctly as I am starting to roll a bunch of packages with config files out to production. I've done the tutorial and thought it was straightforward and made sense. I can fix it by editing the xml of the package and removing the line pointing to my dev box - just want to know what I am doing wrong :)

Nevermind... Found lots of other people with similar issues in diff threads on this forum. This whole config file thing is pretty confusing. When you do the install from the deployment folder it will show all the values from the config file in the deployment directory - but it doesn't use any of them when you actually run the package.

I am really not sure why they put the dtsconfig file in the deployment folder at all - all that does is confuse things. I had been placing the production config file over the one in the deployment folder and assumed it would use it... not so.

Push and Pull subscription?

As I understand replication in Sql2K the only difference in push or pull subscriptions is where the agent runs. If I wanted changes in the publisher to be sent to the subscribers immediately after the change then I thought push would be better. But, if I am equally interested in changes made at the subscriber then what should I use? Or does the agent monitor both the publisher and subscriber at the same time?

Thanks for your help

Graham

Graham, assuming you're talking about merge replication, changes will be propagated up/down whenever the agent runs. If you run the agent in continuous mode, then the changes should be sent within the polling period of the agent. If you run the agent in a scheduled mode, or on demand, then the changes will be sent when the agent runs.

Push Agent limits at Central Distributor

How many Distributor Agents (Distrib.exe files) SQL Server 2000 work better?
There is any limits?
Message posted via http://www.droptable.com
I'm not aware of any limits. For me, the issue is one of ordering of
transactions and isolation of publications. IE if you use a shared agent,
the transaction order is maintained which is not the case with independant
agents. The flipside is that an error which stops the shared agent will stop
it delivering transactions for all its publications until it is fixed.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I've scaled it beyond 200, but that was with a pull, not a push. You get
better scalability with a pull. When you start approaching high numbers you
need to tweak this key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SQL2000\SQLServerAgent\Subsystems\Distribut ion and set the value
C:\Program Files\Microsoft SQL
Server\MSSQL$SQL2000\BINN\SQLREPSS.DLL,C:\Program Files\Microsoft SQL
Server\80\COM\DISTRIB.EXE,ReplStart,ReplEvent,Repl Stop,100
where you Modify 100 to be the number of simultaneous distribution agents
you expect.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Krisnamourt via droptable.com" <u21487@.uwe> wrote in message
news:66e155dcf7428@.uwe...
> How many Distributor Agents (Distrib.exe files) SQL Server 2000 work
> better?
> There is any limits?
> --
> Message posted via http://www.droptable.com
>

Purpose of SQL Server Agent Service

Can someone explain the purpose of the SQL Server Agent Service?
"Ivan Svaljek" <ivan.svaljek@.gmail.com> wrote in message
news:bc7d369f.0503071452.24917756@.posting.google.c om...
> Can someone explain the purpose of the SQL Server Agent Service?
It lets you schedule jobs.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
|||Not only that, you can also set alerts for certain conditions on the server
and notify operators when a job completes or aborts.
-Argenis
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uA5C6n2IFHA.904@.tk2msftngp13.phx.gbl...
> "Ivan Svaljek" <ivan.svaljek@.gmail.com> wrote in message
> news:bc7d369f.0503071452.24917756@.posting.google.c om...
> It lets you schedule jobs.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>

Purpose of SQL Server Agent Service

Can someone explain the purpose of the SQL Server Agent Service?"Ivan Svaljek" <ivan.svaljek@.gmail.com> wrote in message
news:bc7d369f.0503071452.24917756@.posting.google.com...
> Can someone explain the purpose of the SQL Server Agent Service?
It lets you schedule jobs.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--|||Not only that, you can also set alerts for certain conditions on the server
and notify operators when a job completes or aborts.
-Argenis
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uA5C6n2IFHA.904@.tk2msftngp13.phx.gbl...
> "Ivan Svaljek" <ivan.svaljek@.gmail.com> wrote in message
> news:bc7d369f.0503071452.24917756@.posting.google.com...
> It lets you schedule jobs.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>

Purpose of SQL Server Agent Service

Can someone explain the purpose of the SQL Server Agent Service?"Ivan Svaljek" <ivan.svaljek@.gmail.com> wrote in message
news:bc7d369f.0503071452.24917756@.posting.google.com...
> Can someone explain the purpose of the SQL Server Agent Service?
It lets you schedule jobs.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--|||Not only that, you can also set alerts for certain conditions on the server
and notify operators when a job completes or aborts.
-Argenis
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uA5C6n2IFHA.904@.tk2msftngp13.phx.gbl...
> "Ivan Svaljek" <ivan.svaljek@.gmail.com> wrote in message
> news:bc7d369f.0503071452.24917756@.posting.google.com...
> > Can someone explain the purpose of the SQL Server Agent Service?
> It lets you schedule jobs.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.sqljunkies.com/weblog/amachanic
> --
>

Pull:shared agent

I had a problem and lost, with no backups, a couple of data bases.
When I was recreating the subscriptions, a subscription just appeared
the name is 'ServerName:database' & the type is 'Pull:shared
agent'. I cannot delete the publication, I get the message 'SQL
Server Enterprise Manager could not retrieve information about
subscription ServerName:database' Start, Stop & job History are all
grayed out on the right click.
Now the questions...
What is a Pullshared agent?
How can I delete this?
What is in this subscription?
TIA,
Larry...
If you are not using the independent agent option and you have two
subscriptions to the same publication database, the two subscriptions will
share a single distribution agent.
You should be able to delete it by using exec sp_dropmergepullsubscription
or sp_droppullsubscription. Fill in the details by referencing the
MSsubscription_properties table in your subscription database.
This subscription is really very similar to any other subscription only
there are two of them
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
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1130782861.818300.175690@.z14g2000cwz.googlegr oups.com...
> I had a problem and lost, with no backups, a couple of data bases.
> When I was recreating the subscriptions, a subscription just appeared
> the name is 'ServerName:database' & the type is 'Pull:shared
> agent'. I cannot delete the publication, I get the message 'SQL
> Server Enterprise Manager could not retrieve information about
> subscription ServerName:database' Start, Stop & job History are all
> grayed out on the right click.
> Now the questions...
> What is a Pullshared agent?
> How can I delete this?
> What is in this subscription?
>
> TIA,
> Larry...
>
|||Where is this decided independent agent or shared agent? I have
created many many agents and never recall seeing this..

pull subscription, subscriber configuration

Hi,
I was trying a pull subscription and I got all kinds of error messages
all suggesting that the merge agent isn't being run or it isn't
accessible. But, the moment I did a push subscription, it ran and
replication happened without an error message. I don't understand why.
My subscriber is an ordinary windows 2000 OS and is not of a server
configuration. Could that be a reason, since, in a pull subscription,
the agent is supposed to run on the subscriber(which isn't a server)?
Any suggestions or thoughts are welcome!
Also, is there a way a subscriber can tell the publisher to push a
subscription?
Thanks,
PS.
By definition a pull subscriber "pulls" the subscription on its own schedule - it doesn't tell the publisher push now.
Its hard to figure out exactly what the error is from your description. Please provide the complete error messages you are getting.
In general when you have pull subscription problems.
1) check that the SQL Server agent account has rights to read the snapshot share and the underlying path on the publisher, likely to be \\publisherName\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc
2) check on your publisher that you have enabled your subscriber to impersonate the Server agent account on the Publisher. Go to Tools, point to replication, click configure publishers, subscribers, and distributors, click on the browse button to the righ
t of your subscriber and select the impersonate option.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ps" wrote:

> Hi,
> I was trying a pull subscription and I got all kinds of error messages
> all suggesting that the merge agent isn't being run or it isn't
> accessible. But, the moment I did a push subscription, it ran and
> replication happened without an error message. I don't understand why.
> My subscriber is an ordinary windows 2000 OS and is not of a server
> configuration. Could that be a reason, since, in a pull subscription,
> the agent is supposed to run on the subscriber(which isn't a server)?
> Any suggestions or thoughts are welcome!
> Also, is there a way a subscriber can tell the publisher to push a
> subscription?
> Thanks,
> PS.
>

Pull Subscription in SQL Express?

This may be a dumb question. Can SQL server express do pull subscription? I
find out Sql server express doesn't come with SQL server agent, does pull
subscription need the server agent to do the pull job?
Thanks for any help.
KL
Yes, use task scheduler to pull it, probably using some activeX.
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
"KL" <KwanLoonLai@.msn.com> wrote in message
news:30B7CE45-2A5F-4B62-80A5-ED300F8E4850@.microsoft.com...
> This may be a dumb question. Can SQL server express do pull subscription?
> I find out Sql server express doesn't come with SQL server agent, does
> pull subscription need the server agent to do the pull job?
> Thanks for any help.
> KL

Pull Replication with Filter

Hello,
we are working with:
SQL Server 2000 SP 4, publicating a database and trying to filter data
with:
UserGroup = Host_Name()
on the subscriber (agent properties) we set:
-Hostname TW
Starting the subscription with the SyncManager works fine, but no data
with the criteria 'TW' was replicated to the subscriber.
This problem occurs all the time i try to work with the pull
replication. The same procedure on a push replication seems to be OK.
Also two of our customers have the problems and this begins to be a
very big problem for us. Somebody knows an solution. For me it seems to
be an MS SQL Bug?
Thanks for help
Tulio Mossorous
Are you using dynamic snapshots?
You have to do this to make it work or create a separate publication for
each subscriber.
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
"Tulio" <mossorous@.yahoo.de> wrote in message
news:1123439126.086812.143350@.z14g2000cwz.googlegr oups.com...
> Hello,
> we are working with:
> SQL Server 2000 SP 4, publicating a database and trying to filter data
> with:
> UserGroup = Host_Name()
> on the subscriber (agent properties) we set:
> -Hostname TW
> Starting the subscription with the SyncManager works fine, but no data
> with the criteria 'TW' was replicated to the subscriber.
> This problem occurs all the time i try to work with the pull
> replication. The same procedure on a push replication seems to be OK.
> Also two of our customers have the problems and this begins to be a
> very big problem for us. Somebody knows an solution. For me it seems to
> be an MS SQL Bug?
> Thanks for help
> Tulio Mossorous
>
|||Hello Hilary,
thanks for your help!
Yes, I'am using dynamic snapshot.
Regards
Tulio Mossorous
|||Hello again,
in a lot of posts users have problems with the dynamic filtering of a
pull replication. I tried the dynamic filtering for about 2 days,
without any result!
The dynamic snapshot don't get any data. What happens? An Bug?
Best regards
Tulio Mossorous
|||Hello again,
in a lot of posts users have problems with the dynamic filtering of a
pull replication. I tried the dynamic filtering for about 2 days,
without any result!
The dynamic snapshot don't get any data. What happens? A Bug?
Best regards
Tulio Mossorous

Pull replication

I cannot get a pull merge replication to work.
The distributor is Win2000 running SQL 2000.
Subscribers are XP Pro running MSDE.
Agent command:
-Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
[SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
-SubscriberLogin [sa] -SubscriberEncryptedPassword
[??????] -Distributor [DistSVR]
The errors:
Category:AGENT
Source: SubSVR
Number: 20084
Message: The process could not connect to Subscriber 'SubSVR'.
Category:SQLSERVER
Source: SubSVR
Number: 17
Message: SQL Server does not exist or access denied.
Thank you ver much.
This means your subscriber can't connect.
Log on to your subscriber machine and try to ping your publisher.
Also verify you can ping your subscriber using the host name SubSVR from
your subscriber. Also verify that your subscriber password is correct.
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:C60CE48B-18A5-4C03-A034-5FF59E876951@.microsoft.com...
> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode
0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>
|||Thank you for your reply.
Subscriber PC name and SQL server name are different. It's the reason ?
Excuse me for the question: SubscriberLogin is the login to Subscriber or
Distributer ?
Thank you.
"Thang Long" wrote:

> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>

Pull Agent: Process Could Not Connect To Subscriber

OK, with a tip from ChrisR I got the first problem fixed (I hope). Now, I have
another problem. I have created a pull subscription on a second server, say
SERVERB, to get the data from the first server, say SERVERA. Every time I try to
run this pull subscription I get the following message:
The process could not connect to Subscriber 'NEWSERVERB'.
Then it fails every time. Funny thing to me is that then name of the subscriber
in this message is my subscriber server with 'NEW' on the front. Questions:
Where does that name come from? Why is it trying to connect to my subscriber?
What the heck is going on?
Thanks!
Hi Darrell,
It looks like '-Subscriber NEWSERVERB' might have been accidentally added to
the command line for starting the replication agent. You can find out the
replication agent command line by doing a select from msdb..sysjobsteps.
Merge agent job steps will have a subsystem value of 'REPL-MERGE' whereas
distribution agent job steps will have a subsystem value of
'REPL-DISTRIBUTION'.
-Raymond
"Darrell" wrote:

> OK, with a tip from ChrisR I got the first problem fixed (I hope). Now, I have
> another problem. I have created a pull subscription on a second server, say
> SERVERB, to get the data from the first server, say SERVERA. Every time I try to
> run this pull subscription I get the following message:
> The process could not connect to Subscriber 'NEWSERVERB'.
> Then it fails every time. Funny thing to me is that then name of the subscriber
> in this message is my subscriber server with 'NEW' on the front. Questions:
> Where does that name come from? Why is it trying to connect to my subscriber?
> What the heck is going on?
> Thanks!
>
|||Dude, thanks! I thought I had changed that in the steps of all jobs. I must have
missed one or more of the steps. Thanks again.
Raymond Mak [MSFT] wrote:[vbcol=seagreen]
> Hi Darrell,
> It looks like '-Subscriber NEWSERVERB' might have been accidentally added to
> the command line for starting the replication agent. You can find out the
> replication agent command line by doing a select from msdb..sysjobsteps.
> Merge agent job steps will have a subsystem value of 'REPL-MERGE' whereas
> distribution agent job steps will have a subsystem value of
> 'REPL-DISTRIBUTION'.
> -Raymond
> "Darrell" wrote:
>

Publishing problem ...

Hello,
I have a problem when trying to publish articles for merge
replication. During execution of the snapshot agent I
receive the following error "The process could not bulk
copy out of table '[dbo].[table_name]'. Can anyone help
me with this problem?
Any help at all would be greatly appreciated!
Thanks in advance
Jim S.
Basically it means the snapshot agent locked up, timed out, was blocked, or
somehow deadlocked. What you do is stop and restart the snapshot agent. If
you are dealing with a large table, you may need to manually transfer it to
the subscriber. There are cases where the size of the table becomes nearly
impossible to get a snapshot to complete.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Do I:
1. Just let the snapshot agent run until it fails
during the bcp process
2. Transfer all tables to the subscriber via dts
3. Create subscription using the 'do not create schema
and data option'

>--Original Message--
>Basically it means the snapshot agent locked up, timed
out, was blocked, or
>somehow deadlocked. What you do is stop and restart the
snapshot agent. If
>you are dealing with a large table, you may need to
manually transfer it to
>the subscriber. There are cases where the size of the
table becomes nearly
>impossible to get a snapshot to complete.
>--
>Mike
>Principal Mentor
>Solid Quality Learning
>"More than just Training"
>SQL Server MVP
>http://www.solidqualitylearning.com
>http://www.mssqlserver.com
>
>.
>
|||If it continues to fail, what I normally do is to separate out the table
that are failing into a separate publication. The ones separated out I use
the "do not create..." option and use DTS to manually transfer everything
over. It's ugly and full of trial and error, but it works. There aren't
any other good options at this point, because a snapshot has to complete in
order for transactions to start flowing. The interesting thing you will
find is that DTS will generally transfer the data in about 1/10 the amount
of time that the snapshot takes.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Publication w/o logreader agent. Is it possible?

Hi,
Is it possible to create a publication without creating a logreader agent at
the same time? I'm on MS SQL Server 2000 SP3a.
-- Many thanks, Oskar
Oskar - if you are talking about transactional replication, this is an
integral part of the functioning. I'm interested in why would you like to
avoid the logreader agent?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Yes, transactional is what I am talking about. I am interested in this
because I want to have development databases published but I do not want to
have any real replication going on there. This is needed because we must have
identical "change management" in development and production environments.
Looks like I have partly solved this problem by making each development
server a publisher and a distributor, and regenerating the publication from a
script. I even could do without the snapshot agent, but getting rid of the
logreader seems to be tricky, if not impossible.
-- Thanks, Oskar
"Paul Ibison" wrote:

> Oskar - if you are talking about transactional replication, this is an
> integral part of the functioning. I'm interested in why would you like to
> avoid the logreader agent?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Oskar,
don't know if this helps, but until the snapshot has run, the log reader
isn't moving any commands to the distribution database. To prevent it
parsing the transaction log you could simply stop it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||That's exactly what I did. I just don't like to stop it manually everytime
the development database gets refreshed - its job name and id changes at
every such refreshing.
-- Oskar
"Paul Ibison" wrote:

> Oskar,
> don't know if this helps, but until the snapshot has run, the log reader
> isn't moving any commands to the distribution database. To prevent it
> parsing the transaction log you could simply stop it.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||I'd add a piece of code at the end of the script which stops and disables
the job - that way you don't need to worry about it afterwards.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Publication not enabled to use an independent agent

I've created a snapshot replication between 2 databases on 2 different
servers to run once a day. The snapshot has worked but when the
distribution job runs it fails within a few seconds. I've looked at the
job history and the following error message is recorded:
Publication 'EmailDB' is not enabled to use an independent agent. The
step failed.
I think this may be because I've defined the publication so that
anonymous pull subscriptions are not allowed. If not does anyone know
what the problem could be. If it is how do I alter the publication so
that they are allowed - the option doesn't appear to be changeable with
the publication properties window in EM.
TIA
Laurence Breeze
drop your subscriptions and try this
sp_changepublication 'pubs4','independent_agent','true'
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
"Laurence Breeze" <laurence_breeze@.yahoo.co.uk> wrote in message
news:4289AD77.5070305@.yahoo.co.uk...
> I've created a snapshot replication between 2 databases on 2 different
> servers to run once a day. The snapshot has worked but when the
> distribution job runs it fails within a few seconds. I've looked at the
> job history and the following error message is recorded:
> Publication 'EmailDB' is not enabled to use an independent agent. The
> step failed.
> I think this may be because I've defined the publication so that
> anonymous pull subscriptions are not allowed. If not does anyone know
> what the problem could be. If it is how do I alter the publication so
> that they are allowed - the option doesn't appear to be changeable with
> the publication properties window in EM.
> TIA
> Laurence Breeze
>

Publication does not exist.

I have an error that states....
DESCRIPTION:Replication-Replication Merge Subsystem: agent R99S-SQLA-
EDI-EDI Merge to 00-r00s-sqla-2 failed. Publication 'EDI Merge to 00'
does not exist.
Due to the fact that there are other consultants setting up/deleteing
replication & do not know how this happened...nonetheless I need to
delete this replication. The publication is not in the tree list in
Local Publications, so I have no way of getting rid of it from there.
I have done some research & I am suppose to look in the
MSmerge_publications table in the distribution dB, but I do not have a
distribution dB.
Any one have a clue about this one?
Larry...
Looks like someone has created a publication from script that has spaces in
the name. You have to delete this publication, and then recreate it
correctly.
You will probably have to edit the system tables to do this.
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
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1185813236.584431.209930@.19g2000hsx.googlegro ups.com...
>I have an error that states....
> DESCRIPTION: Replication-Replication Merge Subsystem: agent R99S-SQLA-
> EDI-EDI Merge to 00-r00s-sqla-2 failed. Publication 'EDI Merge to 00'
> does not exist.
> Due to the fact that there are other consultants setting up/deleteing
> replication & do not know how this happened...nonetheless I need to
> delete this replication. The publication is not in the tree list in
> Local Publications, so I have no way of getting rid of it from there.
>
> I have done some research & I am suppose to look in the
> MSmerge_publications table in the distribution dB, but I do not have a
> distribution dB.
> Any one have a clue about this one?
> Larry...
>