Quantcast
Channel: autospinstaller Issue Tracker Rss Feed
Viewing all articles
Browse latest Browse all 1245

Commented Unassigned: "The local farm is not accessible" [19850]

$
0
0
On a fresh install of Windows Server 2008 R2 SP1, SQL Server 2012 and PowerShell 3.0 (could PS 3.0 be the reason? ):

[all is well until ...]
--------------------------------------------------------------
- SharePoint 2013 binary file installation done!
--------------------------------------------------------------
- Adding IATTC01\SharePointFarm to local Administrators (only for install)...
--------------------------------------------------------------
--------------------------------------------------------------
- Loading SharePoint Powershell Snapin...
The local farm is not accessible. Cmdlets with FeatureDependencyId are not regis
tered.
could not create a CmdletConfiguration for CmdletName Install-SPRSService, Cmlde
tClass , CmdletHelpFile C:\Program Files\Common Files\Microsoft Shared\Web Serv
er Extensions\15\CONFIG\PowerShell\Help\Microsoft.ReportingServices.SharePoint.P
owerShell.dll-help.xml.
Cannot process argument because the value of argument "implementingType" is null
. Change the value of argument "implementingType" to a non-null value.
could not create a CmdletConfiguration for CmdletName Install-SPRSServiceProxy,
CmldetClass , CmdletHelpFile C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\CONFIG\PowerShell\Help\Microsoft.ReportingServices.SharePo
int.PowerShell.dll-help.xml.

[this repeats many times until eventually we get to:]

--------------------------------------------------------------
- Checking farm membership for INTRANET in "Intranet1_Config"...

- Attempting to join farm on "Intranet1_Config"...
- No existing farm found.
- Creating config database "Intranet1_Config"...
- Done creating configuration database for farm.
--------------------------------------------------------------
--------------------------------------------------------------
- Configuring the SharePoint farm/server...
- Installing Help Collection...
- Securing Resources...
- Installing Services...
- Installing Features...
- Creating Central Admin site...
- Waiting for Central Admin site...Online
- Updating Central Admin branding text to "IATTC Intranet"...
- Installing Application Content...
--------------------------------------------------------------
- Script halted!

Exception : System.IO.FileNotFoundException: Could not load file
or assembly 'Microsoft.IIS.PowerShell.Framework' or
one of its dependencies. The system cannot find the
file specified.
File name: 'Microsoft.IIS.PowerShell.Framework'
at
System.Reflection.RuntimeAssembly._nLoad(AssemblyName
fileName, String codeBase, Evidence assemblySecurity,
RuntimeAssembly locationHint, StackCrawlMark&
stackMark, IntPtr pPrivHostBinder, Boolean
throwOnFileNotFound, Boolean forIntrospection, Boolean
suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.LoadWithPartial
NameInternal(AssemblyName an, Evidence
securityEvidence, StackCrawlMark& stackMark)
at Microsoft.IIs.PowerShell.Framework.Interop.IAppHo
stElement.get_Properties()
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.get_Attributes()
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.ToPSObject(ConfigurationElement parent)
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.ToPSObject(ConfigurationElement parent)
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.ToPSObject(ConfigurationElement parent)
at Microsoft.IIs.PowerShell.Provider.GetWebsiteComma
nd.WriteSite(ConfigurationInfo o)
at Microsoft.IIs.PowerShell.Framework.Configuration.
XPathQueryToStream(String query, PipelineStreamWriter
writer)
at System.Management.Automation.CommandProcessor.Pro
cessRecord()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the
registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to
1.
Note: There is some performance penalty associated
with assembly bind failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].

TargetObject :
CategoryInfo : NotSpecified: (:) [Get-Website], FileNotFoundException
FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.IIs.PowerShel
l.Provider.GetWebsiteCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at ConfigureFarm, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerFunctions.ps1: line 1480
at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\Au
toSPInstallerMain.ps1: line 185
at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

-----------------------------------
| Automated SP2013 install script |
| Started on: 6/13/2013 9:17:10 AM |
| Aborted: 6/13/2013 9:37:31 AM |
-----------------------------------

Second attempt immediatelly after the above:

[all is well until ...]
--------------------------------------------------------------
- Adding Managed Accounts
- Enabling Secondary Logon service...
- Starting Secondary Logon service...
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidation
Exception: Cannot bind argument to parameter 'String'
because it is an empty string.
at System.Management.Automation.ExceptionHandlingOps
.CheckActionPreference(FunctionContext funcContext,
Exception exception)
at System.Management.Automation.Interpreter.ActionCa
llInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTry
CatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTry
CatchFinallyInstruction.Run(InterpretedFrame frame)
TargetObject :
CategoryInfo : InvalidData: (:) [ConvertTo-SecureString],
ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,M
icrosoft.PowerShell.Commands.ConvertToSecureStringComma
nd
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at AddManagedAccounts, C:\AutoSPInstaller\SP\AutoSPInst
aller\AutoSPInstallerFunctions.ps1: line 1580
at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\Au
toSPInstallerMain.ps1: line 189
at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :



-----------------------------------
| Automated SP2013 install script |
| Started on: 6/13/2013 10:49:19 AM |
| Aborted: 6/13/2013 10:49:55 AM |
-----------------------------------
PS C:\AutoSPInstaller\SP\AutoSPInstaller>
Comments: ** Comment from web user: mlopez_iattc **

I meant to say *WMF* 3.0. I am a bit confused because WMF 3.0 is a prerequiste for SP 2013, yet having WMF 3.0 installed on the server before running ASPI is what seems to break things. I'd appreciate being put straight on this.

M.


Viewing all articles
Browse latest Browse all 1245

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>