Error occur in snapshot agent of transactional replication

Copper Contributor

Hi,

Below error occurring while running the snapshot agent in transactional replication. Please help me to resolve this error.

Message

2023-03-17 05:20:35.44 [11%] Pre-loading meta-data of all tables in the publisher database for scripting

2023-03-17 05:20:37.10 [11%] Sorting article objects in the proper creation order

2023-03-17 05:20:37.12 [11%] Customizing object for scripting based on article 'test'

2023-03-17 05:20:37.18 [11%] Resolving duplicate object names among replicated objects

2023-03-17 05:20:37.20 [11%] Analyzing foreign key references among article objects in the publication

2023-03-17 05:20:37.20 [11%] Analyzing external references of all replicated check and default constraints

2023-03-17 05:20:37.20 [11%] Analyzing dependencies on non-article objects

2023-03-17 05:20:37.21 [11%] Generating schema scripts for article 'test'

2023-03-17 05:20:37.69 [62%] Processing system pre-snapshot script

2023-03-17 05:20:37.70 [62%] Posting snapshot commands into the distribution database

2023-03-17 05:20:37.71 [62%] Inserted schema command for article 'test' into the distribution database

2023-03-17 05:20:37.72 [62%] Inserted index creation command for article 'test' into the distribution database.

2023-03-17 05:20:37.72 [62%] Inserted bcp command for article 'test' into the distribution database.

2023-03-17 05:20:37.72 [62%] Inserted stored proc to disable constraint/triggers article 'test' during concurrent snapshot into the distribution database.

2023-03-17 05:20:37.74 [62%] Locking published tables while generating the snapshot

2023-03-17 05:20:38.13 [62%] The replication agent had encountered an exception.

2023-03-17 05:20:38.13 Source: Replication

2023-03-17 05:20:38.13 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException

2023-03-17 05:20:38.13 Exception Message: A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_scriptdropinsreconciliationproc_sqlclr":

2023-03-17 05:20:38.13 System.Data.SqlClient.SqlException: The locale identifier (LCID) 19465 is not supported by SQL Server.

2023-03-17 05:20:38.13 System.Data.SqlClient.SqlException:

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Server.SmiEventSink_Default.DispatchMessages(Boolean ignoreNonFatalMessages)

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Server.SqlDataRecord..ctor(SqlMetaData[] metaData)

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Replication.SqlPipeTextWriter..ctor()

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ScriptDropReconciliationProcedure(SqlInt32 articleId, CustomStoredProcedureType customProcedureType)

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.sp_scriptdropinsreconciliationproc_sqlclr(SqlInt32 articleId, SqlInt32 mode, SqlByte publisherType, SqlInt32 format)

2023-03-17 05:20:38.13 .

2023-03-17 05:20:38.13 A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_scriptdropdelreconciliationproc_sqlclr":

2023-03-17 05:20:38.13 System.Data.SqlClient.SqlException: The locale identifier (LCID) 19465 is not supported by SQL Server.

2023-03-17 05:20:38.13 System.Data.SqlClient.SqlException:

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Server.SmiEventSink_Default.DispatchMessages(Boolean ignoreNonFatalMessages)

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Server.SqlDataRecord..ctor(SqlMetaData[] metaData)

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Replication.SqlPipeTextWriter..ctor()

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ScriptDropReconciliationProcedure(SqlInt32 articleId, CustomStoredProcedureType customProcedureType)

2023-03-17 05:20:38.13 at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.sp_scriptdropdelreconciliationproc_sqlclr(SqlInt32 articleId, SqlInt32 mode, SqlByte publisherType, SqlInt32 format)

2023-03-17 05:20:38.13 .

2023-03-17 05:20:38.13 Message Code: 6522

2023-03-17 05:20:38.13

Thanks

0 Replies