September 17, 2014 at 9:08 am
I've been using replication for a long while now but have never come across this error. It's a basic transactional replication from ServerA to ServerB, where ServerA is also the distributor. Everything had been running fine on it until yesterday, when this error started popping up and no further transactions could be delivered.
After some quick googling I was able to determine that the distribution agent account needed write access to C:\Program Files\Microsoft SQL Server\100\Com. Hmmm...ok, but why? According to the MSFT article it's because the distribution agent is running under a non-default profile. I didn't change this. However, what I did change around the time that these errors started occurring was the server's Replication Max Test Size setting. It would be far too coincidental for this to not be the cause, but what I don't understand is *why* that would have changed it. Can anyone educate me, please?
Finally, how do I change this? It is definitely not preferable to create temp files in this directory in our environment.
November 6, 2015 at 6:47 am
Actually this error is happening just what you say for. When LOB data is increased it began to use this directory for temp files. But I can not find a solution to change this directory. To gain performans I create and divide lots of file systems but using server's default directory and using standard disks for temp files will remove the other file optimizations and I think it will reduce the performance.
Did you find a solution to change this directory?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply