Ask the Community
Groups
SharePoint farm backup job failed, no client messages present - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>SharePoint 2010 or 2013 farm backup job failed, no client messages present</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p>SharePoint backup fails due user credentials not set correctly</p> <p>SharePoint 2010, 2013 or 2016 farm backup job failed, no client messages present</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> Command Failed: Verifying SharePoint User Credentials ----- Client Messages ----- ----- End Client Messages -----</pre> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <ol><li>Create domain account 'domain\SP2013': password never expire</li> <li>Add the account 'domain\SP2013' to local administrators group</li> <li>Give the account 'domain\SP2013' the rights to log on as a service: <ol><li>Select Control Panel > Administrative Tools</li> <li>Select Local Security Policy > Local Policies >User Rights Assignment.</li> <li>Right-click Log on as a service and select Security or Properties.</li> <li>Click Add to add the account on which the Executive Viewer service is running on.</li> <li>For a domain account the Domain Security Policy has to be adjusted.</li> </ol></li> <li>After that the message in summary output will be: <pre class="code codeBlock" spellcheck="false" tabindex="0"> Object reference not set to an instance of an object.</pre> </li> <li>Add 'domain\SP2013' account to be a 'Member of Farm Administrators SharePoint group' <ol><li>Login as SharePoint administrator to the client</li> <li>Click Microsoft SharePoint 2013 Products.</li> <li>Click SharePoint 2013 Management Shell.</li> <li>At the Windows PowerShell command prompt, type the following command: <pre class="code codeBlock" spellcheck="false" tabindex="0"> Add-SPShellAdmin -UserName domain\SP2013</pre> </li> </ol></li> </ol><h2 data-id="cause"><strong>CAUSE</strong></h2> <p>User credentials are not valid</p> </article> </main>