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

Commented Issue: Sharepoint 2013 and User Profile Service using version 96613 [19072]

$
0
0
Hi Brian,
Tried to use the latest one from source code and got the following error

Creating User Profile Service Application as local\SPFarm...
The local farm is not accessible. Cmdlets with FeatureDependencyId are not regis
tered.
New-SPProfileServiceApplication : Object reference not set to an instance of
an object.
At C:\Users\pcuser\AppData\Local\Temp\AutoSPInstaller-ScriptBlock.ps1:3 char:25
+ $newProfileServiceApp = New-SPProfileServiceApplication -Name "User Profile
Serv ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo : InvalidData: (Microsoft.Offic...viceApplication:
SPCmdletNewProfileServiceApplication) [New-SPProfileServiceApplication], N
ullReferenceException
+ FullyQualifiedErrorId : Microsoft.Office.Server.UserProfiles.PowerShell.
SPCmdletNewProfileServiceApplication

C:\Users\pcuser\AppData\Local\Temp\AutoSPInstaller-ScriptBlock.ps1 : - Failed
to create User Profile Service Application
At line:1 char:1
+ C:\Users\pcuser\AppData\Local\Temp\AutoSPInstaller-ScriptBlock.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
tion
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
n,AutoSPInstaller-ScriptBlock.ps1

Press any key to exit...

Hope you have let me know what was wrong. Thanks and GOOD JOB on the installer.
Comments: ** Comment from web user: brianlala **

It looks like maybe local\SPFarm isn't getting added to the local admin group within the script, or it has some other kind of permissions issue. This is evident by the line "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered" which you would only get if there was no farm created yet (not the case here) or if the account running PowerShell didn't have the right permissions.

Double-check your *Input.XML file, or else check if perhaps a GPO or other local setting is preventing the SPFarm account from being added as a local admin (required for creating the UPS as SPFarm).

Brian


Viewing all articles
Browse latest Browse all 1245

Trending Articles