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.

not able to repair sepm

Updated: 21 May 2010 | 4 comments
ajeet kumar's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

error 1315 unable to write to the specified folder d:\program files\symantec\symantec endpoint protection manager\inetpub\reporting\temp

Comments

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

Can you paste SEPM_inst.log

Can you paste SEPM_inst.log here..
Also check the permissions for  d:\program files\symantec\symantec endpoint protection manager\inetpub directory for your current user,System and iuser

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

Rafeeq's picture
18
Nov
2009
0 Votes 0
Login to vote

hI

Create that entire missing folder path if it's missing, and then remove the read-only setting of every level of that path if it is set.

Check the space on C drive , try again should be able to do a repair.

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

sandip_sali's picture
18
Nov
2009
0 Votes 0
Login to vote

SEPM

This error says that you do not have permission to write to this file. There are two easy solutions to this problem:
Go to the file it specifies and check the permission. To do this right click on the file and select Properties. Check the Attributes to see if the file is Read-only. Then, click on the Security tab to check if your computer is one of the user names with access to the file. This should give you more insight on why you don't have permission. Sign on as an administrator. The administrator should have full access to all of the files you need to write to when installing SEPM

Thanks & Regards Sandip C Sali

ajeet kumar's picture
23
Nov
2009
0 Votes 0
Login to vote

Thanks all of you. Dear

Thanks all of you.

Dear Sandip,

It was file permission issue. now i fixed this issue.