As it is always when it comes to replication, the circular problems and suposedly resolved in previous versions rear their head again and again. The title issue was supposedly resolved in SQL server 2005 and 2008. Yet it is again an issue in
2012, there was some indication that it was resolved in SP2, SQL 2012. Yet, it continues to be an issue even after applying the update. The even bigger problem is that the error is so generic that there is not even a place to start troubleshooting. Leave it to Microsoft!!! Maybe a support call will give me an answer. In the mean time, is there anybody out there that can give me a hint on where to start trouble shooting this issue?
↧