Got Error: failed to secure sharepoint resources... cannot apply security settings to.. office server.. does not exist

When running SharePoint 2013 Configuration Wizard I got on step 4 of the Wizard the following error:

failed to secure SharePoint resources... cannot apply security settings to.. office server.. because it does not exist

I ran the Wizard after installing SharePoint 2013 Enterprise Edition.

Prior to  installing SharePoint 2013 Enterprise I've uninstalled SharePoint 2013 Standard on the same server but made sure to upgrade the farm to Enterprise by supplying Enterprise Key to the Central Admin of the Standard edition before uninstalling it.

Thus after installing the Enterprise Edition I was able to connect (With step 3 of the Wizard) to the existing farm/

Also the Standard Edition was Hebrew while the Enterprise is English.

I've also installed Hebrew Language Pack and the ran the Wizard again.

In all the cases I got the error above.

Please advise.

October 9th, 2013 6:33pm

did you uninstall the share point from all server in farm and then re installing with EE license key?

Could you please share PSdiag log?

Free Windows Admin Tool Kit Click here and download it now
October 9th, 2013 6:45pm

Thanks for your reply.

I had only one SharePoint server in the farm (+SQL 2008 R2 Server), and I've uninstalled it and then reinstalled with Enterprise license key. (As said in the previous post - before uninstalling I've upgraded the farm to Enterprise).

Here is a link to the PSdiag log:

https://skydrive.live.com/?cid=D24C15624542223E&id=D24C15624542223E%21127#cid=D24C15624542223E&id=D24C15624542223E%211604

Or:

https://skydrive.live.com/redir?resid=D24C15624542223E!1604&authkey=!IKG8!vvaspg%24

Here is an excerpt from the PSdiag log with the error:

....

10/10/2013 11:44:31  1  INF                        Not running in high contrast, so we will paint the background with our trademarked image
10/10/2013 11:44:31  4  ERR                        Failed to secure the SharePoint resources.
An exception of type System.ArgumentException was thrown.  Additional exception information: Cannot apply security settings to resource C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Office Server\ as it does not exist.
System.ArgumentException: Cannot apply security settings to resource C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Office Server\ as it does not exist.
   at Microsoft.SharePoint.Administration.SPResourceAccess.ValidateResourceName(String name)
   at Microsoft.SharePoint.Administration.SPResourceAccess..ctor(String resourceType, String resourceName, Int32 securityGroup, String permissions)
   at Microsoft.SharePoint.Administration.SPResourceAccess.SecureResources(Boolean isSingleBox, EventHandler`1 progressUpdateEvent)
   at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
10/10/2013 11:44:31  1  INF                        Not running in high contrast, so we will paint the background with our trademarked image

...

Here is screenshot of the error I get:

Please advise.




October 9th, 2013 11:18pm

Couple of things to have check,

1) check the permission on the folder "..\Data\Office Server\Office Server", the account under which you installing the SharePoint?

2) do you have the Hebrew Language pack install, is that still exist, if yes then uninstall it.

3) did you run the pre-requisite before fresh installation.

4) restart the server?

Free Windows Admin Tool Kit Click here and download it now
October 10th, 2013 9:30am

One more thing, i am thinking, may be you instalation was not clean,

Uninstall everything i.e Sharepoint, Language Packs and delete the folder and restart the server.

then try to fresh install.

October 10th, 2013 9:46am

Thanks for your reply.

1. I've checked: the account under which I was installing the SharePoint has Full control of the folder ..\Data\Office Server\Office Server". That account is a member of local Admins which has Full control permission of that folder (as well it is member of domain Admins which is also a member of local Admins).

2. When I was installing the Enterprise Edition I had no Language Pack installed.

3. I've run the prerequisites prior to doing fresh install (of the Enterprise Edition).

4. I've also done server restart several time (although I'm sure if I did one right after installing).

Thanks for the replies.

Free Windows Admin Tool Kit Click here and download it now
October 11th, 2013 4:48am

Thanks again for the replies.

What I did at the end was that I reverted back to the Standard edition and there I made sure to Enable Enterprise Features (via the Central Admin). At a prior step (before the 1st install of EE I only set Enterprise License key (via Central Admin), and didn't make sure to Enable Enterprise Features.

Then I've uninstalled the Standard Edition (including the Hebrew Language Pack- which was left from after installing the EE-English version), as well as restarted the server and re-installed the English Enterprise Edition.

At this stage I didn't had the "failed to secure SharePoint resources..." error of step 4 of the SharePoint 2013 Configuration Wizard and it completed successfully. (see also this thread that I've open in this regard).

Then I also re-installed the Hebrew Language Pack and got SharePoint system to be quite functional again. Yet I'm encountering some strange functional problems. E.g.: on the standard Edition I had a primary (i.e. under the / URL) site collection of type Documents Center. It was Hebrew and stayed Hebrew (under the EE-English installation). That is expected. When tried to create another site Collection (under URL like /sites/DocsArchive) of type Documents Center - this time in English - I got a response error: "Sorry, something went wrong." and below that a line like: "This product has expired". I could create site collection of other type in English (I think it was Publish-type), and I could also create Documents Center in English but only as a SUB-SITE.

Do you have any clue of that new problem?

Thanks



October 11th, 2013 5:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics