PowerShell

Error occurred in deployment step ‘Recycle IIS Application Pool’: The local SharePoint server is not available.

For security and availability purposes we’ve moved away from using the SharePoint Farm account for development. Adding new devs to your farm can be pretty simple if you know what tools to use. Frist, I always add my devs to the local admin group. Second you need to run the following commands. This adds the domain user to the appropriate roles Get-SPDatabase | Where-Object {$_.WebApplication -like “SPAdministrationWebApplication”} | Add-SPShellAdmin domain\username…

windows-broken-mini

Error – Directory “FeatureDirectoryName” associated with feature ‘GUID1’ in the solution is used by feature ‘GUID2’ installed in the farm.

The solution cannot be deployed. Directory “FeatureDirectoryName” associated with feature ‘GUID1’ in the solution is used by feature ‘GUID2’ installed in the farm. All features must have unique directories to avoid overwriting files. I’ve ran into this error three times now. It happens when you create two projects with the same name. This error can happen when you have two solutions with the same name, one of the solutions has…

windows-broken-mini

SharePoint 2013, The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled.

The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled. If the timer job is scheduled to run at a later time, you can run the jobs all at once using stsadm.exe -o execadmsvcjobs. To avoid this problem in the future, enable the Microsoft SharePoint Foundation administrative service, or run your operation through the STSADM.exe command line…