Ask the Community
Groups
Replication failure ELIMIT: Number of registrations exceed maximum limit - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Replication failure, ELIMIT: Number of registrations exceed maximum limit</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p><b>Problem:</b><br>Replication failures with the following symptoms. When viewing the replication history report you see either of the following messages: </p> <blockquote class="blockquote">Failed: Unable to send blocks. This replication will now retry. Network: no error<br>Failed: Failed building on the target. This replication will now retry. Network: no error</blockquote> <br><b>Cause:</b><br>On the target, the vaultServer logs in /usr/bp/logs.dir may be reporting that it could not register the storage manager key. It may be bnecessary to increase the VaultServer log level in Settings > System Configuration and Licencing > General (Advanced) > debugging to log level 3 to see this error. See below for the log excerpt. <blockquote class="blockquote">Apr 15 08:16:06 : [LOG4] Leaving function: smgr_register<br>Apr 15 08:16:06 : [LOG0] SIS.c:2400: <span style="color: #ff0000;">Can't register storage manager key: ELIMIT: Number of registrations exceed maximum limit</span>.<br>Apr 15 08:16:06 : [LOG0] vaultServer.c:647: failed to write to SIS, retry.<br>Apr 15 08:16:06 : [LOG4] Entering function: smgr_avail</blockquote> <b>Solution:</b> <ol><li>Use the replication target's web interface go to Settings->System Monitoring->Processes.</li> <li>Select the devmonitor process' row.</li> <li>Click Terminate Process.</li> <li>Then go to Settings->System Monitoring->Jobs.</li> <li>Check Advanced Options.</li> <li>Click Stop Tasker. The buton label will toggle to say Start Tasker.</li> <li>Click Start Tasker.</li> <li>Go to Settings->System Monitoring->Processes and confirm that you see a devmonitor process again.</li> <li>If the log level for VaultServer on the target was increased, return it to log level 0 or 1 for optimal replication performance.</li> </ol> Note: If the problem continues or reoccurs, contact Unitrends Support. This issue was resolved under release 8.0.x, upgrading to the current release and restarting devmonitor should prevent this issue from reoccurring. </article> </main>