Merge Replication Problem
-
Hi, I have configured 2 SQL Server 2005 instances to replicate using Merge Replication. This is just a test environment at the moment, therefore both instances are on different servers but within the same domain and both running under the same administrator accounts. The replication seems to run smoothly in that the snapshot agent runs successfully and then the subscriber synchronises with no errors. But, when I run my app on the subscriber I get a error when trying to perform a particular task:
Invalid object name 'dbo.MSmerge_genvw_5A046C944AD94C85AA554B95189A5399'.
The said task is calling a stored procedure which I have defined and which I can see has been replicated to the subscriber. I am new to replication so not entirely sure what is going on. Any help would be greatly appreciated. Also, it may be worth pointing out that the subscriber is an express version, therefore all agents are running on the publisher. Thanks.
-
Hi, I have configured 2 SQL Server 2005 instances to replicate using Merge Replication. This is just a test environment at the moment, therefore both instances are on different servers but within the same domain and both running under the same administrator accounts. The replication seems to run smoothly in that the snapshot agent runs successfully and then the subscriber synchronises with no errors. But, when I run my app on the subscriber I get a error when trying to perform a particular task:
Invalid object name 'dbo.MSmerge_genvw_5A046C944AD94C85AA554B95189A5399'.
The said task is calling a stored procedure which I have defined and which I can see has been replicated to the subscriber. I am new to replication so not entirely sure what is going on. Any help would be greatly appreciated. Also, it may be worth pointing out that the subscriber is an express version, therefore all agents are running on the publisher. Thanks.
Just in case anyone is interested, I solved the problem by replacing the SQL Express Server with the full version. All seems to be working correctly now.