Transactional Replication error

Hi,
I have configured Transactional Replication, I have Encountered some error the data is not sync the error is
'Agent is retrying after an error. 361 retries attempted. See agent job history in the Jobs folder for more details.'
when i see in the job history it shows'The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job step history message or Replication Monitor for more information.'
How to fix it

Check the previous job step history message or enable verbose agent logging to get additional details.
You can add the parameters -OutputVerboseLevel 2 -Output C:\TEMP\distributionagent.log to the Distribution Agent job step and rerun the Distribution Agent to enable verbose agent logging and collect the log.
This is covered in
How to enable replication agents for logging to output files in SQL Server
Brandon Williams (blog |
linkedin)

Similar Messages

Transactional replication errored out as subscriber is corrupt

Hello,
I received errors this am that my subscriber db is corrupt. I am using SQL 2008 R2 SE. I have stopped replication and restoring subscriber from last nights backup. After the restore is done will I be able to set up replication? The data missing will only
be few hours.
Thanks

I concurr with Ashwin - if you do find that the subscription has expired, you may want to recreate the subscription as a no-sync subscription, run a validation to determine which tables are our of sync and then drop them from the subscription and add them
back again using sp_dropsubscription 'PublicationName',TableName, SubscriberName, SubscriberDBname
then add them back in a new publication/subscription.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Invalid rowid error while running the snapshot agent in transactional replication

Hi All,
I am getting an Invalid rowid error while replicating an large tables i.e around 30 millions rows from oracle(publisher) to sql server(Subscriber) while running the snapshot agent in transactional replication.
Its taking around 18 hours and its then its throwing this error.
Is there any faster way that i can replicate the initial snapshot this large table as 18 hours is very high on time.
Kindly suggest.i am always got quick and accurate response always..hope the same in this case also.
Thanks,

Hi,
Could you please create a replication with some small tables for a test?
You can disable the firewall on both sides and rerun snapshot. Enable verbose logging to level 4 for snapshot agent and check the results if it fails.
http://support.microsoft.com/kb/312292
Here is a document says for the error: ORA-10632: Invalid rowid Cause: Segment Highwatermark was overwritten due to shrink and space reused Action: Reissue this command.
I also suggest you contact the Oracle support team for further help.
Thanks.
Tracy Cai
TechNet Community Support

Error while setting up Transactional Replication

Hi Team,
I am getting below error while configuring Transactional Replication.
Specifically, when I started configuring the distributor that when I am getting below error. I am getting this in GUI as well TSQL script as well.
SQL Server could not configure 'TEST-PC\SQL2K8' as a Distributor.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Destination path D:\SQL2K8DATA is not valid. Unable to list directory contents. Specify a valid destination path.
Changed database context to 'master'. (Microsoft SQL Server, Error: 14430)
Background of the error.
========================
I installed 3 sql instances of "SQL Server 2008 Developer edition, SP3 (x64)".
I started configuring a remote distributor using one of the instance and error started popping up.
Initially I had the replication running fine and I removed it and tried to reconfigure distributor thats when the error starting popping up.
The folder physically exists and the service account has full permissions and I have logged in as service account and trying to setup Transactional Replication.
He is local administrator on the box and also sysadmin login at sql server level.
Not sure why this error is popping up.....
After wasting a lot of time. I tried to install 3 new fresh instances with same service pack level i.e. sp3, but still the error remains the same.
Appreciate if anyone can guide me resolving this issue.
Thank you.

Hi Brandon,
I generated the script and tried again. No Luck. It is throwing error at creation of distribution database itself i.e. exec sp_adddistributiondb .
/****** Scripting replication configuration. Script Date: 2/25/2014 11:43:31 AM ******/
/****** Please Note: For security reasons, all password parameters were scripted with either NULL or an empty string. ******/
/****** Installing the server as a Distributor. Script Date: 2/25/2014 11:43:31 AM ******/
use master
go
exec sp_adddistributor
@distributor = N'TEST-PC\S2',
@password = N'123'
GO
exec sp_adddistributiondb
@database = N'distribution',
@data_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data',
@log_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data',
@log_file_size = 2,
@min_distretention = 0,
@max_distretention = 72,
@history_retention = 48,
@security_mode = 1
GO
Error Message :
Msg 14430, Level 16, State 1, Procedure sp_adddistributiondb, Line 227
Destination path C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data is not valid. Unable to list directory contents. Specify a valid destination path.
use [distribution]
if (not exists (select * from sysobjects where name = 'UIProperties' and type = 'U '))
   create table UIProperties(id int)
