This is a common problem we are encountering with one of our workgroups in our multi site environment "Failed to aquire entity ownership from workgroup" or "No site in Workgroup"
This message is shown while trying to transfer file ownership from one site to another. All replication messages on the servers show replication is occurring normally. I can log into each machine. But It isn't possible to tranfers file ownership.
We are running Vault Pro 2012 on 64 bit, with sql 2008 r2. Any suggestions would be appreciated.
Has the ownership expired? Usually a site/workgroup will own a file for a set time. Are you able to log into the troubled site and send ownership to another site/workgroup?
Thanks for the response. Ownership is availible for lease. When logging into the other site and trying to transfer ownership.
But as I was typing this message, I found the problem. the server agent wasn't running on one of the sites. who knows how long. Maybe a couple days.
I meant the SQL server Agent. It is responsible for maintaining the replication of the databases and files, as far as i know.
Sometimes the service is interupted and stops running. You can check it through SQL management studio. SQL server agent should have a little green "play" button, if it is running. In a multi-site replicated environement, you have a SQL server agent running on each server.
hope this helps
Well, you can directly check the services from the server managment tools. You may also setup the server to send email notifications if for some reason the service cannot be started. Otherwise SQL management studio is the only way I know how to check
You can see all the services that are installed on your machine, which ones are running, which ones are set to start automatically, etc; by looking in Control Panel >> Administrative Tools >> Services. Or just run services.msc from a DOS shell or the "Run .." dialog off the start menu.
This happened to me when the Autodesk Data Management Job Dispatch services were not running on the target workgroup (Server that had the ownership) server. Once we started the service (and waited about 2 or 3 minutes) all was well.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!