SQL Server Publish subscription error collection

Source: Internet
Author: User
Tags mssqlserver naming convention

Catalogue

1. SQL Server Publishing subscription error collection

1.1. Message: Script for table "dbo. " Table "failed.

1.1.1. Error Messages

1.1.2. Handling Methods

1.2. because of operating system error 3, the process cannot read the file d:\\xxxx\\x.pre ( source : Mssql_repl, error number : mssql_repl20024)

1.2.1. Error Messages

1.2.2. Workaround

1.3. the row was not found at the subscriber when the copied command was applied

1.3.1. error Messages

1.3.2. Workaround

1.4. the transaction log for database ' dbtest ' is full

1.4.1. error Messages

1.4.2. Workaround

2. The process was unable to table "" dbo "." a table name " "for bulk copy.

2.1.1. Error Messages

2.1.2. Workaround

1. SQL Server Publish subscription error collection 1.1. Message: script for table "dbo. " Table "failed. 1.1.1. error Message

Source:Microsoft.SqlServer.Smo

Target Site:System.Collections.Generic.IEnumerable ' 1[system.string] scriptwithlist ( Microsoft.SqlServer.Management.Smo.DependencyCollection, microsoft.sqlserver.management.smo.sqlsmoobject[])

Message: The script failed for table "dbo.hy_corp_bad_credit_info".

Stack: in Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList (dependencycollection deplist, Sqlsmoobject[] objects)

in Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList (sqlsmoobject[] objects)

in Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateLogBasedArticleSchScript ( Scripter Scripter, Basearticlewrapper articlewrapper, Table smotable)

in Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateLogBasedArticleScripts ( Articlescriptingbundle articlescriptingbundle)

in Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateArticleScripts ( Articlescriptingbundle articlescriptingbundle)

in Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.GenerateObjectScripts ( Articlescriptingbundle articlescriptingbundle)

in Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting ()

in Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting ()

in Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot ()

in Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun ()

in Microsoft.SqlServer.Replication.AgentCore.Run () ( source : Microsoft.SqlServer.Smo, error number : 0)

Get help : http://help/0

Source:Microsoft.SqlServer.Smo

Target site:void Checksupportedtype (Microsoft.SqlServer.Management.Smo.ScriptingOptions)

Message: the column fhappendate in object hy_corp_bad_credit_info contains the type Date, This type is not supported by the target server version of SQL Server 2005 .

Stack: in Microsoft.SqlServer.Management.Smo.Column.CheckSupportedType (scriptingoptions options)

in Microsoft.SqlServer.Management.Smo.Column.VersionValidate (scriptingoptions so)

at Microsoft.SqlServer.Management.Smo.Column.ScriptDdlCreateImpl (StringBuilder sb, scriptingoptions so)

in Microsoft.SqlServer.Management.Smo.Column.ScriptDdl (StringCollection queries, scriptingoptions so)

at Microsoft.SqlServer.Management.Smo.Table.ScriptTableInternal (scriptingoptions So, StringBuilder SB, columncollection columns, indexcollection indexes)

at Microsoft.SqlServer.Management.Smo.Table.GetTableCreationScript (scriptingoptions So, StringBuilder SB)

in Microsoft.SqlServer.Management.Smo.Table.ScriptCreate (StringCollection queries, scriptingoptions so)

in Microsoft.SqlServer.Management.Smo.SqlSmoObject.ScriptCreateInternal (stringcollection query, Scriptingoptions so)

in Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithListWorker (Dependencycollection deplist, Sqlsmoobject[] objects)

in Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList (dependencycollection deplist, sqlsmoobject[ ] objects) ( source : Microsoft.SqlServer.Smo, error number : 0)

Get help : http://help/0

1.1.2. Processing Methods

set the database compatibility level to $ , execute the following code on the publication database, and modify the compatibility level of the database to .

ALTER database [Database] SET compatibility_level = 100

or interface operation:

1.2. The process could not read the file d:\\xxxx\\x.pre ( source : Mssql_repl, error number ) due to operating system error 3 : mssql_repl20024) 1.2.1. error Message

the command to try :

E:\DB_backup_xmq\unc\WINDOWS-Q6MJ0R8_REMAIUS_REMAIUS\20161224144353\hy_wait_work_r45f6f27c_249.pre

( transaction serial number : 0x0000fa7e0001c1d4005000000000, command id:252)

error message :