if (exists (select * from ::fn_listextendedproperty('SnapshotFolder', 'user', 'dbo', 'table', 'UIProperties', null, null)))
   EXEC sp_updateextendedproperty N'SnapshotFolder', N'\\TEST-PC\repldata', 'user', dbo, 'table', 'UIProperties'
else
   EXEC sp_addextendedproperty N'SnapshotFolder', N'\\TEST-PC\repldata', 'user', dbo, 'table', 'UIProperties'
GO
exec sp_adddistpublisher @publisher = N'TEST-pc\s1',
@distribution_db = N'distribution',
@security_mode = 1,
@working_directory = N'\\TEST-PC\repldata',
@trusted = N'false',
@thirdparty_flag = 0,
@publisher_type = N'MSSQLSERVER'
GO

Snapshot Error When Adding Article to Transactional Replication

I am trying to add an table articles to my transactional replication setup.   When I do, the snapshot error fails with the following message:
Source: Microsoft.SqlServer.Smo
Target Site: Microsoft.SqlServer.Management.Smo.SqlSmoObject GetSmoObject(Microsoft.SqlServer.Management.Sdk.Sfc.Urn)
Message: Attempt to retrieve data for object failed for Server '<servername>'.
Stack:    at Microsoft.SqlServer.Management.Smo.Server.GetSmoObject(Urn urn)
   at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.BuildSmoObjectArrayAndUrnLookupTable(IDictionary& dictUrnKeyArticleScriptingBundles)
   at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting()
   at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting()
   at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
   at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
   at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: Microsoft.SqlServer.Smo, Error number: 0)
Get help: http://help/0
Source: Microsoft.SqlServer.Smo
Target Site: Microsoft.SqlServer.Management.Smo.ObjectKeyBase CreateKeyFromUrn(Microsoft.SqlServer.Management.Sdk.Sfc.Urn)
Message: The input Urn must specify Name at level UserDefinedFunction.
Stack:    at Microsoft.SqlServer.Management.Smo.SchemaCollectionBase.CreateKeyFromUrn(Urn urn)
   at Microsoft.SqlServer.Management.Smo.Server.GetSmoObjectRec(Urn urn)
   at Microsoft.SqlServer.Management.Smo.Server.GetSmoObject(Urn urn) (Source: Microsoft.SqlServer.Smo, Error number: 0)
Get help: http://help/0
Specifics:
Transactional replication: Both Immediate Sync and Allow Anonymous are set to 0.
Publisher and Distributer are same server: SQL Server Standard 2008 R2 (10.50.4000.0) on Windows 2008 R2 SP1
If I add even one table article (doesn't matter, I've tried different ones), I get the error above when I run the snapshot agent.
If I remove the table just added and rerun the snapshot agent, it succeeds with the message "A snapshot was not generated because no subscriptions needed initialization", so at least I don't have to reinitialize (thank goodness!).
Any ideas as to what might be causing this, and how I can add articles to my existing publication?
Thanks in advance for your help.

Hi John V.Barone,
I’m writing to follow up with you on this post. Was the problem resolved after performing our action plan steps? If not, according to your error message, we need to verify if it is caused by replicating Meta Data corruption. You can check if there is a bad
row
in “sysarticles” (for a table) or “sysschemaarticles” (for a UDF) for which we do not have a corresponding “ObjectId” in sysobjects . If yes, delete
manually this row
from Published (sysarticles, sysschemaarticles, syssubscriptions) and Distribution DB (MSsubscriptions,sysschemaarticles,MSarticles).
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Running transactional replication on SQL server 2008R2 but: "The process could not connect to subscriber 'SERVER NAME'"

I've set up Replication (transactional replication) between two remote servers. On the one of server that I configure Distribution & publication .another server is subscription. The subscription is all set & snapshot agent is started .but the actual
replication doesn't take place.
When viewing the Synchronization Status of the subscription, i get an error, saying "The process could not connect to Subscriber ‘Server name'."
Clicking on start, this is the error message I get:
The agent could not be started.
Additional information:
An exception while executing a Transact-SQL statement or batch.
SQL Server Agent Error: Request to run job Server1-EDUSRV-Pubs-Server2-14 (from User Server1\Administrator) refused because the job is already running from a request by User sa.
Change database context to 'EDUSRV'.(Microsoft SQL Server Error:22022)
What can i do?
Please help me.Thanks

