Running transactional and snapshot replication on a SQL 2005 Enterprise SP2
cluster
Tried using both the SQL agent service account and a proxy account created
for the replication role. Both produce the following error in SQL Agent:

I was wondering if anyone else had a similar issue.  We reboot our SQL
Server 2008 weekly on Sundays.  But on Mondays I have to start the
replication manually.
It seem after a system reboot the replication does not auto start.

I've set my transactional replication and it works fine. Now I want to
generate some scripts to replicate my job over some servers, I've chosen the
option of generating a script (right click on my pubblication). I've noticed
that the generated scripts lacks of all password ...

We have a merge repilcation push subscription setup. Publisher and
subscriber are running on SQL 2005. But the publication compatibility level
is 2000. I need to upgrade it to 2005 in order to replicate DDL changes.
Please advice.

I have installed SQL Server 2008 Standard onto Windows Server 2008. I am
trying to configure web synchronization and have just read in
http://msdn.microsoft.com/en-us/library/ms151255.aspx that " IIS version 5.0
and IIS version 6.0 are supported. IIS version 7.0 is not supported ...

Is it safe to delete commands from distributiondb.MSrepl_commands ? I
know there is an error in the command and I don't want it to go to
subscriber

I just ran into an odd error, and I'm trying to figure out what
happened.
I replicate a table "rules", from ServerA to ServerB.  Normal
transactional replication.  The table itself has a constraint:

Using SQL Server 2008
Situation:
DB 'Server1' with merge replication (done with wizard) - @pub_identity_range
= 10000 and @identity_range = 1000

Recently, my AD username was changed.  Where ever I add a
subscription, SQL grabs my OLD username.  Being this username is no
longer valid in AD, the distribution agent never starts.
Where is SQL pulling the OLD username from??  How can I resolve this??

I created a merge replication publication on Computer A and added Computer B
as subscriber.
When i was trying to create a new Publication on the same database on
Computer B i got this error on several tables:

I have recently setup publication over wan. The tokens doesnot seems to be
getting through. Does any body have faced this issue.
Thanks in advance
Siddu

Can I restore a database that is currently a subscriber to a
publisher?  Meaning, that if my publisher goes down, I would like to
restore the last full backup on top of the subscriber's database, thus
making it have the same data (close the same) that the publisher has/

Hi Experts,
I am new in this area and no nothing abt replication so.. i need your advise
pls. we need to setup replication between 2 server.  Our requirement is
1.       Any database changes that happens in server 1 databases must be

I'm talking about a transactional replication, let's say that I've this
table that I want to replicate over the subscribers:
[GenericTable]
ID            INT        IDENTITY(1,1) PRIMARY KEY

I have several publications (transactional replication). For some of the
publications I have observed that the snapshot
folder(repldata\unc\pubfolder\folder_with_datetime_stamp) are still having
the snapshot(folder_with_datetime_stamp). And for some of the publications