the process could not read the file because of operating system error 3 "E:\DB_backup_xmq\unc\WINDOWS-Q6MJ0R8_REMAIUS_REMAIUS\20161224144353 \hy_wait_work_r45f6f27c_249.pre". ( source : Mssql_repl, error number : mssql_repl20051)

Get help : http://help/MSSQL_REPL20051

The system could not find the path specified.

( source : Mssql_repl, error number : MSSQL_REPL3)

Get help : http://help/MSSQL_REPL3

1.2.2. Workaround

qlServer2008 's subscription was published, the initial use of the push subscription was smooth, and later changed to a pull subscription This problem occurs .

1.3. The row was not found at the subscriber when the copied command was applied1.3.1. error Message

the command to try :

If @ @trancount > 0 Rollback Tran

Transaction serial number :

--0x0000fdab0003a908008f00000000 command id:7

error message :

The row was not found at the subscriber when the copied command was applied. ( source : MSSQLServer, error number : 20598)

Get help : http://help/20598

The row was not found at the subscriber when the copied command was applied. ( source : MSSQLServer, error number : 20598)

Get help : http://help/20598

1.3.2. Workaround

1. the publisher server

exec sp_helpsubscriptionerrors ' windows-q6mj0r8 '

, ' Remaius '

, ' Remaius '

, ' Win-v0r4coildas '

, ' Remaius ';

2. Resolve

A. ignore, execute on subscription

exec sp_setsubscriptionxactseqno ' windows-q6mj0r8 '

, ' Remaius '

, ' Remaius '

, 0x0000fdab0003a908008f00000000;

B. as the first SQLto find xact_seqno, get xact_seqno,command_ ID

Then on the release,

Sp_browsereplcmds ' 0x0000fbf300119d32000900000000 ', ' 0x0000fbf300119d32000900000000 ';

Sp_browsereplcmds ' 0x0000fdab0003a908008f00000000 ', ' 0x0000fdab0003a908008f00000000 ';

Find {call [dbo]. [Sp_msupd_dbotable1] (, ' DD ', 4,0x04)} "The default naming convention is Sp_ms+operation+schemaname+tablename "

then at the Subscriber, the data of the primary key =4 is replenished , and then the copy is resumed.

"Note":the ID will need to be marked for auto-growth when it is added:

--set identity_insert table_1 on-- Open

--insert into table_1 (ID) values (134);

--set identity_insert table_1 off-- Close

1.4. The transaction log for database ' dbtest ' is full1.4.1. error Message

the command to try :

If ColumnProperty (object_id (' MSreplication_subscriptions '), ' distribution_agent ', ' Allowsnull ') <> 1 BEGIN ALTER TABLE msreplication_subscriptions ALTER column distribution_agent sysname NULL end

error message :

Database the transaction log for ' dbtest is full. To find out why the space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases. ( source : MSSQLServer, error number : 9002)

Get help : http://help/9002

1.4.2. Workaround

-- Empty log

--Truncate The log by changing the database recovery model to simple.

ALTER DATABASE Remaius SET RECOVERY simple;

--Shrink The truncated log file to 1 MB.

DBCC Shrinkfile (Remaius_new_log, 1);

--Reset the database recovery model.

ALTER DATABASE Remaius SET RECOVERY full;

2. The process could not "" dbo " to the table." a table name " "for bulk copy. 2.0.1. error Message

process failed to table“" dbo". "a table name""for bulk copy. (Source: Mssql_repl, the error number: mssql_repl20037)
Get help: http://help/MSSQL_REPL20037
Batch Send failed
fromBcpThe client receives a column value pair columnID Notoginsenginvalid. (Source: MSSQLServer, the error number: 4896)
Get help: http://help/4896
For a detailed description of the error file that was encountered when initializing the subscription table, perform theBcpcommand. About thebcpFor more information about the utility and its supported options, seeBOL. (Source: MSSQLServer, the error number: 20253)
Get help: http://help/20253
BCP "a publication name"." dbo "."a table name"in" H:sqlmssql10_50.uzai2008mssqlrepldatauncsqlcluster$sql2008_a library name_a publication name20120711171029a table name_2.bcp "-E" errorfile "-T" n<x$3>n "-R" N<,@g>n "-m10000-sSubscription Name subscription instance name-t-w (Source: MSSQLServer, the error number: 20253)
Get help: http://help/20253

2.0.2. Workaround

because This table has a long list of special characters such as the special HTML tag class /<&%|^ , and the release of this column is successful . or adjust all non- Unicode (varchar/char/text) type fields to Unicode (Nvarchar/nchar/ntext) type can "

SQL Server Publish subscription error collection

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.