The error The process could not connect to Subscriber 'Server name' indicates that the Distribution Agent process account does not have enough permissions to connect to the Subscriber.
If this is a push subscription, verify the Distribution Agent process account is db_owner in the distribution and subscription databases, is a member of the PAL, and has read permissions on the snapshot share.
If this is a pull subscription, verify the Distribution Agent process account is db_owner in the subscription database, is a member of the PAL, and has read permissions on the snapshot share.
The permissions required are covered in
Replication Agent Security Model.
If you have anymore questions, please let me know. I hope this helps.
Brandon Williams (blog |
linkedin)

Transactional Replication Stalled.

Hi,
We are having a Transactional replication issue where the Data does not get replicated and the log Just keeps grawing.
Last week we had an accidental load 15 Million records, on one of the T replication enabled Db's .Then the replication stopped working i mean i look at the replication monitor it says NO transactions to replicate but we have a lot difference
with the DATA.I also see that the logfile file for the DB is growing.
1.I did a few things like stopping the log reader and restarting.
2.Reinitialize the Snapshot ,the snapshot is taken but is not being applied to the subscriber .No error msg that i can see.
So had to drop the replication entirely , shrink the log and recreate it adding few bunches of articles, creating a snapshot for them wait until they are applied and then add the other articles which worked fine for few days , and DB replication
stopped again and log started growing.This time it is also effecting other replications this time too.
I am running out of options can some one plz help!
THanks,
Jack

That message means the log reader agent is going through the log reading commands from it. If your ETL operation does large batch operations replication many not be able to keep up. You might need to break these batches up into smaller batches - batchsize
works well here.
Another thing to consider is to do your ETL operation on both sides. This works well if the only source of changes occurs from the ETL process - then you would not publish these tables.
If not - think about use MaxCmdsInTran - you can set this to something like 10,000 which means that if you do a million row update - the log reader agent will start to read the commands out of the log for every 10,000 changes and replicate them to the subscriber
- before the transaction is committed on the publisher.
This is a command that you can put in your log reader agent profile so you can turn it off when the ETL process is done and replicated.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Transactional replication with 1 publisher 2 subscribers in SQL 2012 SE

I have a setup of transaction replication between one publisher and subscriber in the Same server.Now, I need to add a new subscriber to the existing publisher. So publisher database name is DB_A and Subscriber 1 name is DB_B. So the new subscriber will
be DB_C.
Is this kind of setup possible on one server?
If yes then at the time of reinitialization is it going to apply the snapshot on DB_B as well as DB_C?
Also let say if due to disk error DB_B gets corrupted then will data be still replicated between DB_A and DB_C? (Assuming publisher, subscriber 1 and 2 are sitting on individual disks)
Need your valuable thoughts experts.
Thanks a ton.

For that you have to setup replication with backups. Assuming you had a failure and the only option now is to reinitialize, then instead you basically drop the subscription, change the publication property to
allow_initialize_from_backup to true. Now you can follow the article below to create the subscription. Instead of using the backup from publisher you can use the old backup of subscriber. In this case, you need to confirm that
all the data that is in the publisher (which needs to be replicated) is already there in subscriber.
http://msdn.microsoft.com/en-us/library/ms147834.aspx
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Transactional replication is a problem

i have got transactional replication going on.
when i check the status on publisher database , publisher to distrubutor history shows perfefcely fine but distributor to subscriber is waiting since forever
and when i check the status on subscription/distributor side this is what i get
k

i disconnect from ssms and connect again using the server name instead of IP so the error message is gone,
but distributor to subscriber is still waiting for looooooooooooong time.
k

Unable to drop publication database from publisher server in transactional replication

Dear All,
we are getting one issue when the time of dropping publication database on publisher server in transactional replication in sql server 2008 r2.
TITLE: Microsoft SQL Server Management Studio
Could not delete publication 'dbname_Pubs'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1&EvtSrc=Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Replication.ReplicationMenuItem&EvtID=CantDeletePublication&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Could not find stored procedure ''. (Microsoft SQL Server, Error: 2812)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.4000&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476
BUTTONS:
OK
mastanvali shaik

try this..
exec sp_removedbreplication N'<dbname>'
exec sp_droppublication @publication = N'<dbname>'
Raju Rasagounder Sr MSSQL DBA

