Kashif Nizam Qureshi

Timer Job, could not be updated because the current user is not a Farm Administrator

After successful deployment of WSP over the server, when activating the feature it threw an error “Timer Job, could not be updated because the current user is not a Farm Administrator” found it from the logs.

The solution is simple, run the following command as Administrator in SharePoint 2010 Management Shell.

Enable-SPFeature -Identity “FeatureName” -Url “http://servername:port”

Follow the link for more details:

http://msdn.microsoft.com/ru-ru/library/cc427068(en-us).aspx

Updates 24-08-2013:

I had similar issue again but this time the above solution didn’t work in first go, it threw this error “The Feature is not a Farm level feature and is not found in a site level defined by the url” when tried the above command. I followed the steps given below and it worked, it’s not necessary to do all these steps.

1. If multiple servers exist ( App, WFE etc.), try running from WFE first and then to others.

2. Uncheck read only files, use the following command

$Path = “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\”
$Files = Get-ChildItem $Path -Recurse
ForEach ($File in $Files)
{
Write-Host “File: ” $File “IsReadOnly: ” $File.IsReadOnly
if ($File.Attributes -ne “Directory” -and $File.Attributes -ne “Directory, Archive”)
{
if ($File.IsReadOnly -eq $true )
{
try
{
Set-ItemProperty -path $File.FullName -name IsReadOnly -value $false
write-host “file:” $File.FullName “is now false read only” -foregroundcolor “magenta”
}
catch [Exception]
{
Write-Host “Error at file ” $Path “\” $File
Write-Host $_.Exception.Message
}
}
}
}

http://iwillsharemypoint.blogspot.com/2012/05/enable-spfeature-feature-is-not-farm.html

http://iwillsharemypoint.blogspot.com/2012/04/uncheck-read-only-file-for-all-sub.html

3. Added Application Pool account to Central Admin’s Farm Administrator groups.

http://www.thorntontechnical.com/tag/current-user-is-not-a-farm-administrator#.UhfjeRumg70

4. Retract, Remove, Deploy (run as different user (shift+right click), farm account) and Activate using command Enable-SPFeature.

5. I had to use the following post to find correct name of my feature.

http://rajeshch999.blogspot.com/2012/07/powerdhell-feature-is-not-farm-level.html

Advertisements

4 thoughts on “Timer Job, could not be updated because the current user is not a Farm Administrator

  1. This isn’t so much a solution as a work around.

  2. didn’t work

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s