Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Failed to change data folder ACLs

Updated: 03 Nov 2009 | 5 comments
sezam's picture
+5 5 Votes
Login to vote

Sometimes when You try to configure SEPM to use SQL database You can face this problem:

1.JPG 

Solution is Simple…..

          1.       Stop IIS Admin Service

2.JPG

          2.       Go to:  C:\Program Files\Symantec\Symantec Endpoint Protection Manager

·         Please open properties of data folder
                                                                            3.JPG

3.JPG

·         And check if Full control is granted for “Everyone”.

                                                                             4.JPG

          3.       After that go to Management Server Configuration Wizard and reconfigure SEPM one more.

                                                                             5.JPG

          4.  If You have made all steps written in this article, you should get this window, which means SUCCESS ;)
                                                                             6.JPG
6.JPG

Comments

shp's picture
15
Nov
2009
0 Votes 0
Login to vote

Good one.... 

Good one.... 

Regards,
Srinivas H.P.
HCL Infosystems Ltd

AravindKM's picture
15
Nov
2009
0 Votes 0
Login to vote

Nice Information.... 

Nice Information.... 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

steffen910's picture
07
May
2010
0 Votes 0
Login to vote

good information

good information

Constantine's picture
25
Oct
2010
0 Votes 0
Login to vote

quite good information

quite good information bro,

it heped me very much...

 

P.S. also do not forget to turn on an inheritance on "data" folder....

Moin_Sobhan's picture
22
Nov
2011
0 Votes 0
Login to vote

Failed to change data folder ACLs

This is very common if SEPM is installed in Windows 2008. This error can be avoided by doing the following:

1. If running Management Server Configuration Wizard remotely, make sure console/admin switch is used

2. Right Click on "Management Server Configuration Wizard", click "Run as administrator"