Ask the Community
Groups
KAV 9.3: Cannot Install KAV Due to Error "Could not add job to scheduler: Agent has not been provisioned yet." - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>Problem</strong></p> <p>Cannot install KAV in the new Antivirus module due to the error "Could not add job to scheduler: Agent has not been provisioned yet. Could not get EndpointId with given assetId (<id>)."</p> <p> </p> <p><strong>Cause</strong></p> <p><strong><br></strong>There are several ways this error can occur. However, the issue is cause by agent endpoint data in the database not matching the data in the agent side.</p> <p> </p> <p><strong>Solution</strong></p> <p>The first thing to check is to see if the secondary KServer address configured on the agent can reach the KServer. To resolve this:</p> <ol><li>Navigate to Agent > Agents > Manage Agents.</li> <li>Click on the down arror next to a column, go to the Columns drop down and click the checkbox "Secondary KServer."</li> <li>Make sure you can ping the secondary KServer IP address from the agent.</li> <li>If this fails, set secondary kserver address to be same as the primary, delete the C:\Program Files (x86)\Kaseya\serverGUID\Endpoint\Provisioning.xml file, then restart the Kaseya Agent Endpoint service.</li> </ol><p>After performing this step, please try to install KAV again. If the install continues to fail with the same error, please perform the following:</p> <ol><li>Navigate to the Agent Procedures > Manage Procedures > Schedule / Create.</li> <li>Select a folder you want to import the agent procedure to and click the Import Folder/Procedure button.</li> <li>Upload the attached agent procedure to the "Upload an XML file for Import:" section and click Save.</li> <li>Run the Clean - Cycle Endpoint Service agent procedure on the agent with the error.</li> </ol><p>After the agent procedure runs, please schedule the KAV install again. If the same error appears again, please submit a Support ticket referencing that you have already performed the steps in this article.</p> <p><em>We recently updated the attached procedure. Please update this procedure in your VSA and delete the original Cycle Endpoint Service agent Procedure.</em></p> <p><strong>***IMPORTANT*** - this solution should ONLY be used to address the specific error mentioned above.</strong></p> <p><strong>Applies To</strong></p> <p>Kaseya 9.3</p> </article> </main>