Transaction replication failing at creation of Publication

Hi Gurus, I am facing very uncommon issue when setting up transactional replication. My instance is running on MSSQL 2005 SP3 and same instance act as Distributor and Publisher.
Step1: Created Distributor with no issues.
Step2: Enable Pblisher - Same instance and a database under this instance runnning in full recovery mode.
Step3: Create Publication - Went thru all the steps and selected couple tables(articles) to create initial snapshot. After provide a name to the publication, click ok - its throwing following error for both articles:
TITLE: New Publication Wizard
SQL Server Management Studio could not create article 'abc_Table'.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The article 'abc_table ' does not exist. Changed database context to '<publisher_DB> '. (Microsoft SQL Server, Error: 20027)
Both tables have primary key and available in publisher database. I did setup n number Transactional replications and did not see this kind of error so far. Did not see any help when googled/Binged, Any help is highly appreciated. Thanks in advance for your
help.
Thanks, TTeam

Hi Mohammad, Please see the table structure it is under dbo schema.
CREATE
TABLE [dbo].[busmgt](
[id] [int]
NOT
NULL,
[persid] [nvarchar]
(30)
NULL,
[hier_parent] [binary]
(16)
NULL,
[hier_child] [binary]
(16)
NOT
NULL,
[last_mod_dt] [int]
NULL,
[last_mod_by] [binary]
(16)
NULL,
[cost] [int]
NULL,
[sym] [nvarchar]
(60)
NOT
NULL,
[nx_desc] [nvarchar]
(40)
NULL,
[bm_rep] [int]
NULL,
[ci_rel_type] [int]
NULL,
[tenant] [binary]
(16)
NULL,
[del] [int]
NOT
NULL
DEFAULT
('0'),
CONSTRAINT [PK__busmgt__187915EB]
PRIMARY
KEY
NONCLUSTERED
[id]
ASC
WITH
(PAD_INDEX
=
OFF,
STATISTICS_NORECOMPUTE
=
OFF,
IGNORE_DUP_KEY
=
OFF,
ALLOW_ROW_LOCKS
=
ON,
ALLOW_PAGE_LOCKS
=
ON)
ON [PRIMARY]
ON [PRIMARY]
Thanks, TTeam

Replication - Error with real data type

Hi Everybody,
I have a replication problem on a certain SQL Server 2012 build 2100. First of all:
- Tables are the same on Publisher and Subscriber (double-checked)
The problem is 8152 - String or binary would be truncated. Since I know this error, I looked for the command (xact_seqno) and it shows:
{CALL [sp_MSins_tbl2Replicate]
({7B914E3E-25ED-E411-BC82-005056A54F21}
,{BA54EA41-ECE1-4F4B-7A63-08D05A57DCC9}
,{51BEC1B8-F6D2-E411-BC82-005056A54F21}
,1
,NULL
,N'2015-04-27'
,{87766F58-A0C8-41E6-E7D4-08CFE45FE017}
,2
,2.81122997072606E-313
,N'2015-04-27 23:34:59.7600274'
,{87766F58-A0C8-41E6-E7D4-08CFE45FE017}
,NULL
,{0AB7C33E-0B3E-E211-A06F-005056A54F21},NULL,NULL,0,NULL,NULL)}
My problem is the value "2.81122997072606E-313" since this field is a real field. I dont understand that. The Value is way to small and a SELECT in the Publisher-DB shows a "1". Does anybody has an idea?
Thanks
Dave

Hi,
first of all thanks for your help. Publisher-Table-Schema:
[EV_GUID] [uniqueidentifier] ROWGUIDCOL NOT NULL,
   [EV_PV_Profilvariable] [uniqueidentifier] NOT NULL,
   [EV_Empfaenger] [uniqueidentifier] NOT NULL,
   [EV_EmpfaengerTyp] [tinyint] NOT NULL,
   [EV_Gruppe] [uniqueidentifier] NULL,
   [EV_ErbrachtDatum] [date] NOT NULL,
   [EV_AN_Erbringer] [uniqueidentifier] NOT NULL,
   [EV_Zeitwert] [int] NOT NULL,
   [EV_Anteil] [real] NOT NULL,
   [EV_ErfasstZeitpunkt] [datetime2](7) NOT NULL,
   [EV_AN_Erfasser] [uniqueidentifier] NULL,
   [EV_SC_Statistikcode] [uniqueidentifier] NULL,
   [EV_OE_Auftraggeber] [uniqueidentifier] NOT NULL,
   [EV_KST_Kostenstelle] [uniqueidentifier] NULL,
   [EV_Bemerkung] [varchar](max) SPARSE NULL,
   [EV_Flags] [int] NOT NULL,
   [EV_MN_Massnahme] [smallint] NULL,
   [EV_Fremdkey] [varchar](100) NULL
Subscriber-Table-Schema:
just the same....
SELECT EV_Anteil FROM tbl2Replicate WHERE EV_GUID = '7B914E3E-25ED-E411-BC82-005056A54F21'
returns "1". The reported value wont fit in a real-field or am I missing something? I tested this and it would fill in a "0" for such a tiny number. Therefore it cant be in the publisher database. Also tested with SELECT MIN(EV_Anteil)
and returned "0.02040816" with another PK of course.
Other Options in Transactional Replication:
Replicate schema changes - True
Copy objects all to false, except clustered index, unique key constraints, Collation and INSERT, UPDATE, DELETE stored procedures
Convert data types = False
Thanks
Dave

Customer Master replication error from R/3 to CRM

Experts,
I am trying to replicate Customer Master from R/3 to CRM.
All the settings have been done. Nothing shows up in Queues. However, Bdoc hangs in "Received" state.
When I try to reprocess the Bdoc, I get a prog dump of type DBIF_RSQL_INTERNAL_ERROR in below function module: CRM_BUPA_FRG0020_SAVE_TABS
at INSERT crmm_but_set0020 FROM TABLE it_set0020_insert[]
This data corresponds to Shipping data in Customer Master.
Can you please help? I saw a similar thread in the forum where there was a suggestion about R/3 plug in update. How can I do that?
Thanks in advance,
JD

Pls see Customer Master replication error
Closed.

Transactional replication from a failover cluster instance to a SQL Server Express DB

Hello,
I have been poking around on Google trying to understand if there are any gotchas in configuring transactional replication on a instance DB of a failover cluster, to a SQL Server Express DB. Also, this client would like to replicate a set of tables between
two instances DB's which both reside on nodes of the cluster.
Everything I've read suggests there is no problem using transactional replication on clustered instance as long as you use a shared snapshot folder. I still have some concerns:
1) Should the distributor need to live on a separate instance?
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber.
There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Thanks in advance.

