This project has moved and is read-only. For the latest updates, please go here.


Topics: Support
Apr 27, 2016 at 4:01 PM
Hi Guys,

AutoSpInstaller has recently stopped working at my organization after we applied Windows updates to our test machine. We're trying to set up SharePoint 2013 SP 1 (15.0.4569.1506) on a Windows Server 2012 R2 box with SQL Server 2014 (12.0.4100.1).

Powershell errors with the message:

PS>TerminatingError(Get-SPFarm): "Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permission to access the database before trying again.

Has anyone come across this before after applying Windows updates? Unfortunately we run the autospinstaller as part of an msi so I don't know which line of code is causing the problem, hence making diagnosing the issue very tricky. I've looked through the AutoSPInstaller related scripts and there are around 20 instances of Get-SPFarm so any assistance with this would be greatly appreciated.


Kevin White
May 5, 2016 at 4:41 AM
I'd suggest you run the script outside the context of the MSI just to see where it's failing. Personally I've not run into this FWIW.

May 6, 2016 at 2:13 PM
Thanks Brian, we narrowed the issue down to a big Windows Update (KB3000850) so we're just excluding that update for the time being.