question

@Deepika Have you tried multiple catch blocks (one for each possible exception type) or, most importantly, interrogating the InnerException and viewing the StackTrace? All types of exceptions inherit from Exception, but sometimes it makes sense to trap them separately, i.e. to wheel out a separate catch blocks for [ReplicationAgentException][1], [ReplicationAgentContainerException][2], [OSException][3] etc. [1]: https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.replication.replicationagentexception.aspx [2]: https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.replication.replicationagentcontainerexception.aspx [3]: https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.replication.osexception.aspx

@Oleg Thanks for quick response. We are getting ComErrorException when the subscription is expired for trans/merge subscription.In this case,the inner exception is nothing and the stack trace contains the below details Microsoft.SqlServer.Replication.TransSynchronizationAgent.Initialize() at Microsoft.SqlServer.Replication.TransSynchronizationAgent.Synchronize() at Sysco.SAM.BusinessLayer.CSubscription.AsyncTransPullSubscriptions() As suggested, i have included ComErrorException as separate exception but the exception details seems to be generic as that of Exception. Do we have possible SQL replication error codes and error messages?

@Oleg Can you provide the possible replication error messages/error code so that we can handle those in our application. For ex:Subscription is getting failed because of the subscription expiration/retention period.

@Deepika If you are getting the ComErrorException then you can try reading the value of the [ComHResult][1] property which this specific type of exception exposes. Also, the [ErrorMessage][2] property might be a bit more helpful than the Message of the Exception. Please let me know if this works. [1]: https://technet.microsoft.com/en-us/library/ms147562(v=sql.110).aspx [2]: https://technet.microsoft.com/en-us/library/ms147589(v=sql.110).aspx

@Oleg ComHResult and ExceptionMessage property has the value "-2147467259" and "unspecified error" respectively and this seems to be generic SQL error. Do we have the standard replication error code and error messages in order to handle this scenario.