1) Should the distributor need to live on a separate instance?
Answer: It is recommended to configure the distributor on the different server, but it also be configured on Publisher/subscriber server. (Subscriber in our case is not possible as its a Express edition)
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber. There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Answer: If you configure both publisher and distributor on the same server and the SQL instance is failed over, the data synchronization/replication is suspended till the instance comes online.
Once the instance is up,all the replication jobs will start again and it will continue to synchronize the data to subscriber. No manual intervention is required.

Replication error BP from CRM to R/3 - "Fill in all required entry Fields"

Dear Folks
I have maintained all steps mentioned in building block - C03. I have maintained separate account group approach. Made sure that number ranges are in sync in both the systems. Particularly in PIDE, mapping classification Consumer-Org 'A' to 'ZZ01' (Copy of 0001).
      I changed all required entry to optional entry in my 'ZZ01' field status using OVT0.
       But when i replicate using R3AS, i get an error 'Fill in all required entry Fields" - Error in receiving system (i.e R/3).
       I tried manually creating customer in R/3 with the account group ZZ01. Surprisingly it does not allows me to save unless i give the reconcillation account entry, even though it is not a required field.
   Please let me know for further details and Please help me to resolve this error. I am in real urgency.
Thanks
Keerthi
Chicago IL
507 401 1030

Hi Karunakaran
        Your reply answered my question of creating customer with no 'recon' a/c required entry. Thanks awarded 2 points.
          My replication error is still hanging around. I found that It has no bearing on the 'Reconcillation A/c' required entry.
          Some other field is still restricting my BP Role- Consumer:Organization to replicate. The error still showing as "required fields are not entered in R/3", even after suppressing "Reconcillation Account".
       I think my reference customer master i created in R/3 using VD07 is not assigned in case of the account group Consumer:Organization.
   But i don't know how to verify my doubts and get rid of this error.
Please help, in great urgency.

Transactional Replication error

Similar Messages

Maybe you are looking for