The difference between my successful attempts and the failed attempts was installing the SP2013 pre-requisite EXEs but having ASPI install the hotfix patches. I was able to get around this by rolling back to my previous snapshot (without pre-requisites at all) and having ASPI complete all the prerequisite installs (much slower of course).
The script finally stalls with the following:
- Provisioning Managed Metadata Service Application
- Creating SharePoint Hosted Services Application Pool...
- Starting Managed Metadata Service:
- Starting Metadata Service Instance...
- Waiting for Metadata service...Online
- Creating Metadata Service Application...
The section of the install that deals with pre-requisites looks like this:
- Installing Prerequisite Software:
- Running Prerequisite Installer (online mode)........Done.
- Prerequisite Installer completed in 00:00:25.
- SharePoint 2013 "missing hotfix" prerequisites...
- Checking for KB2554876...Already installed.
- Checking for KB2708075...Already installed.
- Checking for KB2472264...Already installed.
- All Prerequisite Software installed successfully.
I know using ASPI for SP2013 is beta - but I thought I would raise the awareness of the behaviour.
@SPSavvy
Comments: ** Comment from web user: brianlala **
More info. I managed to repro the issue a few days ago. However I remembered to launch ULSViewer while the script was running. The last entry in the ULS logs for powershell.exe process is this:
_Blocking until timer job '65a7cd06-b598-4ede-92b3-9ec1417cf695' has completed._
Then I went looking for this timer job soon afterwards (w/ Get-SPTimerJob) but couldn't find it.
I actually left/forgot the script in that 'hung' state after "Creating Metadata Service Application...", and interestingly, after an undetermined period of time, it finally errored out with:
New-SPMetadataServiceApplication : The timer job did not complete running within the allotted time.
At \\brilalawin8\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1768 char:39
+ $metaDataServiceApp = New-SPMetadataServiceApplication -Name $me ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...MetadataService:SPCmdletNewMetadataService) [New-SPMetad
ataServiceApplication], TimeoutException
+ FullyQualifiedErrorId : Microsoft.SharePoint.Taxonomy.Cmdlet.SPCmdletNewMetadataService
I'm inclined to think that this is a bug in the provisioning process rather than AutoSPInstaller (naturally :)) but it requires more digging.
Brian