Ask the Community
Groups
Reapply Schema Error: Table 'DeploymentPermissions' already has a primary key defined on it. - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>PROBLEM</strong></p> <p>When running a reapply schema/reinstall database schema, and encounter the following error:</p> <p dir="auto"><strong>Fatal MessageSys Error: ESET/index/eset.PK_DeploymentPermissions.sql</strong></p> <p dir="auto"><strong>System Error [0] Message: Error <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/agent/tickets/1779" rel="noopener ticket nofollow">#1779</a>: Table 'DeploymentPermissions' already has a primary key defined on it. </strong><br><strong>Could not create constraint. See previous errors. on line 1.</strong></p> <p dir="auto"> <img src="https://us.v-cdn.net/6032361/uploads/migrated/5TF7Y32ZVEG0/2017-12-13-17-51-20.png" alt="2017-12-13_17-51-20.png" class="embedImage-img importedEmbed-img"></img></p> <p><strong>WORKAROUND </strong></p> <ol><li>Access <strong>SQL Management Studio</strong> on your SQL Server.</li> <li>Run the following SQL Command: <ul><li>USE ksubscribers;<br>ALTER TABLE eset.DeploymentPermissions<br>DROP CONSTRAINT PK_DepIDRoleID;</li> </ul></li> </ol><p><strong>Note:</strong> Please reach out to ESET to let them know that you've experienced this issue so that they can track internally on their side.</p> <p>ESET has also included this resolution in their own troubleshooting steps found <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fhelp.eset.com%2Fera%2F6%2Fplugins%2Fkaseya%2Fen-US%2Ftroubleshooting.html">here.</a></p> <p><strong>APPLIES TO</strong></p> <p>Integration with ESET </p> <p> </p> <div> </div> <div> </div> <div> </div> <div> </div> </article> </main>