I encountered this problem on our SQL2012 and I have tried different scenarios (see below) to no avail. I have decided to give up and check if someone here has encountered this and resolved it.
One thing I know, it's not a memory issue. Both servers we're using has lots of memory to spare and we monitor the memory as the replication goes through it's steps.
I hope someone can help me on this. Thanks!
The Error:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent.
Our Scenario
- We're using SQL Server 2012 SP1. All subscriptions are pull based.
- We're using direct Merge Replication (not FTP or web sync)
- We already have 10 active replications with larger databases. Only 1 has this issue.
- Database size is less than 5 GB
- Rebuilding the publisher is not an option.
What have I tried?
- There is no memory problem --- we have lots to spare
- I have tried re-initialization of the database. Same problem.
- I tried deleting the database and reinitializing it. Same problem
- New snapshot. Same problem.
- I tried changing the subscriber server but still same issue.
MCP, MCSD, MCDBA (ANXA)